start without planning
start a written plan. Make clear the purpose of developing App and the functions it realizes, and then design a flow chart of user needs. This method effectively avoids the embarrassment of building a home without a blueprint or writing a novel without an outline. You should plan the desired basic structure before starting to create it. This will help to design and build the framework.
before creating a cross-platform App
designing an application, you should conduct a survey among users. Through the investigation, we can understand the age level, education status and living environment of users, so as to judge the proportion of using Android and iOS platforms. There are many reasons for doing this survey, the most important of which is to want more successful applications. Cross-platform applications usually do not have comprehensive functions, and more coding may be needed for each independent platform. However, cross-platform App has one advantage: it can be released quickly in the first platform, and feedback can be obtained from users' actual use, which helps to improve the version released on other platforms.
Ignore the developer's suggestion
The product designer may come up with a good idea and help the sales of this App. However, developers may tell that this idea is not applicable in most mobile devices, or that the implementation of this idea will take up a lot of ordinary user data. If we ignore the developer's suggestions, we may eventually design a poor product, or users may delete applications because of excessive data traffic costs. Although designers may have some correct groundbreaking new ideas, reality will make them come true. If the design is really clever, see if you can patent the idea, and when the technology is feasible, you can implement the idea.
trying to turn an App into a desktop website
it may be easy to integrate all the functions of a website into a mobile App, but it is not absolute-in some cases, it is almost impossible. This is not the real demand of users. If users want to browse the web, they will use the computer. Apps are usually designed to be fast and simple tasks and functions, and it takes only a short time to get results. The main reason why users install App is that they don't want to spend a lot of time browsing a huge website.
The screen size of the mobile phone is not compatible
A larger screen will be used when developing than when installing the App device. One of the biggest mistakes developers make is forgetting the compatibility of mobile phones. This risk will be reduced when more functions or texts are typeset on one page. The messy screen of small buttons is not popular with users.
triggering the background program
creating high minimum software is a common mistake in computers and servers for many years, and now it is a mobile device. Remember that when an application is used on a device, it will also run all background services or several other processes that the user feels it necessary to run. App is running in the mobile phone, but too much system demand will cause the device to crash, thus losing customers.
ignore operating system integration
it's not just a function. Android and iOS have very different styles, layouts and navigation. Try to match every operating system that creates the project, and users will be satisfied. Android users and iPhone users have unnecessary expectations for design and function, and an iPhoneApp will not be suitable for Android users. It doesn't need matching design customization, but it does need applications designed specifically for the operating system.
Save testing
Just like writing rules, you never test your own tasks, and developers should not try to test their own applications. This is a problem that people who participate in the development or design of programs will ignore, because they fully understand the programs they develop or design.
Ideal test crowd:
As a part of the target market-if the game is developed for teenagers, it should be the teenagers who test the program, not the developers;
there are no people involved in the development-although you or the team may have their own fans, you still need to find other new testers when testing;
the most authentic feedback-don't hire your family to test.
losing the ultimate goal
it is easy to have a brand-new direction based on a good idea or a cool idea in the development process. But you need to make sure that the final product is what you want when you start. If you design for others, the customer may have specific needs, and then gradually move away from the original idea, and finally the customer is still dissatisfied. If you have a good requirement change, make sure to discuss and confirm it before development. If there is any dissatisfaction in the product, the customer can raise it, but make sure that the created product meets the original design purpose and functional requirements.