Startup Engineering Cookbook for Mobile Apps
•
80 likes•20,586 views
Do you have a great app idea? Are you a non-technical founder confused about the technology to deploy for your new website? The presentation covers the various options available for building a website and beyond...
Report
Share
Startup Engineering Cookbook for Mobile Apps
- 2. Overview Slide Topic 3 I Have This Great App Idea… 4 The Lean Startup 5 Implementation Options 6-9 Mobile App Design Process 10-14 Mobile App Architecture 15-25 Backend Architecture 26-31 Reference Architecture 32-36 Monitoring 37-38 Disaster Recovery 39-40 Scaling 41-42 Internal Communication 43 Questions?
- 7. Paper Prototype Getting to the final look and feel of an mobile app requires a multi- step process. The first step is understanding what the flow and functionality will be of the mobile app. mobile app paper prototype 7 Our choice: Pencil and paper. It’s free and works surprising well.
- 8. Wireframes Wireframes start to give you an idea of what the mobile app will contain when it comes to information, navigation and interface design. mobile app wireframe tools 8 Our choice: Any of the above + InVision. The ability to share designs and make comments can speed up the design process. Options: Axure, Balsamiq, Flinto, HotGloo, Justinmind, MockFlow, Moqups, Sketch, Solidify and UXPin
- 11. Mobile Phone Platforms There are really only two major mobile platforms that are currently in use – Android and iOS. Other options: Blackberry and Microsoft Windows Phone mobile phone platforms 11 Our choice: Android and iOS. In Asia, Android is more popular but the tastemakers and journalists tend to be on iOS. In the US and Europe you can get away with iOS initially then Android.
- 12. Development Options native hybrid mobile apps 12 Our choice: It Depends. Native development brings a much richer experience but lately React Native is gaining traction for hybrid development.
- 18. Central vs. Distributed The old way of designing the infrastructure for a backend was to put all the resources such as databases, files, images, etc... on the same server. The problem is if your database is slow and everything else is fine, you have to upgrade the entire server and disrupt the other functions. By distributing the resources you can quickly pinpoint the bottleneck and scale that particular resource. distributed web architecture Central Our choice: Distributed Architecture. Distributed Computing Database Static Files Computing, database, files, etc... 18
- 20. Technology Stack The “stack” refers to a set of software components needed to create a complete platform. For a mobile application that includes the operating system, web server, database and programming language. lamp lemp mean 20 Our choice: It depends. Several factors to evaluate include time to market, cost and knowledge of the technology stack. 1 2 3 4 LAMP Stack LEMP Stack MEAN Stack Windows Stack
- 25. An Application Programming Interface (API) is how the front end of the mobile app communicates with the backend to display information to the user. Web Services Architecture Api mobile access 25 Previously Today Future In the late 1990’s, Microsoft released a specification called Simple Object Access Protocol (SOAP). It used Extensible Markup Language (XML) to send data to a requesting endpoint. In the early 2000’s a specification was released called Representational State Transfer (REST). It has become the de facto standard to enable mobile apps to communicate with the backend. It’s commonly referred to as a RESTful API. GraphQL is a new nested query language. It’s an open source standard published by Facebook to enhance the REST specification.