419
420

[APK] Google I/O 2015 (apkmirror.com)

iwantatrophyBlue が 投稿

全 92 件のコメント
並べ替え:
ベスト
トップ新着論争中古い順q&a

[–]samewaterbottle 56 ポイント57 ポイント  (36子コメント)

It's a really well designed and beautiful app.

[–]LazyCouchPotatoNexus 4 | Android 5.1 | Euphoria ROM 54 ポイント55 ポイント  (32子コメント)

Why can't the rest of the Google apps be like this, following the guidelines correctly, having animations and having some neat artwork?

[–]vectorzulu 74 ポイント75 ポイント  (14子コメント)

Because this is a relatively simple app.

Apps like Hangouts and Youtube already have a very complex backend. Improving those apps would require a lot of back and forth between different teams.

[–]atb1183OPO 64GB on CM11S - viva la kitkat 32 ポイント33 ポイント  (2子コメント)

If Google can't be expected to produce high quality material design apps that follow their own guidelines after nearly a year then how can we expect faster conversion of third parties?

That's the problem with this ecosystem compared to iOS.

And then there's those defending Google with arguments such as "it's a big product/company". What everyone should be doing is ridiculing and criticising Google in mass media until quality improves.

[–]velkro16Galaxy Note 4, HTC One M8, Nexus 7 2013, Galaxy Note Pro 12.2 6 ポイント7 ポイント  (0子コメント)

Agreed. So many excuses are made for Google and it's only hurting them and us in the long run.

[–]caliber 2 ポイント3 ポイント  (0子コメント)

Especially when apps like Hangouts fail in the most basic things, like support for a tablet layout (which has already been present on the iOS version for a long time).

[–]eponabestponyHTC M8 GPE/Nexus 9/ Sony Z3 Tablet 7 ポイント8 ポイント  (0子コメント)

That is implying Google doesn't just have a sticker artist and a record label working on those two.

[–]NEDM64 -1 ポイント0 ポイント  (0子コメント)

In case you don't know, Android Apps have a separation between presentation and the underlying logic. They can easily re-skin the App from day to night.

The problem tough, is that Google isn't an amateur company.

They will have a lot of bureaucracy to do, like tech support manuals...

[–]slackrboi 6 ポイント7 ポイント  (5子コメント)

The app looks pretty and does seem to follow material design guidelines. Scrolling is good too.

However, I don't see any animation or nice material transitions. The navigation drawer is laggy just like all other Google apps.

[–]d_thinkerNexus 4, 10/10 Stock, Praise Duarte 8 ポイント9 ポイント  (4子コメント)

They are not doing it right. I've looked code from the last years IO app and this one has the same base, and one bug is here for a year now, nobody cares. I mean its not a bug, It won't crash the app, but it is really annoying and google needs to show people how android apps can be smooth if done right and they are doing exact opposite with their laziness.

Bug is: if you select settings from drawer it stutters, thats really easy to fix, even I do it in my apps, but they don't care, or they are blind. As I said I've read the code and I see they did some effort for other drawer items (they start to stutter near the end because they hardcoded like after x amount of milliseconds start doing stuff, but animation is not done when that happens thats bad practice imo, it should be, when drawer is closed, do stuff, it is slower but doesnt lag). It can't be that I know more then they do, I've been doing this for a few months and I pay special attention to make apps as smooth as possible.

Funny thing though: If you enable Strict mode from developers option (screen gets red frame when doing too much work on UI thread) only google apps make it turn red out of all apps I use on my phone, really sad.

tl;dr Google devs are blind or assholes or lazy or any combination.

[–]slackrboi 4 ポイント5 ポイント  (3子コメント)

Wow, I just enabled this Strict mode on my Nexus 5, and all I have to say is OMFG. Of all the apps on my phone only Google apps make the screen flash red when firing them up. Not even Facebook does that which is, IMO, one of the worst Android apps. Google Play Music, Store, Play Movies, Drive, Docs, Sheets, Slides, Maps and Chrome are the worst. I just cannot believe my eyes. And, I am not talking about the jankiness in almost all of their apps. The navigation drawer implementation in almost of their apps is far from even OK. Frames constantly drop when navigating between different parts of drawer. The only apps which seem have relatively better implementation are YouTube and Keep. Some third party apps (for example "Relay for Reddit") have miles better implementation of Navigation Drawer than Google's own apps. The so called material transitions and animations in Google Play Newsstand and Play Games are not even remotely smooth and visually just plain jarring. And don't even talk about inconsistencies in visual design between their apps.

I wonder whether or not Google's Android apps team even has a QA/QC department. Don't they test their apps in terms of performance before making them available for consumption. Most of well known Google apps are first party apps which come pre-installed on almost all of the Android devices. They should set the performance and design benchmark for rest of the third party developers. Whereas on the contrary, the complete opposite is true. Even simple app such this IO15 can't perform without dropping frames. I honestly think it should be the app that everyone should look up to when developing Material Design app. All they have done here is just put the new colored lipstick on the same pig. :-(

Don't get me wrong Android has come a long way from its early days, but performance wise it still leaves something to be desired. I love its openness and awesome feature set. My wife has an iPhone 5 which does seem slower than my Nexus 5,but doesn't feel rough around the edges. The UI is very smooth and animations almost always run at 60fps. Even Google apps on iOS perform way better than their Android counterpart. I know it has something to do with difference in internal architecture. But, it is 2015 and Google must iron out these wrinkles which have been plaguing android and its apps since forever. Google has been talking about performance boost in Android since Jelly Bean but it's still not there yet. I don't want to go to the dark side but I am loosing patience now!

P.S. Sorry about my long rant. But, I had to say it because Android is my preferred platform and I want it to be better in terms of performance and smoothness.

[–]d_thinkerNexus 4, 10/10 Stock, Praise Duarte 1 ポイント2 ポイント  (2子コメント)

The only apps which seem have relatively better implementation are YouTube and Keep.

Yeah, Keep does it the way I think is a good practice. (but don't try to scroll fast through reminders with strict mode enabled)

In my opinion I'll always vote for 60fps experience over speed. It can be done at the same time, but if people at google struggle, just make your animation wait.

As I said, I'm relatively new to programming and the more I know the more frustrated I get. Like the lack of ripples in every app especially Hangouts.

<ripple android:color="@android:color/darker_gray"/>

This is all you need to get ripple, 2 lines of code, one for this xml and other to assign this as background to the button/element you want to make ripple on. (Ok, maybe some mask, but thats like 5 additional lines of code if needed)

I mean, is it so hard to do that? Is it against the guidelines? NO!

That thing with strict mode shows that google devs use UI thread to do heavy tasks and that is like Android development 101 lesson, not to lock the UI thread. If you do you get those little stutters that make my brain melt.

I am not an expert, not even close and even I can see that there is something really wrong with google apps code in general.

I can rant here whole night about little issues I have with every google app that can be fixed in like 10 minutes if devs cared enough but the point is:

It can be done well, android can perform well, there is a ton of apps that are well designed and follow material design guidelines better than google apps, its just that google devs doesn't seem to care enough.

EDIT: Have you tried Drive with strict mode on? Beware, flashing images might cause seasures.

[–]slackrboi 2 ポイント3 ポイント  (1子コメント)

Ya I remember Chet Haase, their UI Toolkit Lead, talk about not loading the main thread too much at last year IO's what's new in Android. I am pretty sure there is a serious disconnect between Google Android apps devs and Apps testing team, if such a team really does exist. In that same talk Cher also talked about a new system wide Renderthread which was supposed to take care of all Material animations and transitions and make them run smoothly. Now I am not a developer so I don't have a deep knowledge of these programming jargons. Can anyone confirm if such a thing exist, because animations are still not smooth?

[–]d_thinkerNexus 4, 10/10 Stock, Praise Duarte 0 ポイント1 ポイント  (0子コメント)

A new system-managed processing thread called RenderThread keeps animations smooth even when there are delays in the main UI thread.

Source: https://developer.android.com/about/versions/lollipop.html

Can't find any documentation about how it works though. From what I've seen I think its supposed to work on its own without any developer interaction.

[–]johnghanksN1 GT10.1 GN N4 N7 N7(2013) MX 17 ポイント18 ポイント  (7子コメント)

"why can't feature x be in product y"

because that's not how software development works. It's not one team working on one product at the same time until completion. It's different teams working on different parts of different products at different times.

Maybe the UI team prioritized this over, say, Hangouts. Maybe the IO Team UI Team is more versed/aligned with the Material specs. Maybe... etc.

[–]konk3r 5 ポイント6 ポイント  (6子コメント)

Still, if Google is going to set guidelines for the apps we build on their systems they should enforce them on updates to their internal apps.

[–]ronakgGalaxy S6 | 32GB | T-Mobile -5 ポイント-4 ポイント  (1子コメント)

You can't use guidelines and enforce in the same sentence.

[–]konk3r 5 ポイント6 ポイント  (0子コメント)

Sure you can. If Google wants to start getting developers to start following their guidelines, they should enforce them internally. They are guidelines for apps added to the store, but if Google wants to see them actually followed they can force their internal apps to follow them to set an example of proper app development.

Very least they could at least do a better job with their internal apps at starting with the guidelines to show how you can follow the guidelines while bending some of the them to personalize an app.

[–]johnghanksN1 GT10.1 GN N4 N7 N7(2013) MX -5 ポイント-4 ポイント  (3子コメント)

No, it comes down to Google is an organization which employs, literally, tens of thousands of people. The person or team who wrote IO may never meet the person or team who wrote Hangouts, etc. They are completely different people or teams with different skills and different visions.

Just let it be.

[–]redditisforfags3 6 ポイント7 ポイント  (0子コメント)

Let it be? Are you kidding me? I'm supposed to be charitable to a multi-billion dollar multinational corporation like they're an eight-year-old that tried really hard at their little league game?

That's insane.

[–]konk3r 2 ポイント3 ポイント  (1子コメント)

Yes, tens of thousands of people, a small percentage of which are Android developers, and all it takes is for someone high up in the android side of things to say, "Hey, all teams working on Android need to heavily focus on matching the design guidelines to make sure we are setting the bar high" for all the separate teams to have to move in that direction.

Amazon has pulled off much harder feats of unifying the products of their development teams, I guarantee that Google could do this small thing while not treating their employees like shit or creating unfair demands.

[–]johnghanksN1 GT10.1 GN N4 N7 N7(2013) MX 0 ポイント1 ポイント  (0子コメント)

Really, though compared to other apps, the bar is set high with most Google Material apps.

[–]anthonyvardizAMA Coordinator | Nexus 6/OnePlus One 2 ポイント3 ポイント  (0子コメント)

Yes basically what /u/Natanael_L said. This app needs to follow the latest design guidelines to a T so developers can use the code to improve their own apps to the latest design language.

[–]samewaterbottle 3 ポイント4 ポイント  (0子コメント)

I think what other users are saying is pretty true. Also, I feel Google has a bit of ADD, it doesn't focus on what's been done, like what products it releases and support for it. Case and point Nexus 6, Android One, Nexus 9. Instead Google starts on a new project right away. Project Fi, releasing new apps and developing more, instead of properly updating existing apps and services. They have a lot to do and not the focus to do everything properly. Apple doesn't have much to do compared to Google's size and they release their products slow and thought out properly. Google does stuff and thinks about it later.

[–]Natanael_LS4 Active GT-i9295 & Tab Pro 8.4" SM-T320, stock with Xposed 0 ポイント1 ポイント  (0子コメント)

Effort

[–]PowerLemonsPlusApps Developer - BrightNotes 6 ポイント7 ポイント  (1子コメント)

Doesn't look amazing in my opinion. It looks more like a simple reskin of the IO 2014 app, and was changed for the sake of change - like a lot of Google's other apps.

But this is a recent update, and I'm looking forward into seeing what Google does with this app. I'll be disappointed if Google doesn't update this with impressive features however, as this app should be a showcase of what Google has in store for Android developers.

[–]slackrboi -2 ポイント-1 ポイント  (0子コメント)

This! I am talking about.

[–]ProfessorOakTreeHTC One (M7) 2 ポイント3 ポイント  (0子コメント)

It's meh. This is something I would expect from a very small team, not from Google.

  • They should have showed off their new Shared Element APIs to animate the thumbnail into the larger header image when you click on an item.
  • Their status bar is not dark enough, you can barely tell the difference between it and the toolbar.
  • If they are going to use people's Google account background image in the drawer, they should've done something about light backgrounds. Either do a floor fade or a scrim. I have a lighter background and I can barely read the text.

If anyone is interested in a beautiful app, you should check out Inbox. It is the epitome of Material Design imo.

[–]LaceratedCantaloupeOnePlus One 64GB - Rooted Cyanogen OS 12 10 ポイント11 ポイント  (2子コメント)

What the hell is going on with the top bar? It doesn't scroll with the rest of the page like every other app does, but moves at one speed and turns the status bar black.

[–]wallflyersOne M8 (GPE), 5.1; Nexus 7 (2013), 5.1 4 ポイント5 ポイント  (1子コメント)

Yeah, I hate this in apps like Google Plus. Why can't all apps do it like Chrome?

[–]LaceratedCantaloupeOnePlus One 64GB - Rooted Cyanogen OS 12 0 ポイント1 ポイント  (0子コメント)

I hadn't even noticed it in Google+. Fortunately I don't use it often, so it shouldn't be too much of a bother.

[–]Thefinalhack 40 ポイント41 ポイント  (12子コメント)

Something of a newcomer to android here, is this basically the equivalent of the WWDC app on Apple devices?

[–]caseyls 49 ポイント50 ポイント  (10子コメント)

Usually it's a scheduling app for Google I/O with a few hidden tidbits (scavenger hunts at the conference, etc), and they often update it during/after google I/O to conform to the latest design guidelines, and then open source it for devs to look around the code afterwards.

[–]clydethefrogMoto G 2013, 5.0 stock | Nexus 7 2012, 4.4.2 stock 55 ポイント56 ポイント  (9子コメント)

The Google I/O app is Google's way of showing off to its developer community. The code for this app is usually godly, follows all best practices and guidelines, uses the latest and greatest APIs that Android supports, and often falls back gracefully to older platforms. For any Android developer, this is Mecca. If you're confused on how to do something, and you see something similar done in the Google I/O app, get the code, and follow Google's implementation like religion. Study the source, and look at the right way to do things.

https://www.reddit.com/r/Android/comments/vb4n9/official_google_io_2012_app_now_in_the_play_store/c5309v8

[–]anthonyvardizAMA Coordinator | Nexus 6/OnePlus One 15 ポイント16 ポイント  (7子コメント)

This makes sense. The app is the epitome of Material Design. All it's lacking is a dark theme.

[–]need_tts 15 ポイント16 ポイント  (2子コメント)

The app is the epitome of Material Design

it's lacking is a dark theme

I love android but this sums up the entire ecosystem. Even the absolute best is still sometimes lacking that last bit to make it truly perfect.

[–]anthonyvardizAMA Coordinator | Nexus 6/OnePlus One 3 ポイント4 ポイント  (1子コメント)

Google does provide for Material Dark themes, but they aren't very good at applying it their own apps.

[–]K3fkaAT&T Galaxy S6 Edge 11 ポイント12 ポイント  (0子コメント)

Google does provide for [insert anything here], but they aren't very good at applying it to their own apps.

[–]Kai231Nexus 5 | Android L 5 ポイント6 ポイント  (2子コメント)

And nice animations.

[–]RetepNamenotsNexus 5 & 7 (2013), EE UK 6 ポイント7 ポイント  (1子コメント)

nice animations

Material was never about 'nice' animations, it is about useful/meaningful ones. Quite possibly why we never saw the animated FAB from the original material Google Play Music demo come to fruition.

[–]yodeiu 2 ポイント3 ポイント  (0子コメント)

Not seeing those either

[–]The0x539OPO, CM12, Franco 2 ポイント3 ポイント  (0子コメント)

The status bar seems rather off.

[–]staticfish 0 ポイント1 ポイント  (0子コメント)

I wouldn't agree with that at all. I mean, there weren't even tests in last years app, and this year Google have 2 sessions regarding tests. It might be helpful for a beginner though.

[–]clydethefrogMoto G 2013, 5.0 stock | Nexus 7 2012, 4.4.2 stock 1 ポイント2 ポイント  (0子コメント)

https://www.reddit.com/r/Android/comments/vb4n9/official_google_io_2012_app_now_in_the_play_store/c5309v8

[–]plexistar31 2 ポイント3 ポイント  (0子コメント)

This has more Holo principles than Material principles.

[–]beall49iPhone6+ (work) 2 ポイント3 ポイント  (0子コメント)

One thing that's cool is that the floating button and snackbar (toast replacement) appear to become part of the standard android sdk. This means you're going to see a lot more material design, previously developers had to implement their own. credit to /u/iwantatrophy http://i.imgur.com/FHnNsxV.png

[–]Tweaver9 5 ポイント6 ポイント  (5子コメント)

ELI5 Google I/O. Please..

[–]ownage516Moto X (2014) | Android 5.1 | T-Mobile 11 ポイント12 ポイント  (4子コメント)

Think Apple's WWDC (Apple's keynote) but for Google.

[–]Tweaver9 2 ポイント3 ポイント  (3子コメント)

Oh ok cool. but. why is it an app? ohhhhhhhhhhhhhh. it's like a schedule or something for the conference!

[–]ownage516Moto X (2014) | Android 5.1 | T-Mobile 3 ポイント4 ポイント  (2子コメント)

Basically.

Here's the description that I literally copy and pasted from the google play store:

Description

The official Google I/O 2014 app was built to be your co-pilot to navigate the conference, whether you're attending in-person or remotely.

  • Explore the conference agenda, with details on themes, topics and speakers
  • Add events to a personalized schedule
  • Get reminders before events in “My schedule” start and once they're over, to provide feedback
  • Watch the Keynote and sessions live stream
  • Sync your schedule between all of your devices and the I/O website
  • Guide yourself using the vector-based conference map
  • Follow public social I/O related conversations on Google+
  • See I/O content from previous years in the Video Library
  • Find and connect with Google Developer Experts (GDEs) from around the world
  • Use the Widget to check your upcoming events directly from your home screen
  • Start playing I/O Hunt

For in-person attendees:

  • Take advantage of facilitated pre-event WiFi configuration
  • Scan attendee badges with your NFC-enabled device, registering the Google+ profile and your personal notes on all people you meet during the conference
  • Find more information about things that are Nearby at Moscone This app is optimized for phones and tablets of all shapes and sizes, running Android 4.0 and up. Source code for the app will be available soon at: https://github.com/google/iosched

Available in 9 languages: English, French, Italian, German, Spanish, Chinese (traditional and simplified), Japanese, Korean, Russian.

[–]Tweaver9 -1 ポイント0 ポイント  (1子コメント)

thanks! for some reason I thought it may have been an OS.

[–]ownage516Moto X (2014) | Android 5.1 | T-Mobile 0 ポイント1 ポイント  (0子コメント)

Well they're probably unveiling Android M.

[–]redditrasberry 1 ポイント2 ポイント  (1子コメント)

I'm trying to get excited about I/O this year but I'm really the least interested I've been in it for many years. I really can't think of anything that might come out of it that is likely to change the landscape of technology in any significant way. Am I just jaded and cynical now? Or is there potential for them to surprise us with something really cool that hasn't been leaked or speculated about much?

  • widening scope for project fi?
  • project loon going live world wide
  • brand new wearables that might actually take off?
  • something more than incremental improvements in Android? given the problems with Lollipop I'm almost hoping they just buckle down and focus on quality.

[–]s73v3rSony Xperia Z3 0 ポイント1 ポイント  (0子コメント)

I'm excited cause they finally have some sessions on automated testing, which is something that has been fairly lacking on Android.

[–]Speckknoedel 3 ポイント4 ポイント  (5子コメント)

We all agreed we can trust apkmirror, right? How come? Do they anything to avoid getting hacked apps?

[–]efstajasNexus 6, Nexus 7 13, Moto 360 19 ポイント20 ポイント  (2子コメント)

Apks get cryptographically signed by their maker. You will notice that this apk is legit because it has been production signed by Google. If you download a newer version for an app you already have from the Play Store from apk mirror, it will upgrade without problems. If the apk had been tampered with, it would fail because the signatures don't match.

Also apk mirror is run by Android Police which is a popular news source with lots of reputation to uphold.

[–]Speckknoedel 2 ポイント3 ポイント  (1子コメント)

Thanks for the explanation. Where can I see the signature? Can I make sure I the apps I download haven't been tampered with myself?

[–]BlueShellOPZ3 CM12(want SlimRom) | GS3 SlimKat 2 ポイント3 ポイント  (0子コメント)

On each APK's page there's a couple of hashes (MD5 and SHA1) that you can cross-compare to the official hashes....assuming you knew where to find them. If the hashes match then they're the same file; that's the easiest way to explain.

To be perfectly honest, I only use AKP-mirror top get older versions of Snapchat so I don't have the new discover 'feature'

[–]archon810Android Police 3 ポイント4 ポイント  (1子コメント)

I should make this more obvious, and at some point I will, but all uploads to APK Mirror are carefully examined and manually approved only after we verify the signature matches a previously 100% legitimate version of the same app, or another app from the same developer.

All APKs we've ever published have been official in a sense that they were release versions, with a few exceptions that were heavily documented in the notes section.

The site is indeed run by Android Police, and we do indeed have reputation to uphold.

[–]Speckknoedel 0 ポイント1 ポイント  (0子コメント)

Aha thanks!

[–]Kmann1994 -1 ポイント0 ポイント  (0子コメント)

GODDDDDD I am so excited for the wearable announcements this year. I want a smartwatch sooo badly but I'm waiting for all the Gen 2 announcements. Bring them on!

[–]Redd575 0 ポイント1 ポイント  (4子コメント)

I have seen these every year and have been wondering: what are I/Os and what does the app actually do?

[–]beall49iPhone6+ (work) 1 ポイント2 ポイント  (3子コメント)

It provides a schedule as well as hints towards what's going to happen. Most importantly for developers it usually gives subtile hints about new design directions.

[–]Redd575 0 ポイント1 ポイント  (2子コメント)

So if you do not mind waiting, you lose nothing by just waiting for the full google I/O event?

[–]beall49iPhone6+ (work) 1 ポイント2 ポイント  (1子コメント)

yup

[–]Redd575 1 ポイント2 ポイント  (0子コメント)

Thanks for taking the time to inform.

[–]hozayhandsome 0 ポイント1 ポイント  (0子コメント)

Will the source code be released after Google I/O?