10 iOS Development Common mistakes did you recruit?

Since 2008, I have developed dozens of applications. In the process, I learned that developers make common mistakes in the development process. Sometimes they do their best to solve the problem, but sometimes some mistakes make the developer completely missed the success. So in this article, I've listed some common bugs in the iOS development process. Some mistakes, if not discovered in time, can stifle start-ups. Coupled with the depletion of the start-up reserve and the collapse of confidence among team members, it is difficult to get out of the crisis.

　　1. In case of failure, improper information processing and user interaction

Making a user's head spin is no good for creating an excellent user experience, such as when users want to update their Twitter password, you show a false hint, "Oops, there was a mistake, please try again later." What you need to do is to make the error messages as clear as possible and to test for situations that you might encounter. Confusing or ambiguous error messages are of no help to you.

At the same time, do not annoy users, not one by one to show the error reminder, but to guide the user step-by-step solution.

　　2.Beta Beta Tester Unreliable

Finding testers is a must, but doing some research in advance is necessary. These testers should be your target audience, not just anyone on the social networking site.

You want to be able to get their feedback so you can adjust the application as needed. The key, though, is knowing when to update. Not all feedback is valuable, so you need to parse the feedback from the tester as needed. The need for a few people to have individual features doesn't mean you have to add that functionality.

　　3. Mandatory use of Facebook or Twitter login

Use the Include standard mail enrollment option instead of forcing the user to log on. Forcing users to log on with social accounts can annoy a subset of users. Although we all know the power of this approach, the ultimate option is still to be given to the user.

　　4. Wishful thinking that app is going to be a big sell

Once you've released your application, you're in an arena full of thousands of competitors. At this point, you need to make a detailed plan, need to know who the user is, need to know where the user is, so that you can fully control. This is a very boring chore, but it's important if you want to stay in the App Store.

　　5. Ignoring testing in the "real World" network situation

What do you do with your app when you don't have a network? What happens to your application when the network is plugged in or disconnected? To ensure that your application can handle these situations, your users will experience bad experiences. Spend time using the network link conditioner tool to mimic weak connections on a device.

　　6. No guarantee that the application will function on all target model devices

Since we need to deal with a series of screen sizes, it's worth taking the time to make sure that the app works and performs as expected, rather than accidentally doing something strange.

　　7. Equate the experience of the mobile end with the experience of the web side

There's nothing wrong with creating the ultimate user experience for an existing platform, but Android and iOS are two different areas of the mobile OS and web side, so avoid bringing web-side experience into the mobile-end application.

　　8. Stacking functions for Applications

Although you just want to make apps more powerful, too much functionality can only limit you to your own predicament. Developers may feel very guilty about the need for a small number of users to be enthusiastic about individual features. This time you need to think about your own vision and expectations. If the user's feedback is real and you have previously overlooked it, then you can identify the requirements and increase them appropriately. Focus on the more concise but more valuable places, so that you can test your ideas as much as possible.

　　9. Poor code flexibility

When you need to consider the product and market at the same time, about the code library this point, does not require you tangled code to write a good look, the most basic is to ensure that it is not a pile of garbage. Take the time to make the code a maintainable level. The code side is a delicate balance, and you don't have to spend too much time on it, but you can't ignore it.

　　10. Development for all platforms immediately

For some reason, developers will feel that their applications should appear in front of each platform and all users. This is a bad idea, and if you're currently developing an iOS app, you don't need to develop an Android app right now. What you need to do is take the time to build a platform that will help you build a more perfect product and avoid cutting your team's time and energy. When you have multiple versions of your application, you need more support requirements. This practice kills a startup, so focus and optimize the use of all resources.

　　Summarize

These are just some of the common bugs in the iOS development process that I've seen from the perspective of a developer and founder, and it doesn't seem to make sense to ask you to do 100%, and you can do it on your own, but keep your eye on the content, and you can adjust it based on time and resources. The things you want to avoid---run out of all the reserve funds. Mistakes are everywhere, but the price you spend will be much greater-your start-up company. This is no exaggeration to say that some people have lost their start-ups because of the mistakes they made above.