Good rules for bad apps

Download Good rules for bad apps

Post on 09-Apr-2017

3.505 views

Category:

Mobile

0 download

Embed Size (px)

TRANSCRIPT

<p>GOOD RULESBAD APPSfor</p> <p>SHEM MAGNEZI@shemag8 shem8.github.com</p> <p>GOOD</p> <p>BAD</p> <p>vs </p> <p>Why?Imagine how boring was the Batman movies without the Joker. We need those bad things to give us a perspective about the good things.The internet is full of how make to make things right but you cant really tell when youre doing a bad thing.For example- google suggests using Activties and Fragments, but dont really explain what goes where.They give you bitmaps and then you realize that you are leaking memory.Nobody is taking about the dark side, and why not?Were doing mistakes, a lot, and we probably keep going to do them, so lets share and learn.</p> <p>What is a good app?</p> <p>BEFORE WE BEGIN</p> <p>There are MANY bad rules</p> <p>Its not ALL or NOTHING</p> <p>Rules depends on TIME &amp; PLACE</p> <p>There is no PRIORITY</p> <p>Ask as MANY PERMISSIONS as POSSIBLE</p> <p>1.</p> <p>#1 Ask as many permission as possibleYou know what your app worth, dont let minor things like user privacy get down your way. The user is begging for this crucial analytics sending on boot, so go and ask that BOOT_COMPLETED permission! If you need to share this wonderful url to your users friends- pull the fucking contact list from his phone, and while you doing so why not sending it to your server and spam them all? Remember- data is power, and others data is money!</p> <p>Bonus point: when implement Android M permissions, dont let the user do anything until he or she accept your permission, even if he accepted some, dont let him win!</p> <p>Dont handle LOADING2.</p> <p>#1 Ask as many permission as possibleYou know what your app worth, dont let minor things like user privacy get down your way. The user is begging for this crucial analytics sending on boot, so go and ask that BOOT_COMPLETED permission! If you need to share this wonderful url to your users friends- pull the fucking contact list from his phone, and while you doing so why not sending it to your server and spam them all? Remember- data is power, and others data is money!</p> <p>Bonus point: when implement Android M permissions, dont let the user do anything until he or she accept your permission, even if he accepted some, dont let him win!</p> <p>Dont save SCREEN STATE</p> <p>3.</p> <p>#4 Dont save activity or fragment stateYou snooze you lose, you rotated the screen? Boom- your form was lost. This is the best way to teach your users never leave your app, even if them just got a phone call.Tip: use id for your view to save text</p> <p>Dont use VECTORS</p> <p>4.</p> <p>#9: Use gifs instead of drawing things in code or animation drawableYes, I know, animation drawable might saves you a couple of MB, but your time is much more important!#10: Create resources for all resolutionsBecause you just saves time, so lets waste it.</p> <p>Ignore MATERIAL DESIGN specs</p> <p>5.</p> <p>#1: Ignore material design guidelinesGoogle, one of the greatest companies in the world, put lots of efforts creating material design, they probably do a long user research and gather feedback from many expert, but hey- you are the one with the bachelor of industrial design, so you probably know better.</p> <p>Create INTRO, OVERLAY and HINTS</p> <p>6.</p> <p>#5: Create intro, overlay explanations AND hintsBecause users are stupid (mostly true) and they always read your explanation (no chance ever)Bonus points: do a step-by-step tutorial with no option to skip.</p> <p>Mysterious ICONS</p> <p>7.</p> <p>#3: Create a mysterious app icon</p> <p>App that let you send Yo, of course.Thats really helpful when users need to quickly find your app from 40 apps icons grid.#4: Use your own ideas for iconsNow Im talking about in app icons. I understand- you dont fully pleased with the Android default share icon, youre also didnt find anything suits to your needs between hundreds of material design icons so why not creating a full icon pack from your own?Bonus points: dont even bother to add title to your menu items, so that users will able to get a textual hint.</p> <p>Put ANIMATIONS everywhere8.</p> <p>#8: Put animations everywhereA splash screen animation is nice, even Google recommend adding animation while moving between screens, and the more the merrier</p> <p>Support the OLDEST ANDROID VERSION</p> <p>Im not going to GIVE UP on those users!!!9.</p> <p>#5: Support the oldest android versionBecause why not? youre not the one the writing the code. And every user count! also those 0.8% of the users that still using 2.2, although those devices are so weak that your 42MB app probably cant even run on them.</p> <p>Dont use A/B TESTING</p> <p>10.</p> <p>#3: Trust you instincts, no A/B testing or data analysingBecause you are the PM and you know what your users want, and this should CTA button should absolutely be green. Or red. Whatever.Bonus points: change your opinion regularly and randomly.</p> <p>Listen to EVERY single FEEDBACK</p> <p>11.</p> <p>#2: Listen to every single feedback and implement itWorrying that you implemented all your 492 items from your backlog and the ideas are about to run out? Go over all the store reviews, search some feedback in twitter and check all the posts in your beta group. Users are very demanding creatures and probably will keep whining about all those features that your app absolutely garbage without, yes even if it isnt the core of the app or they can do it easily with other apps.</p> <p>PermissionsLoadingActivity stateVector drawableMin SDKA/B testingPrioritizefeedbacksMaterial designIconsOnboardingAnimationsTECHUI/UXPRODUCT</p> <p>THE FULL LISTshem8.github.com</p> <p>FEEDBACK&amp; slides</p> <p>QUESTIONS?@shemag8 shem8.github.com</p>