Here’s a way to prevent your app from getting a low download count

 2 years ago
source link: https://uxplanet.org/heres-a-way-to-prevent-your-app-from-getting-a-low-download-count-a60d866bb585
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
Gif and illustrations by Pablo Stanley

Here’s a way to prevent your app from getting a low download count

App creators need to test their ideas and launch their products as soon as possible. Tech moves fast. Users change. Design sprints & no-code tools can help reduce risk and find the right product-market fit for your app.

Startups, investors, companies, entrepreneurs, and creators in general waste a lot of time and money on ideas that haven’t even been tested by a single user. There are hundreds of thousands of apps in every store that have a really low download count. Behind each of those apps, you’ll find teams, agencies, studios, developers, designers, communicators, CEOs, COOs, CTOs, and more. The solution? Validating your ideas before going all-in.

Why should you consider doing a Design Sprint?

You might already have noticed that the world is changing a bit too fast. Taking this into account, you probably realize that it’s impossible to predict what will happen with the industry, with our users, or with the market and, consequently, we cannot know for sure what will work and what will not in a couple of months.

App creators need to be flexible and fast enough to design and develop apps quickly, react and adapt to unexpected changes and, most importantly, iterate on their ideas. App building cannot take 3, 6, or 12 months. Plus, ideas need to be tested!

Design Sprint is a methodology that’s based on the fundamentals of Design Thinking and focuses on the user, reducing the waste produced during the design cycle and improving UX through multiple iterations without losing time while producing documentation. This does not mean not working on research but optimizing it. There are 3 key phases: build, measure, learn.

Design Sprints assume that the first release of a product will always be incorrect and will need an iteration. This is the reason why it is considered more important to launch a prototype developed using minimum resources and start collecting feedback from real users as soon as possible than spending months designing and developing a “perfect” product based on a hunch. The outcome will probably be outdated at the time it’s released.

What is a Design Sprint?

Basically, a Design Sprint helps you build prototypes from a transversal perspective, taking into account, at the same time, the emotional, usable, trustworthy, and functional traits.


Design Sprints incorporate a technique to ensure that, although it seems contradictory, the brainstorming of a multidisciplinary team is structured, follows a timetable, and is not carried out during infinite meetings where the one who shouts louder or has a more clear idea is right. Design Sprints decentralize discussions and give the decision-maker the power to choose, after hearing different perspectives, which path to take.

Companies like Slack, Google, Uber, and Twitter have been using Design Sprints for a while now. You can find here and here some case studies.

Which are the Design Sprint steps?

The key is to stick to a timetable, follow a series of steps and get a prototype that’s been tested by 5 users by the end of the week. On the first day you’ll map the problem, on the second day you’ll sketch solutions, on the third day you’ll decide what solution to prototype, on the fourth day you’ll prototype, and on the last day, you’ll test your prototype with real users.


I want to learn how to use design sprints!

Glad you asked! I’ve gathered a series of free ebooks for anyone who wants to give Sprints a chance:

Got questions? Shoot me an email!

About Joyk

Aggregate valuable and interesting links.
Joyk means Joy of geeK