Guys, the folder structure is normal for gradle android projects.<p>I like this project, because it combines appengine, cloudstorage, android & android wear all together.<p>As you can see it also has a server component which reads the .json files from cloud storage of updated schedules. At least that is what i understand from it after looking around for 5 minutes.<p>It also contains a GCM (cloud messasing) implementation.<p>All in all, its a very cool that google open sourced this.
The best part is the build.gradle files. They clearly show how to setup debug and release builds , multiple flavours , annotation pre-processing, multiple apks, etc. Something that took me 2 days to import my project from eclipse to studio. Very handy for all app developers who want to switch to gradle. Also, be sure not to release any app build with SDK v21 as it would be rejected by Google play.
I'm a bit disappointed there are no tests. I've always wondered how Google handles testing on internal Android projects (especially since it's a bit of a sore spot for Android [1]). It would've been great to see a "real world", official example.<p>[1] <a href="https://github.com/JakeWharton/gradle-android-test-plugin#deprecated" rel="nofollow">https://github.com/JakeWharton/gradle-android-test-plugin#de...</a>
Quite interesting to see that Google released it on Github rather than using Google code hosting like they've done in the past [1].<p>[1] <a href="https://code.google.com/p/iosched/" rel="nofollow">https://code.google.com/p/iosched/</a> IO 2013 app.
Am I the only one who finds the layout of the Android app extremely complicated? Folders upon folders, how can you make your head around the various parts?