Reading Other People's Apps
读懂别人的应用
01What this concept is really about
Reading other people's apps means deliberately examining how an app is built, how it behaves, and how it solves problems for its users. It is not about copying code or stealing designs. Instead, it is about developing a habit of observation and curiosity. When you read an app, you look at its screens, its navigation, its feedback, its language, and its flow. You ask questions like: Why is this button here? What happens when I tap it? How does the app tell me something went wrong? How does it help me finish a task quickly? This practice turns everyday app use into a learning opportunity.
For a beginner, reading an app is a skill that complements writing code. Many people focus only on building, thinking that the more they code, the better they get. But building without reading is like writing without reading books. You miss out on patterns, conventions, and clever solutions that others have already discovered. Reading apps helps you see the difference between a thoughtful design and a careless one. It trains your eye to notice details: spacing, color, wording, transitions, and error messages. Over time, you build a mental library of ideas you can adapt to your own projects.
The concept is framework-agnostic. Whether the app is built with one technology or another, the principles of good user experience remain similar. You are not learning a specific tool; you are learning to think like a designer and a developer at the same time. This makes you more versatile and more empathetic to the people who will use your app.
02Why it matters for your app
Reading other apps matters because it exposes you to solutions you might never invent on your own. When you only build, you tend to repeat your own habits. You might keep using the same navigation pattern or the same error message style because it is familiar. By studying a variety of apps, you see alternatives. You notice how a simple change in wording can make a screen feel friendlier. You see how a subtle animation can guide the eye. You learn how to handle edge cases like empty states, loading, and offline mode. These insights directly improve the quality of your own app.
Another reason is that reading apps helps you understand user expectations. People use many apps every day. They unconsciously expect certain behaviors: a back button that works, a clear way to cancel an action, a confirmation before deleting something important. If your app violates these expectations, users get frustrated. By reading popular and well-designed apps, you learn what feels natural. You can then apply those conventions to your app, making it easier for people to learn and use.
Finally, reading apps builds your problem-solving vocabulary. When you encounter a challenge in your own project, you can recall how another app solved a similar problem. Maybe you remember a clean way to present a long form, or a clever way to show progress. You do not need to copy the exact implementation; you just need the idea. This speeds up your development and raises the overall quality of your work. It also makes you a more critical thinker, because you start to evaluate why something works, not just that it works.
03The mistake beginners often make
The most common mistake is to focus only on building. Beginners often think that the best way to learn is to start a project and write as much code as possible. They spend hours debugging and adding features, but they rarely step back to study how other apps are made. This is like trying to write a novel without ever reading one. You might finish something, but it will likely be full of rough edges. You miss out on proven patterns and end up reinventing solutions that already exist.
Another mistake is to read apps passively. Scrolling through an app and thinking, "That's nice," is not real reading. To learn, you need to be active. You should ask specific questions: How many taps does it take to complete a core task? What happens when I rotate the screen? How does the app handle a slow network? What words does it use in buttons and labels? Without this active questioning, you will not retain much. You might even overlook problems because you are not paying attention.
A third mistake is to copy without understanding. Some beginners see a design they like and immediately try to replicate it in their own app. But they do not understand why it works or whether it fits their context. This can lead to a confusing user experience. Reading is not about copying; it is about learning principles. You should always ask, "Why did they do it this way? Would this work for my users?" If you skip that step, you are just building someone else's app, not learning to build your own.
04A simple way to learn it
A simple and repeatable way to learn by reading apps is to pick one app and study it deeply over a week. Choose an app you use often and that is known for good design. Do not try to study many apps at once; depth beats breadth when you are starting. Each day, focus on a different aspect. On day one, explore the overall navigation: how do you move between major sections? Is there a tab bar, a menu, or something else? Draw a simple map of the screens on paper. On day two, look at a single core task, like sending a message or buying an item. Count the steps and note what feedback you get at each step.
On day three, examine the language. Write down all the button labels, headings, and error messages you see. Notice whether the tone is formal or casual, and whether words are clear or confusing. On day four, look at visual design: colors, spacing, font sizes, and icons. Ask how these choices affect readability and focus. On day five, test edge cases. Turn off your network and see what happens. Try to submit an empty form. See how the app handles mistakes. On day six, compare your notes with another app that does something similar. What is different? Why might that be? On day seven, write a short summary of what you learned and how you could apply it to your own project.
This approach is concrete because it gives you a daily action. It is repeatable because you can do it with any app. It forces you to be active and reflective. After a week, you will have a much deeper understanding of how a well-made app works, and you will have a list of ideas to try in your own development.
05What to pair it with
Reading apps works best when paired with learning UI principles. UI principles are the fundamental rules about layout, contrast, alignment, and hierarchy. When you study an app, you can see these principles in action. For example, you might notice how a screen uses a clear visual hierarchy to guide your eye to the most important action. If you already know the principle, you can appreciate why it works. If you do not, you might just think it looks nice. So, as you read apps, also read about UI principles. This combination helps you understand the "why" behind the design.
Another good pairing is navigation. Navigation is how users move through your app. It is one of the most critical parts of the user experience. When you read an app, pay special attention to its navigation patterns. How does it handle going back? How does it show where you are? How does it deal with deep links? By studying navigation in other apps, you will be better prepared to design your own. You can also pair reading with learning about common navigation models, such as tabs, stacks, and drawers. Seeing them in real apps makes the concepts concrete.
Finally, pair reading with a mindset of continuous learning. Reading apps is not a one-time activity. It is a habit. You can combine it with keeping a design journal, where you note interesting patterns and ideas. You can also pair it with building small prototypes to test what you learn. But remember: the goal is not to only build. The goal is to learn by reading first, then apply. By pairing reading with UI principles, navigation, and a learning habit, you create a strong foundation for your own app development.
06When to keep it simple
When you are just starting out, it is easy to get overwhelmed by the complexity of some apps. Many popular apps have years of development behind them, with dozens of features and intricate flows. If you try to understand everything at once, you will feel lost. In these moments, keep it simple. Focus on one small part of the app. For example, just study the login screen. How does it handle errors? What does the button say? How is the form laid out? By narrowing your scope, you can still learn valuable lessons without being drowned in details.
Another time to keep it simple is when you are short on time. You do not need to spend hours reading an app. Even ten minutes of focused observation can teach you something. Pick one screen and ask three questions: What is the main action? How does the app guide me to it? What happens if I make a mistake? Write down your answers. That is enough for one session. Over time, these small sessions add up. You do not need to analyze every pixel or every transition.
Also, keep it simple when the app is not relevant to your project. Not every app is a good model for what you are building. If you are making a simple to-do list app, studying a complex social network might not be helpful. Instead, find an app that solves a similar problem. Study that one. Simplicity also means not over-analyzing. Sometimes an app does something in a certain way just because of its brand or history. You do not need to understand every decision. Focus on what you can apply. Keeping it simple helps you stay motivated and avoid burnout.
07Questions beginners ask
Q: How do I choose which app to study? A: Start with an app you use daily and find easy to use. It should be relevant to the type of app you want to build. Avoid apps that are overly complex or that you do not enjoy using. The goal is to learn from good examples, so pick something that feels well-designed to you.
Q: What if I do not understand why the app is designed that way? A: That is okay. Not every decision will be obvious. Try to think about the user's needs. Ask yourself: What problem is this design solving? If you still cannot figure it out, make a note and move on. You can always come back later. Over time, you will build intuition. You can also look for articles or videos that explain common design patterns, but avoid relying on them too much. The important thing is to keep observing and asking questions.
Q: How long should I study one app? A: There is no fixed rule. A week of short daily sessions is a good start. After that, you can move to another app or continue with the same one if you find it valuable. The key is consistency. Even a few minutes a day can make a difference. Do not pressure yourself to finish quickly. Learning by reading is a marathon, not a sprint. The more you practice, the more you will see patterns everywhere.