I was lucky enough to be present at the Google Solve For India – Kolkata Event (Roadshow). Enjoyed the event a lot, met with many interesting people, and most important learned a lot of things. Due to my habit I kept taking notes during the talks, and after returning home created a google doc with the gist of the talks. Lateer I thought why not share it, so that those people who were not able to be present at the event can have a look at this and may be benefited.
Note, Disclaimer There were a lot more discussions and talks than the note below. There was two tracks for the event 1. Mobile and 2. Cloud, and I was only at Mobile track, so the note below. It is my personal note, so it may miss something, to be very specific I noted only those points that I felt of.
This note is not a substitute of the event/talks in any way. This note only reflects my understanding on the event.
Soham Mondal (@s0h4m) – Design (bit.ly/design_for_india)
- Compatibility – Use low-end phones to build and test the app
- Most of the phones in India are low-end in 3K-10K range, even with broken screen.
- Connectivity – Consider Offline 1st instead of Offline Support
- Use Posters
- Share Offline feature (Bluetooth. Whatsapp and other social share)
- Regional Design & Language Support
- Content and Commerce
- Consider Android Instant Apps
- Usability Test – (Think Aloud Testing)
Jadeja Dushyantsinh (@JadejaDA) – Build for Billion (PWA)
- 3.2 Bl. Internet Users Worldwide
- Progressive Web Apps
- Web – ServiceWorker – Servers
- WebApp Manifest
- PWA Codelab: http://g.co/codelabs/pwa
- Example PWA – airhorner.com, flipcart light, housing.com
- Cache data
Amrit Sanjeev (@amsanjeev) – Build for Billion (Apps)
- Optimise Battery Usage (Measure Battery regularly while developing)
- Test 1st, Media Later
- Test on Airplane Mode
- Cost of App includes Data Costs (So no app is actually free)
- Background Processing
- Firebase Job Dispatcher
- Doze Mode – (2 min internet window will be given to apps after each 15 min no-internet break)
- Offline 1st
- Think Partial Loading (Pagination)
- Call to Action – (Don’t show a dumb dialog that says “No Internet Connection”, there should be a call to action).
- Low Data Broadcast – When a device runs out of Space it broadcasts low data, listen to it and free up caches by yourself before user uninstalls your app to free up device space).
- Adaptive Behaviour
- Listen to Battery (Dont start downloading 10MB data/image when battery is at 10%).
- Collect Data about users (Analytics) to further optimise your app and boost performance as well
- Consider Language Support (Take help from GDGs to add language support to your app)
- APK Size
- Target should be less than 10MB
- Try to make it below 5MB
- Consider Multi-APK to reduce APK size when supporting multiple screen sizes
- Update Cycles
- App Update Cycles should be 6~8 Weeks (Don’t push an update to your app every alternate week)
- Use Remote Config for regular cosmetic changes
- Force Update should only be used for Security Concerns
- Remote Config is not a substitute of App Update, but an useful stuff to avoid update for example when you’re considering update just for a icon change (Say the tri-color icon of cars in Uber during Independence Day).
- Identity != Authentication
- Use Google Smart lock to reduce Login Flow (even to just remove Login Screen in some cases).
- Use Google Smart Lock for single click Signup.
Jadeja Dushyantsinh (@JadejaDA) – api.ai
- Build with API.AI, take the challenge
- Flow could be Linear or Non-Linear
- Create Intent (Action)
- Create Entities (Pre-Configured Inputs)
- sys.any (for anonymous inputs)
Also published on Medium.