gdgomsk / devfest-app Goto Github PK

Provide manifest and corresponded json files with real event blocks, themes, topics, types, rooms, colors, known sessions for both days of event.

If in current moment it's no defined talk/speaker for a block, then place stub session in the block.

Stub session should have invitation to become a speaker in description, looks awesome and works as standard sessions in terms of app's mechanic.

Understand do we need a wearable app. If we do, then find a ways to customize it. And fix :wearable project signing config (now it crashes during build from the lack of signing config file).

To understand do we need experts sections or not, first it's necessary to make some json experts data and play with section. Anyway, I think this feature is not important to be included to first app release to Google Play.

• Follow customization docs of IOSched and make basic customization
• Create necessary Google environment and configure sharing options
• Customize app's name and icon

Replace all occurrence of the text San-Francisco to Omsk

Use GDG Logo instead of I/O Logo in ActionBar and all other places.

Replace all occurrence of the text I/O, Google I/O, etc to GDG DevFest Omsk

Implement several docker containers: one for Android app itself, second for emulation of remote manifest storage and static files providers, third for GCM, and so on.

Test environment should has zero dependency from external world for all features under test.

Use Espresso and/or UiAutomation for automation of user actions.

Check slide-out menu items, remove unsuitable items.

Setup custom GCM to handle push notification in app.

Use devfest-omsk-app App Engine application. Full url of application is devfest-omsk-app.appspot.com, also there is configured alias gcm.gdg-devfest-omsk.org.

Inside Android app it's necessary to use alias gcm.gdg-devfest-omsk.org during communication with GCM app.

When running the application displays a alert dialog with text: "This app won't run unless you update Google Play services".

However i have the last version of Google Play services 5.0.89:

Application is closed when you close the alert dialog.

Provide template and easy way of its customization to DevFest in concrete city.

Setup updater at Google App Engine.
It requires some configuration:

• appengine-web.xml
• build.gradle
• Config.java requires a lot of configuration - names, keys, urls, dates, conference data.

@korovyansk i guess we need to create another GAE application for updater. So there will be two apps: updater and gcm server.

Our attendees know only Russian and English, so let's follow KISS and remove all extra locales. Moreover in other locales it can be artifacts that are incorrect and that we cannot check.

Use new animations api from L to implement cute transitions between screens.

Add indoor maps for IMIT OmSU, looks like it's possible through http://www.google.com/maps/about/partners/indoormaps/

Related to #14.

Implement UI and logic for ability to win invites through play with Slot Machine. If random selects three identical numbers, then special invitation code is displaying on the screen. Later user will be able to use this code to guarantee automatic confirmation of his registration to the event.

Display map around OmSU in Map section, instead of Moscone Center West in San Francisco. If it's possible it would be awesome to show plan of levels.

Provide json data for Ignite Session, in its description it should be a link to form for submitting Ignite talk.

Provide cute pics with cats and dogs for session placeholder. Cats for first day, dogs for second.

It's not clear how nearby feature should work. Need to understand it and support this feature if it's suitable for GDG DevFest Omsk, else we need to remove this feature from the app.

Configure necessary stuff to fix feedback feature. Start from here https://github.com/GDGOmsk/devfest-app/blob/develop/android/src/main/java/com/google/samples/apps/iosched/Config.java#L225

Most important place to protect — logic of working with invite codes.