Going mobile - The Design Decisions

581 views

Published on

A check list of design decisions for your mobile development team by Karthikeyan Mani. CEO & Co-founder at ByteAlly
website : http://byteally.com

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
581
On SlideShare
0
From Embeds
0
Number of Embeds
106
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Going mobile - The Design Decisions

  1. 1. GOING MOBILE The Design Decisions
  2. 2. The Developer Dude •Developer must know the Human Interface Guidelines (Time killer) •Platform specific problems are plenty •CONCLUSION : Never allow first timer to develop your mobile app
  3. 3. Native vs Hybrid Dilemma GO NATIVE BE HYBRID •UI/UX is a differentiator •UI/UX not a major differentiator •App is more than a skin with native functionality fat •One code base is a myth •Launching on one platform •Going out early is not crucial •$$$ •Must launch on all platforms •Can’t afford death by launching late •$
  4. 4. The Architecture
  5. 5. Your App must be DUMB •Should just be a skin. •Move functionalities to the server side
  6. 6. HTTP Requests are Costly COSTLIER BATTERY LIFE EFFICIENT /api/place/images /api/place/home /api/place/products {Images, products}
  7. 7. Handle the worst •Incorrect or no response from the server •No required Services (Internet, Camera, Contact, Location etc) •Low Memory
  8. 8. Remotely Configurable App Don’t make your app a brick Examples •Label Messages •Rating form •Default Views •Anything else that would save your a**
  9. 9. Track & Measure Everything •Watch the funnels •Report Crashes •Okay to dedicate most of HTTP request (Battery Life) for measuring during early stages
  10. 10. Yay! We are done Thank you Karthikeyan Mani Co-founder ByteAlly keyan@byteally.com Twitter : keyanmk

×