Android Anti patterns

The common mistakes made by app developers and a list of what should not be done.

Transcript

1. Android Anti-Patterns Abhishek Nandi
2. User Identity Using Device Identifiers Getting All Email IDs Not considering multiple device logins MAC ID ANDROID ID with GET_ACCOUNTS permission accidentally taking work emails providing logout ? removing associated devices after user logs out not providing an update email option Lets take everything Phone Number, Email Id Do you really need them ?
3. Unwanted Stuff Is it really needed ? Its just another Java application Using a lot of libs even if you don’t really need it Using GCM & HTTP for creating Chat Applications Unwanted permissions Long running background services TASKS permission Really, HTTP ? Do you need them all ? Using java mail jars to compose email in background Frequent Polling Using reflection for non-public APIs A food delivery app asking for bluetooth permissions I need Butterknife, GreenDAO, Retrofit, Dagger A Travel app asking for READ_LOGS Everyone wants a BOOT_COMPLETED receiver Using old jars and not updating them Everyone thinks its just one call A Banking app tracking user location
4. Wrong Engagement Sending Notifications at the wrong time Sending too many pushes Irritating sounds Using all channels for a single communication That strange “Getting Stalked” feeling Improper deep links Treating all users in the same way
5. Replicating Analytics Data • Tracking wrong events • Sending same events to all platforms, like GA, Flurry, Localytics • Not utilising the platform completely
6. “User experience matters more than design” iPhone like design Over Customising Notification Layouts Grouping items under the wrong section Trying landscape images for mobile devices in InApps Portrait only apps for tablets Not thinking about Back Stack Navigation Neglecting Touch Feedbacks/clicked states
7. Thank You