Development app not to know these 20 problems, must become a disaster

The rapid growth of the mobile economy has greatly stimulated the enthusiasm of enterprise and individual app development, from selling wild pheasant to selling drones, from old aunt to small positive, not to mention the information executives of traditional enterprises.

Faced with today's Awash app market, few people realize that mobile development is actually a huge "pit", with real challenges coming from the development phase of demand changes, product rollout iterations, various tweaks in app operations, and how to support the requirements of various promotional channels. Before you start developing your app, whether you have a ready-made development team or are ready to outsource, you should ask yourself the following 20 questions:

1. On which platforms are you going to publish? Do you have a plan? does the recent versions of Ios/android need to be compatible? In addition to publishing iOS app, Android app, should also be published as app H5app? Baidu light application, such as various cloud platform, it is not released? In addition, H5 app is becoming more and more mainstream because it is extremely convenient and technology matures, are you also going to publish? A variety of platforms, do you choose to deploy a single development, or choose to separate development separately? If you develop separately, are you aware of the heavy workload of the subsequent workloads?

2. Do you plan the environment for back-end services? is the server Java EE or. NET or PHP or other? is the database fixed in one way or may there be multiple? Are all kinds of back-end technologies supported? In addition, is the back-end server Linux or Windows? Have you considered the cost of server hosting or cloud server? Your requirements need to be understood by the software team and the development engineer in advance.

3. Is the requirements document clearly written? what are the core features of the app? The more clearly the functional and non-functional requirements of the product are described, the better the efficiency and controllability of the outsourced development can be greatly improved.

is the decision structure for 4.APP products/projects clear? who is the ultimate decision maker? If there is more than one decision maker in the app design and development process, who is the final decider?

5. Have you thoroughly scoured and analyzed your app's potentially competitive offerings?

6. Do you want to make the profit model clear? Do you have a realizable plan? is there a charge for app downloads? Do you use subscription mode? Do you support in-app ads? Do you support in-app purchases?

7. What are the key metrics for your app's success for your stakeholders? is the number of users, order growth? Do you need to integrate analytics into your app to measure results?

8. Do you have a budget plan? Do you know how to control the budget? app development costs are difficult to estimate, but there are too many variables, but there is a rough budget plan that allows developers to implement key features while avoiding overspending, or completing the highest-priority, most important product features within a budget. The main cost of app development is labor costs, and most of the app development budget overruns are rooted in the labor-intensive overruns caused by demand changes; you'd better choose a mature rapid development framework such as WEX5 to achieve the best demand change response with minimal human input.

9. have you considered the investment protection of app development? does the app have to be completely overturned and re-developed after a year when existing apps don't meet the app? It depends on whether your technical architecture choice has enough scalability and is open enough to support a variety of unknown needs?

10. Where are your target users? is your app ready to meet the needs of the target users or solve any problems? Why use the app to solve? What systems and platforms are used by your target users? Did you conduct user research before designing or developing your app?

11. Have you already implemented an app or company brand (logo, color theme, font, etc.)?

12. What are the project risks you foresee? anticipating and discussing project risks with developers helps developers develop low-risk plans.

13. Do you know anything about the security requirements of the app? What sensitive data does your app collect, and is it stored securely? Most app development companies can work with customers to negotiate the best security solution for your product.

14. Can you articulate your ideas and business models to the development team in plain-easy words?

15. What is the business goal of your app? is it to increase sales or enhance the competitive advantage of enterprises? Or is it more productive?

16. Are there any ready-made products that can inspire or reference you on the market? using the finished product as a reference can improve the accuracy and speed of demand analysis.

17. Do you draw a wireframe of the app product? have you got a technical background to help you see the wireframes? Are all the features you need to be implemented on the target platform?

18. Have you made the product visual design? After you've finished the wireframe you can look for a designer to draw the UI interface, but if you don't have any product visual design on your own, most app development companies can provide user experience and visual design services.

do I need technical support after 19.APP release? Most app development companies provide app debugging and improvement services after the app is released, but the technical framework used is the most important factor in determining whether the app's follow-up support can actually be implemented in place or not, and whether it has an active developer community. If there is not a sufficiently active developer community behind the app's framework, the app's technical maintainers are very prone to suspended and fall into trouble finding people to support them.

20. Are you sure what external API services need to be called or consolidated? It is once again important to adopt a mature technology architecture that is mainstream in the industry. Because, whether it is the existing external API or the future of the new API services, will be actively compatible with these industry's most common technical framework, which will virtually prevent your future a lot of trouble. For example, PhoneGap and Bootstrap, these technical architectures are the de facto industry app standards.

Development app does not know these 20 problems, must become a disaster