richard: hi. good afternoon, and welcome toour interview with the gpdc team, also known as thegoogle play developer console preview team. today we're joined in our lovelyhangout little room
Android developer console, here with ricardo andmax and ellie and-- pierre: pierre. richard: pierre. slightly awkward moment as idon't know pierre's name.
and of course we're here todiscuss the brand new google play developer console preview,which hopefully you've had a good chance to tryout, see the new features through the awesome new ui. i'll leave you in the capablehands of max, i think, to start with. he's going to run throughsome demos for us of all the new features. ellie: so really quickly beforewe jump into demos, i
guess wanted to just make sureyou all know why we built a new developer console. big reasons we've gotten from itwas, you guys are using the developer console more andmore to update your applications. you're really growingyour businesses. and we had a bunch of featureswe want to be able to add in the future. and we wanted to give youa great user experience.
so that was the motivationfor doing it. and so this year at google i/owe announced and demoed the and then last week, you all got access, as richard mentioned. so we wanted to say that whatwe have here is a preview. it's not totally done yet. i'm sure many of you have foundthings that you'd like to see improved beforewe consider it done. and there are a coupleof features we
haven't released yet. but we also hope that you'llsee this as kind of a foundation and a platformfor more things to come. so we really welcome all of yourfeedback about how we can continue to improve it. so max is going to walk usthrough what we have in the preview today. max: cool. richard, can we make my screenvisible for everyone?
richard: of course we can. max: perfect. here we go. you may remember the demo atthe google i/o. so you may remember this app. so basically that's thestart page if you arrive on the new page. and you see the handy developerguide, which got published during thedemo at google i/o.
so you start with the storelisting with the most important informationabout your app. what's interesting is with thenew page, we now support up to 49 localized information. so for instance, let's try toadd some german to that app. we still call it the handydeveloper guide. and you can add descriptionand so on and so forth. we can save and publishdrive guests. we should get anerror for that.
you see, we also tried to giveyou way better information. if you do something wrong, whatyou did wrong, what you should do to fix that. but let's see. let's fix it. ellie: it's not a veryinteresting app, is it? so one of the other things thatyou'll notice, like max mentioned, is you have up to 49languages, which is a lot more than we had before.
we have some languages like ukenglish and turkish that we didn't have before. and another thing that you'llalso notice, it's kind of an invisible feature. for listings where you don'tprovide a manual translation or a human translation, we'llcreate an automated translation using googletranslate behind the scenes. and then users who areencountering your store listing, if it's not in theirnative language, once you've
saved it to the new developerconsole, they'll actually see a button allowing them to viewan automated translation. so just to be clear, theautomated translations are generated by google translate. and so they're obviously notgoing to be as good as having a native speaker of german,like max, creating the translation. but until such time as you'reable to get the servicers of a professional translator, theycertainly will go a long way.
and you don't have to doanything to make the automated translations happen. once you've saved your app tothe new developer console, they'll happen behindthe scenes. and you can go ahead and updatethe default language as often as you want, and theautomated translations will update automatically. this is a change from the olddeveloper console, wherein you used to have to select anautomated translation for each
language where you wanted one. and then they didn'tupdate properly. so here it all happens behindthe scenes as soon as you've saved your app inthe new console. max: we've seen, usually,german is too long. so we leave it here inthe original title. ok. we've saved these changes. let's have a lookinto the other--
i have to click thatobviously. richard: and you get thelittle running android. max: yeah, the running androidis one of the best parts of the new app. ellie: i think that was the mostpopular feature with our developer relations team. they really liked therunning android. max: we love it. some kind of progress isalways nice, right?
ellie: yeah, exactly. and it's just cute. i think it's cute. max: so yeah, the list ofcountries where you can publish your app. obviously if you have a paidapp, you see and can set the prices here. this app has no innerproducts. let's look into theapk screen.
again, we tried to give you asmuch information as we can give you on that page. and see like the supporteddevices, i think this is a great way to go through earththrough the devices to see where your app is workingor where not. or even if you even want toexclude devices because there's certain handsets whereyou have problems. you can add that here as well. and obviously if you havean update, you can
upload new apk here. and you see the changes. so for instance, we have nowlocalized information for german in the app. i think it's pretty good herebecause you may unfortunately use the wrong apk to uploador something like that. and you get immediately theinformation of what changed. so we want to just give you asmuch information as we can give you to prevent any mistakesfrom your side.
let's have a lookinto statistics. same statistics. we will see some more ona different tab soon. we have all of these differentdimensions. if you're ever in doubt what itexactly means, there's the handy tool to give you detailsabout the differences between active and total devicesand users. i think once you get used toit, you know what it means. and it's just, again, great.
we want to give you, justrepeat myself, as much information. and we will let the decision foryou to what you actually want and how youwant to use it. the new crashes overviewis also pretty cool. so we have a bunch of filters. and you can go throughthe stack traces. and you also might have thatvisible on the last report here on that part, if you cansee the mouse pointer.
we also jump through thedetails of everything. ellie: yes, this is when iforgot that grid layout didn't exist in older versions. that was a good lesson for me. max: happens. and as well, theuser messages. hopefully they will give usefulinformation, like how it exactly happened. let's jump into one of rich'sapps, where we have pretty
cool ratings. because it's an awesomeapp, obviously. richard: ultimate stopwatch. max: it's a new dimensionjust recently added. ricardo, maybe you can saya bit more about that. ricardo: yeah, we use it todisplay basically how your ratings have evolvedover time. because often that's aninteresting method to keep track of, to measureuser satisfaction.
and we offer you basicallytwo new metrics. one is the cumulativeaverage rating. and it tells you basically theaverage of all the ratings that your application hasgathered over time. and this is exactly what you seealso in the storefront on play.google.com of the actualrating that the user has given you. and so basically, the last pointin the chart that says that we have a rating of 4.35should match what you see on
the storefront above therating that your app currently has. the extra information that youget here, in addition to the history over the time of thisrating, is the breakdown by all the usual dimensions thatyou're already used to from the other metricsthat we offer. so for example, you could seeby, i don't know, how the rating is divided by device. and you can see maybe that someusers from given devices
give you a lower ratingthan other users. and maybe this is indicativethat you have not optimized your application fora given device. maybe it uses a different screensize, and you have not really optimized for that. so the user experienceis less optimal. by language as well, maybe youhave not optimized your application for agiven language. you have not localized.
so your user rated poorly. and another interesting oneis by application version. because you can see by rollingout new version whether people like it more or not. and maybe your new version isnot as good as you thought, and you want to do some fixesand change it again. if the cumulative average ratingover time provides a too broad metric, because itaccumulates all the rating even from last versions, evenfrom previous, if you have
been out for a long time,previous months, previous years, then you can switch tothe daily average rating, which is exactly the same metricbut aggregated over a daily basis. and this gives you a much moregranular information about how on each day uses are ratingyour application. and again, depending on how manyusers you have, you may have various [? interactive ?]information that shows you on a particular day what is theaverage rating that your
application got. and this gives you much moredetailed information. for example, when you want toclosely track how a new launch is happening, how a newlaunch is going. and as usual, you can alwaysexport this metric, just like all the others. so if you want to do your owncustom aggregations on your site by merging together otherdata sources, you can get a full breakdown in cspformat as well.
so you can proceed from there. richard: that's absolutelyexcellent. i didn't know theratings trending existed inside the reporting. has that been in the stats sincethe new stats were in? ellie: no, this is actually alaunch last monday with the new developer console preview. richard: well, i'm sureto make use of that. i'm working on an update to theultimate stopwatch anyway.
it's likely we'll be able tosee the trending app as-- ellie: i was noticing on yourstats, actually, that for your latest version, that had anactually better user rating than the other versions. i'm not sure if you knewthat, but your update really was an update. it was a good update. max: and i know you're workingon tablet support. so you can see which devices arerating it higher, if the
tablets are now likingit more. ellie: that's true, you can seeif the nexus 7 users are enjoying that one. max: that's brilliant. ricardo: and on this case,you maybe should work on localization for portuguese. ellie: you're not very happy. richard: can you justdo that for me now? just press the--
max: i don't know. i can help you with german. richard: no, the automatictranslation-- max: oh, yeah, that's right. ellie: the automatictranslations are just for the store listing. that's not actually forthe applications. or maybe portuguese users arejust more unhappy than the dutch users, i'm not sure.
max: talking writing in reviews,actually, forgot to show that page as well,to give you an overview about the ratings. but as we just encountered, thegreater overview and the details are on thestatistics page. and our products are also partof the developer console. some of you had early access,but that's now as well live. so if you want to adda new product-- there's a typo.
want to fix that, because youcan't do it otherwise afterwards. manage product. and again, it looks prettysimilar to the store listing page for your main app. we didn't want to confuse youwith too many different widgets and so on. you can add all of yourinformation here, as you're used to from your store listing,obviously just what
is required for innerproducts. and easy, just do theauto convert. you may want to check thedetailed prices, because guessing euro maybe 2.49sounds a bit better. but again, want to give youthe tools so you can do everything easily. it's sometimes abit difficult. but we always try. we know some of you developershave full time jobs.
and you love to developfor android and do that on the side. and we try to support you in thesame way as we do it for big developers. but as we said, we are happyto get some feedback today from all backgroundsof developers. so let us know if you haveany wishes or ideas. and we're more than happy todiscuss that, and maybe even do it in the end.
we have also the service inapis here, if you, for instance, use google talkmessaging, you can configure that here. and i think that'sbasically format. i'm not sure ricardohas anything else? ricardo: that's prettymuch it. ellie: yeah. we hope you all give it a try. and one other thing to point outif you haven't noticed it
is the gigantic orange link thatsay, give us feedback, in the upper right hand corner. we read all that feedbackpersonally. and although we're not able torespond to every message that we get, we do keep it all inmind when we're planning future updates. so please click on it, let usknow what you think, and tell your friends. richard: thank you very much.
excellent. some good stats. and the fact that i've learnedsomething is also kind of handy, too. is the trending ratings theonly new statistic? is there anything elsei would've missed? ellie: no, those are the newones that we launched with the open preview. so we definitely see that asa great way to identify
opportunities to improve yourapp, and to also see, every time you release a new version,did it actually improve what your usersthink about you. richard: hopefully it does. ellie: that's always the goal. max: leave it on, maybe we wantto switch back, but i think we can. richard: ok. hello, everybody.
so we have some questionsin the moderator. but if you're thinking ofjoining the hangout and asking the gpdc team something live,now's a good time to jump in. and we'll get you lined upto ask the questions. also, you can comment onthe g+ post for this. and we'll be readingthose as well. so do you have somethingfrom the moderator? nick: yeah, i can dive in tothe moderator questions. before we go into the questions,i think it's best
to reiterate, as we always sayon our developer hangouts, that we're not going tobe making any product announcements here. we're going to be discussingyour comments and feedback. but any questions of, when willx launch, when will i get feature y, that we're notgoing to be able to talk about, i'm afraid. so i think the best way todirect the conversation is to give us constructive feedback ofwhat you like, and what you
would like to see moreof from the team. but asking for launchdates, not so much. so with that in mind, whenwill it be possible to moderate comments onapplications, is i guess one of these forward-lookingstatements we're not going to really get into, like we said. ellie: well, i guess what wecan say so far is that we realize that this was a reallyimportant feature for developers.
so we wanted to get it out thereas soon as possible. we've definitely heard verystrong feedback from a lot of developers who don't have accessyet that they do want to have access. so we hear that you wantto have the access. but we're still trying to makesure that the feature's working exactly as it shouldfor developers and users. and hopefully, we'llbe able to roll it out more in the future.
but as nick mentioned, wecan't really make any announcements in this meeting. nick: so the next questionis again asking for when will x happen. but i'm going to rephraseit into feedback. cicero in france asks, he saysthat his screen shots and feature promo graphics at themoment come out slightly blurry due to compression. and so i'm going to rephrasethat to, are we aware of this?
and are we looking into this? ricardo: yes, we are. so we're aware that in theprocess in some cases, the screen shot maybe got resizedin a way that-- nick: so we compress it onour end to save space. ricardo: yeah. we do some optimizationsfor serving as well. and so yes, we'reaware of that. nick: ok.
so watch your space,essentially. we've got someone joiningus in the hangout. male speaker: yes,one small thing. you said that you posted on theyoutube channel to go to the link in the description. there is no link inthe description. i was trying to put something inthe moderator, but i don't have a link in thedescription. nick: apparently if youtry hitting refresh?
male speaker: i have. and i've closed the pageand reloaded it. still nothing. richard: all right. let me take a look. i'll try to fix that for you. we've got a [inaudible] engineer extraordinaire from themountain view office has kindly dialed in live.
you might've seen his faceappear in the bottom corner. so hopefully we can getthat sorted out for you pretty instantly. nick: next question from themoderator, oren in israel asks, how can i delete orhide an unpublished app? ellie: well, that is somethingthat has gotten nearly as many requests as being ableto reply to reviews. i think it's something thatwe're looking into. nothing to announceat this point.
but thanks for that feedback. we've definitely heard fromdevelopers that they want a way to kind of de-cluttertheir interface. some people only have one or twoapps and they don't have this problem. but some people haveall sorts of apps. and at some point they decidethat they don't want to maintain that app anymore. or they've created it byaccident, and they'd
like to remove it. so yeah, thanks forthat feedback. richard: am i right in thinkingyou can delete an app if it's never been published? ellie: not in the new site. it hasn't been implementedyet. like i said, totallynot finished yet. this is one of the things wehaven't implemented yet. richard: so the thing to dowould be to create a second
android in front of a consoleaccount, and then use the app transfer to transferall your apps. ellie: no! just ignore it! just ignore it for now. sorry it's a bit cluttered. richard: yeah. it'll sort itself out. [inaudible].
nick: next question, so nikolaiin tokyo, he's asking, are there any plans to publishan api for app statistics? so i guess we're not goingto comment on future plans and so on. but i guess we could fit thatinto feedback, that he would love to see somestatistics api. so i guess that would be nicefor automating your own reporting mechanisms. ellie: yeah, definitely.
in the meantime, you canuse the csv export. richard: so we have heard thatfeedback i think more than once already. ellie: many times, yeah. ricardo: csv is obviously notas powerful as an api. but it is the easiest form toget access to those data. and it's a bit hard to discover,but csv also include more complete breakdown thanthe other metrics. on this interface, yousee only the top 10.
but if you get the csv, forexample, you get the full list of devices, if you are lookingat device dimension. and so you can do more complete analysis by using that. nick: so definitely worth goinginto that csv if you haven't tried it yet. and just rely on thetop 10 graphs. ricardo: we have heardthe requests about more complete apis.
nick: cool, awesome. next request is obviously, userx is loving the new dev console so much he wants thechoice to be sticky rather than having to optin every time. when he switched to try the newdev console, he says he has to check it every time. ricardo: yes, that is correct. it's not a stick yet. max: just put in a bookmarkto the new one.
the thing is-- richard: it's a v2. max: it's a differenturl, so-- ellie: bookmark it for now. richard: change your bookmarks,there we go. also, oren, about deleting appsfrom your account, i just had an idea that you could justrename the apps that you don't like to zed zed zed. and they would just go downto the bottom of the list.
i've just been into my accountsand renamed the apps that i didn't wantto see there. and they've all gone straightto the bottom of the list. nick: or put a tilde orsomething next to it. richard: so at least you don'thave to look at them anymore, even if they're just at thebottom of the page. ellie: that's a good idea. richard: does the new consolehave a limit to the number of apps that appear onthe front page?
ricardo: it's 50 per page. we did a few estimations ofthe average number of that seems to be a goodcompromise between the different usages. and also trying to geteverything in one page. before it was eight applicationsper page, and it was just not. richard: someone else has joinedus in the hangout. it is [? sonel. ?]
[? sonel, ?] do you have anyquestions for the developer console team? male speaker: hello? nick: hello. you're very quiet. ellie: hello. male speaker: i havea question. richard: yeah, please,go ahead. male speaker: i have a questionregarding android.
hello? please go ahead andask the question. male speaker: i want to know,how [inaudible] secure using android apps? nick: how secure is itto use android apps? ok, so i don't think that'sreally a question for the android publisher site. can you perhaps come back intoour office hours we have on wednesdays at 2:00 pm gmt andask the question there?
we're going to focuson the developer console for this session. ok? male speaker: thank you. nick: sorry. richard: thanks for joiningus though, cheers. back into the moderator. so there's a feature requesthere that ashley in london would like to see us order--
comments on devices by thosecomments left by people in the same device. so feedback, i guess, for thegoogle play client team. ellie: sorry, what was it? was it being able to-- nick: they'd like to seecomments, when they're looking at an application on device inthe google play store, to see comments rated or ranked byusers of the same device. that's an interestingfeedback.
ricardo: isn't that labeledalready in the google client? you can see-- nick: you can see whatdevice it came from. ricardo: from my device? richard: there is a filterin there, isn't there? ellie: it's hard to find, buti think it does exist. richard: maybe italready exists. nick: in the web version,you're saying, or? [interposing voices]
ricardo: reviews from mydevice, or something. ellie: you have to clickon reviews first. richard: see all reviews. most helpful first, highestrating, newest, options, for my device model only. so whoever askedthat question-- nick: ashley in london. richard: ashley in london,there's an option-- not that you're going to be able to seethis-- it's on the right hand
side of the ratings. and you can press itand choose for my device model only. nick: next question, andy inbrooklyn in usa asks, are you planning an api to facilitateautomated or at least more streamlined publishedand updating? so i guess you can't say arewe going to do it or are we going to launch it or whatever,but is it feedback that you've heard?
ellie: we've definitelyheard it before. and i think for developers whohave larger numbers of applications, some of them have definitely requested this. nick: my problem with suchthings is that i could see people using it to publish tomultiple places at once, in which case you get to the lowestcommon denominator approach, where they're nottaking advantage of things like the stream translation,and so on and so forth that
other storefrontsmight not offer. ricardo: may be helpful,depending if you have customized build tools andworkflows, at which point publishing is just at theend of your train. but there is the moderation. richard: quite interestingcomment from daniel baines on the g+ post, one that i hadn'tthought about before but may not be too tricky. it's about promotingyour applications.
at the moment, we give peopleaccess to the google play branding, in that little buttonso they can put it in their website. he's asking for an embeddablewidget that he can put in his website where it will list hisapplications on the play store in a nice format with theratings that they have. and just let peopleclick straight through, and can buy them. ellie: ooh, thanksfor that idea.
richard: thank you, daniel. nick: that is cool. richard: well, anythingto help promote. nick: we could talk about thebadge, because we don't really have the badge generators forindividual apps at the moment, don't we? we don't have one for thepublisher page, as well. richard: for all your apps. nick: cicero, again, in franceasks, there's currently no way
to prepare a full release. you can upload an apk. but all of the extrainformation-- descriptions, screen shot, et cetera-- arenot part of a release. as a result, apk and informationare currently made available independently. that makes sense? ricardo: yeah, that is true. so at the moment, after you havepublished, then you add
it physically each part of theapplication independently. but until the moment youpublish, you're free to modify and add information as soonas you gather them. so you can start by saying,i'm putting in the store listing or a screen shot,because that's what my designer gave me first. and one day if apk'sready, you can add that in a second moment. until the moment of your firstpublishing time, you're free
to assemble your applicationin bits and pieces. nick: so i guess he's askingfor a way to tie that description and everything toa particular release rather than having a-- ellie: we've definitely had somedevelopers ask for that. because they want to be ableto do exactly what he's talking about, prepareeverything and then at one moment, release it as a unit. so we've definitelyheard that.
max: so basically it would beup and ready for new apps. but ones that are published,then they're unfortunately losing that possibility ofediting on the fly without publishing. but yeah. richard: i know when you uploada new application it can take you a couple ofhours to get through to people to see it. if you make content descriptionchanges at the
same time as uploading, do thedescription changes go live in a different time to the apk? or does it all happenat the same time? ellie: it's a good question. ricardo: there's a bit ofcaching and optimizations involved in the pipeline throughwhich from the moment you submit something to themoment it gets live. and that's also something to-- i'm not sure [inaudible].
but there are different groups,there are different bits of information they takebefore they go live. richard: interesting. nick: there's another requesthere on the moderator, so lukas, is that lukas ruecker? richard: ah, lukas has joinedus here as well. nick: ah, do you want toask your question live? richard: hi lukas, thanksfor joining us. lukas: i added a question.
but i thought it would benicer to ask personally. so i know there's something ingoogle play for tracking campaigns and all. so you can know where your newinstalls are coming from. but that involves changesin the app and all. and for indy developers thatdon't have a lot of infrastructure, you need to sendthis with some server. so it's more work when youdon't have time or resources to do it.
so it would be really nice ifthere was some sort of super simple mechanism totrack where new installs are coming from. it could be things, for a start,like tracking what search keywords trigger newinstalls inside the client. so either web or on desktopor the mobile app on the android device. that's one. let's see, maybe which pageopened google play to install
the new app? so that's nice for if you have alanding page, then if you're triggering the installs fromthere, you have some sort of way to gauge that. so that's another one. anyway, just a few ideas. but having a simpler versionof tracking referrers on google play would be useful,especially for people who don't have a lot ofinfrastructure.
ellie: and so this would be likesomething even simpler than integrating googleanalytics? is that kind of whatyou're looking for? lukas: yes-ish? the thing is, so just mypersonal take on that, i usually try to avoid addinggoogle analytics if i don't have a very strong reasonfor doing that. if i can have just a simple wayto track where people are finding the app and installingit, that's fine.
because google analytics takesbandwidth and a lot of data connection costs involvedfor users. so if i can avoid that, iprefer to not add that. ellie: ok. lukas: so it's just maybe asimple mechanism to track where the install came from. and if you want to go furtherin adding your own infrastructure for serviceside, or even google analytics, that'sanother step.
nick: yeah. it's a good idea. for those of you who don't knowwhat lukas is referring to, there is a method at themoment if you're tracking install referrers. if you google for android andreferrer, you'll find a way you can pass particularkind of campaign ids all the way through. so you can track theeffectiveness.
but i agree. there's some work tobe done there. and maybe there's a betterway to automatically service this stuff. so thanks for the feedback. so next question isdaniel in london. is that you, daniel? will it be possible in thefuture for a developer page to show developer details?
and perhaps even integrate withtheir google+ account? so that's a good idea. thank you for the featuresuggestion. and that'll be quick cool. because at the moment, if you goto a developer's page, you just see the list oftheir applications. so it might be nice to havesome blow up there. cool. thanks for the request.
richard: we've got anotherone in the g+ stream from philip madison. he says he would like to be ableto click on the headers of the all application sectionto reorder the listings. to go to the app with the mostdownloads, with the most money, pretty muchall those things. thanks for that. richard: thanks, philip. any more moderators?
nick: yeah, there's a last oneis saying, any plans for better support for proguard? and to easier read your stacktraces when they'll be proguarded? ellie: oh, for native crashes? nick: yeah. well no, justproguarded normal files. if you upload your mapping filefor the apk, so you can decode the stack traces. yeah, native is anotherkettle of fish.
but yeah, thanks forthe feedback. like we said, we're not goingto comment on whether it's coming or not. but thank you for the request. i think we exhaustedthe moderator. richard: running lowon questions now. so we'll wrap it up. but if [? adira, ?] who's justjoined us again, has another question for us, please.
male speaker: yeah, i wroteit on the moderator. but you said that onewas the last one. so i don't know, maybe itdoesn't record mine. i wanted to ask if there willbe a way to reply for users, not developers, to reply likethe developers can reply. i mean when in an app, there aremany apps in google play that the developer hassort of abandoned. and many people withquestions there. you understand whati'm saying?
so they ask questionand there's no way to reply to them. nick: so you want to,as a user, reply to another user's comment? male speaker: yeah. because you can see, forexample, adw launcher, it seems like the developercompletely neglects it. and there are a ton of peoplewith questions there. and no one can answer them.
ricardo: sort of self-supportforum for users of an app. huh, haven't heard thatrequest before. it's interesting. richard: almost turns into acomments thread instead of a-- ellie: yeah, more of a forum. male speaker: yeah, just likeyoutube, for example. you have replies, comments. nick: not sure that's an exampleyou want to emulate. thank you for the feedback.
richard: are you checking theyoutube comments, daniel? any good questionscoming through? daniel: there aremany questions. but none of them are related. richard: and if any of you arewondering throughout this hangout why mine and nick'sheads are so much bigger than everyone else's, it's becausethey're actually beamed in from another studio. and there's a green screenhere and we're just
superimposing. so it's just been fakedinteractions. or we've just got big heads. male speaker: i have a questionthat's not exactly related if you don't mind. it's about the market, the play,but not the developers. in the market, there was a wayto download more than one app. since you updated to play, itdownloads one at a time. so if you're downloadinglike a one
gigabyte, it takes forever. and the other one don'tdownload until the first ones finish. richard: it's interesting. hadn't noticed thatit switched over. you mean before-- do you knowhow many would downloaded at the time before? was it just two at a time? male speaker: no,indefinitely.
you have, like, 50 updates, ido update all, and they all download at once. richard: and now it'sdone serially instead of in parallel. male speaker: they were doingit together, simultaneously, but slower speed. but in general, overallit was faster than just one at a time. richard: i guess the problemwith that is you end up--
i don't know what the actualproblem was-- but you could end up with five apps finishingat the same time, and then trying to install. so the installer stillhas to stack them one after the other. because you can only beinstalling one app at a time. but i didn't know thathad happened. male speaker: it used to be oneof the up points against ios that i used touse for people.
but now ios-- nick: update all all the time. richard: and just for it. male speaker: because now iosdoes have this ability. and android does not. so it's kind of annoying. ellie: well, you're going tobe limited by your download bandwidth probablyanyway, right? male speaker: it doesn'treally matter.
for example, me, i have 100megabits per second. so nothing's goingto slow it down. you guys are going to give usone gigabit sometime soon. richard: if you're in kansas. ellie: only in kansas. richard: three clicks. male speaker: yeah, eventuallywe'll reach worldwide, i hope. well, i'd like to thank thegpdc, google play developer console preview teamfor joining us from
wherever they are at. i don't know where that is, ina magic office somewhere. and thank you foryour questions. we'll see you wednesday, 2:00pm uk time, 3:00 pm cet for our office hours. nick: join me and romannurik tomorrow for android design in action. we'll be talking about whatyour android design needs.
richard: please do.
android design is very importantto all of us. thank you very much. nick: thanks and bye.
