A step-by-step guide to mobile application development strategy
- 5. Here are some of the most obvious reasons why: Varying business needs and requirements Unique user/customer base Differing budget capabilities Unequal user experience and Quality control requirements Differing technology philosphies and ideologies
- 6. Native Apps HTML5 Web Apps Hybrid Mobile Apps MEAP/MADP based Native/Hybrid Apps
- 7. Highly graphical Visibility and monitory channel through App store Complete device integration High on performance and security No portability Rapidly evolving platforms Development cost Development time Maintenance overhead Closely controlled and monitored ecosystem Niche skill-set Future proof Cross-platform Budget-friendly development cost Single code Ease of maintenance Instant updates Relatively open ecosystem Minimal device integration Limited graphics Fragmented implementation of features Relatively slow and inconsistent performance Close to native look and feel Moderate device integration Visibility through App store distribution Budget-friendly development cost Limited graphics Fragmented implementation of features Inconsistent performance Steep learning curve for mobile frameworks Framework-level dependencies Native look and feel Good performance Great device integration App store distribution Single code base Vendor lock/ restrictions High-dependency on platform to support major industry upgrades Not budget- friendly Moderate Learning curve
- 8. Business-level factors: 1. Needs and requirements 2. Budget allocation 3. Target audience 4. User experience acceptance criteria 5. Expected release deadlines Engineering-level factors: 1. Technology mission and roadmap 2. Available skill set 3. Quality control requirements 4. Security and Performance criteria 5. Size of data and volume of user base 6. Frequency of upgrade and scaling 7. Frequency of release 8. Access to and use of device features
- 9. SYMBOLS USED MEANING CONVEYED ALL SAFE In this scenario, any of the options can be safely used. Hence no elimination. CAUTION! There is a note of caution. You can proceed at your own risk. DANGER ZONE! In this scenario, this option should not be used failing which one might end up in a very sticky situation. CASE STUDY A sample case study to help you relate and take cues from.
- 10. 1. What is the complexity of the requirements? Simple Complex Average
- 11. 2. What is the User interface requirements and its acceptance criteria? Simple Absolutely Stunning Sleek and good looking
- 12. 3. What is the Budget allocated for the app? Low Loads of Money Moderate
- 13. 4. Who is the app targeted at? B2B C2C B2C
- 14. 5. What is the application genre? Productivity Games & Entertainment Social Networking
- 15. 6. What are the platforms targeted? Single/ Dual Platforms Cross Platform 2+ Platforms
- 16. 7. How secured is the app and its data expected to be? No Security requirements Strictly secured Minimal security
- 17. 8. What is the extent of usage of device features? No device features Intensive use Of device features Minimal Features
- 18. 9. What is the company’s technology mission and road map? Minimal risk taking with technology Actively adopt and embrace upcoming and evolving technology Good adoption to fully- functional technology
- 19. 10. What is the frequency of upgrades/ code push? Minimal change Frequent/daily updates Moderate Change frequency
- 20. 11. How urgent are your “out-to-market” deadlines? No immediate deadlines Rapid and tight deadlines Moderately quick development
- 21. 12. What volume of data and user base you foresee? Minimal Data & user base Huge data sets and intensive user base Moderate Data and User base
- 22. 1 - 2 2 - 4 > 4 > 2 1 - 2 If is greater than 4 or => If is greater than 2
- 24. .
Editor's Notes
- #2: A very good afternoon to one and all. I am Nithya from India here to deliver a presentation on structured approach to choosing one’s mobile app development strategy.
- #3: Now quickly – The motive behind choosing this topic. Today if the entire world is united in following that one trend it is most certainly “Go Mobile”.
- #4: And I think it is totally justified in the fact that Apps are almost literally “omnipresent” these days. From the very moment you wake up in the morning with soothing alarm of beautiful sounds of nature to the minute you go to sleep in the night after reading skimming your favorite e-magazine or finishing up your book on the e-book apps like kindle, mobile apps have penetrated into everyone’s life so deeply and meaningfully.
- #5: Ok, now that one realizes the reach and potential of mobile apps and decides he’s going exploit it to the fullest extent possible for his business, he is lost in the plethora of options available out there not knowing which way to go.
- #6: Typically, deriving inspiration from success stories appears to be the safest solution. For instance, take our very own competitor or another business in the same domain and watch closely and analyze his mobile app development strategy. Common assumption – If a mobile app development strategy works great for a company A, what are the chances it wouldn’t work for me? Ground reality – Good luck with that! Because that’s not how the mobile space works. And why is that so? Because every business is unique in its own way and this strategy has to be molded and shaped exactly in accordance with your business. Some of the obvious reasons include – Varying business needs and requirements, unique customer base, differing budget capabilities, unique user experience expectations and finally differing technology philosophies and ideologies.