Getting your app's market positioning right isn't just marketing fluff—it's the difference between crafting something people actually want and creating another forgotten app that gets buried in the app stores. I've seen brilliant technical teams pour months into developing features nobody asked for, simply because they never took the time to understand who they were designing for and why those people should care.
Here's the thing about app positioning: it's not about finding every possible user who might download your app. That's a recipe for designing something generic that appeals to nobody. Instead, successful positioning means getting laser-focused on a specific group of people with a particular problem you can solve better than anyone else. Think about it—when you try to speak to everyone, you end up speaking to no one.
The most successful apps don't try to be everything to everyone; they become indispensable to someone specific
Market positioning goes way deeper than just knowing your users age or income bracket. It's about understanding their daily frustrations, the jobs they're trying to get done, and the emotional triggers that make them reach for their phone. When I work with clients on positioning, we dig into the psychology behind user behaviour—what makes someone choose one app over another when they have dozens of similar options?
The mobile app landscape is crowded beyond belief. Your positioning strategy needs to cut through that noise by making it crystal clear why your app exists and who benefits most from using it. Get this foundation wrong, and even the most polished user interface won't save you from mediocre downloads and poor retention rates.
Before you spend a single pound on development, you need to understand who actually wants your app. I mean, really wants it—not just your mum saying it sounds "lovely" to be supportive! Over the years, I've watched brilliant developers build technically perfect apps that nobody downloads because they skipped this bit. It's painful to see, honestly.
Market research isn't just about proving your idea is good; it's about understanding how good it needs to be and what "good" even means to your users. You're looking for three key things: what problems people are trying to solve, how they currently solve them, and whether your solution fits into their daily routine. If someone's already spending fifteen minutes each morning checking three different apps, maybe there's space for you to combine those functions?
The tricky part is that people often can't articulate what they want. They'll tell you they want faster horses when what they really need is a car, you know what I mean? You need to watch what they do, not just listen to what they say. I always look at app store reviews for similar apps—the complaints tell you exactly where the gaps are.
But here's the thing—don't get stuck in research mode forever. Once you've got a solid understanding of your market's pain points and current solutions, it's time to start designing. The real learning happens when people start using your experience.
Right, let's talk about something that honestly makes or breaks most app projects—understanding what you're up against. I can't tell you how many times I've had clients come to me with what they think is a "completely unique" idea, only to discover there are already dozens of similar apps in the market. It's not their fault really; when you're passionate about solving a problem, it's easy to get tunnel vision.
But here's the thing—competition isn't necessarily bad news. Actually, it can be quite reassuring because it proves there's genuine demand for what you're designing. The key is knowing how to research your competitors properly and then use that information to position your app differently.
Start by searching the app stores using keywords your potential users would type. Don't just look at the obvious competitors; dig deeper into related categories too. I always tell my clients to download the top 10-15 apps that even remotely overlap with their idea. Use them for a week. Read every single review, especially the negative ones—they're pure gold for understanding what users actually want.
Create a simple spreadsheet tracking your competitors' strengths, weaknesses, and user complaints. This becomes your roadmap for differentiation and helps you spot opportunities they've missed.
The goal isn't to copy what others are doing—it's to understand the competitive landscape so you can find your own space within it. Sometimes the best positioning comes from doing the exact opposite of what everyone else is doing.
Right, let's talk about user personas—because honestly, most of the ones I see are complete rubbish. You know the type: "Sarah, 28, loves yoga and organic coffee, owns an iPhone 12." That tells us absolutely nothing useful about how Sarah actually behaves when she's using an app.
Real user personas aren't about demographics; they're about behaviour, pain points, and the specific moments when people reach for their phones. I've seen too many apps fail because the team designed for imaginary users instead of real ones. When I work with clients, we dig into the messy, complicated reality of how people actually use mobile apps—not the polished version we'd like to believe.
The personas that actually help during design focus on what people are trying to accomplish. Take a fitness app—forget about Sarah's yoga obsession for a minute. What matters is: does she check the app whilst waiting for the bus, or does she plan her workouts the night before? Is she motivated by progress tracking or social comparison? These behavioural insights drive real design decisions.
I always include the user's emotional state in our personas because that's what really matters in mobile. Someone booking a last-minute taxi is in a completely different headspace than someone browsing for holiday destinations. Your app needs to match that energy.
Here's what I include in every persona we create:
When your personas answer these questions, they become powerful tools that help everyone on the team make better decisions. They stop being marketing fluff and start being design guides.
Right, so you've got your user personas sorted and you understand who you're designing for. Now comes the bit that gets business people really excited—working out just how big this opportunity actually is. I mean, there's no point crafting the perfect app for a market of twelve people, is there?
Market sizing isn't about finding massive numbers to impress investors (though that doesn't hurt). It's about understanding whether your app target market is big enough to sustain your business goals. I've seen brilliant apps fail because the founders didn't realise their total addressable market was tiny, and I've also seen mediocre apps succeed because they picked a massive market with room to grow.
Start with your Total Addressable Market (TAM)—that's everyone who could theoretically use your app. Then narrow down to your Serviceable Available Market (SAM), which is the slice you can realistically reach. Finally, work out your Serviceable Obtainable Market (SOM)—what you can actually capture with your resources and timeline.
Let's say you're designing a fitness app for busy parents. Your TAM might be all smartphone users who exercise; your SAM could be parents aged 25-45 in English-speaking countries; and your SOM might be 0.1% of that group in your first year. That's still potentially thousands of users if you've done the maths right.
The best opportunities aren't always the biggest markets—they're markets where you can craft something meaningfully better than what exists today
Look for markets that are growing, underserved, or ready for disruption. A smaller market that's expanding rapidly can be much more valuable than a massive market that's stagnant. And honestly? Sometimes being a big fish in a small pond beats fighting for scraps in an ocean.
Right, so you've done your research and you know your market inside out. Now comes the fun part—deciding exactly where your app fits in this whole ecosystem. And honestly? This is where a lot of people get it wrong because they try to be everything to everyone.
Your positioning strategy is basically your app's identity in the marketplace. It's how you want people to think about your app when they compare it to alternatives. Are you the budget option? The premium choice? The simplest solution? The most feature-rich? You need to pick one lane and own it completely.
I've seen apps succeed with different positioning strategies, but they generally fall into these categories:
Here's the thing though—your positioning needs to match what you can actually deliver. I've worked with clients who wanted to position themselves as the premium option but weren't willing to invest in the user experience that premium users expect. That's a recipe for disaster.
The best positioning strategies also consider your competition's weaknesses. If all your competitors are complex and feature-heavy, positioning yourself as the simple, easy-to-use alternative can work brilliantly. But if there's already a dominant "simple" player? You might need to find a different angle.
Think about your target users personas here too. What matters most to them? Speed? Price? Features? Status? Your positioning should speak directly to their primary motivation for choosing an app like yours. Once you've picked your position, everything else—from your app's design to your marketing messages—should reinforce that choice.
Right, you've done your research, created your user personas, and chosen your positioning strategy. Now comes the part that separates the successful apps from the ones that quietly disappear—actually testing whether your market position works in the real world.
I'll be honest, this is where many app creators get a bit nervous. It's one thing to have a brilliant strategy on paper; it's another thing entirely to put it in front of real users and see what happens. But here's the thing—testing your market position early can save you months of development time and thousands of pounds.
You don't need a fully designed app to test your market position. Actually, that's probably the worst way to do it! I've seen too many clients spend six months crafting something only to discover their target market doesn't care about the problem they're solving.
Landing page tests work brilliantly for this. Create a simple page that explains your app's value proposition, shows some mockups or wireframes, and includes a sign-up form for early access. Then drive targeted traffic to see how your positioning resonates with your intended market.
Run your landing page test for at least two weeks with different messaging variations. A 15-20% conversion rate suggests strong market interest, whilst anything below 5% means you need to rethink your approach.
Social media ads are another brilliant way to test positioning quickly. Create several versions of your app concept—each highlighting different benefits or targeting slightly different user segments. See which ones get the most engagement, comments, and click-throughs.
User interviews are absolutely gold for this stage. I usually recommend speaking to at least 20-30 people from your target market. Ask them about the problem you're solving, show them your concept, and listen carefully to their language. Do they describe the problem the same way you do? Are they excited about your solution?
Here's what to test systematically:
The key is being genuinely open to feedback, even when it challenges your assumptions. Some of the best apps I've worked on changed direction completely based on early market testing. That's not failure—that's smart business.
Getting feedback on your app's market positioning isn't a one-and-done thing—it's an ongoing conversation with your users. I've seen too many creators collect feedback, file it away somewhere, and then wonder why their app isn't performing better. The magic happens when you actually use that feedback to refine and improve your approach.
First thing to understand: not all feedback is created equal. You'll get loads of opinions, feature requests, and complaints, but the feedback that really matters comes from your core users—the ones who genuinely love your app and use it regularly. These are the people who "get" what you're trying to do, and their suggestions usually align with your positioning goals.
Look beyond what people say and watch what they actually do. I always tell my clients to focus on user behaviour data alongside verbal feedback. If users say they want feature X but never use similar features you already have, that tells you something important about the gap between what people think they want and what they actually need.
App analytics can reveal whether your positioning is working. Are people discovering your app through the channels you expected? Are they using the features you thought would be your main selling points? If your analytics show that users are gravitating towards different features than you anticipated, that's valuable positioning intel right there.
When refining your positioning based on feedback, make small changes rather than dramatic pivots. I've watched companies completely overhaul their positioning based on feedback from a vocal minority, only to alienate their existing user base. Test changes with a subset of users first, measure the impact, and then decide whether to roll them out more broadly. Your positioning should evolve, not revolve.
Right, let's talk about the mistakes I see apps make time and time again. These are proper face-palm moments that can sink even the best app ideas before they get off the ground.
The biggest mistake? Trying to be everything to everyone. I get it—casting a wide net feels safer, but it's actually the kiss of death. When your app target market is "anyone with a smartphone," you've basically got no market at all. Your messaging becomes so generic that nobody feels like your app was made specifically for them. And here's the thing: people only download apps that feel relevant to their specific needs.
Another classic blunder is assuming your market positioning will sort itself out after launch. I've seen brilliant creators spend months perfecting their app's functionality while giving zero thought to who will actually use it. That's backwards thinking that leads to expensive lessons. Your positioning needs to shape your design decisions, not the other way around.
The worst mobile app strategy is having no strategy at all—hoping users will figure out why they need your app is like expecting them to read your mind.
Then there's the comparison trap. Too many apps position themselves as "like Uber but for X" or "Tinder meets Y." While comparisons can help explain your concept quickly, relying on them too heavily makes you look like a copycat rather than a solution to a real problem. Focus on the problem you solve, not the successful app you're trying to emulate. Your user segmentation should be based on needs and behaviours, not on copying someone else's homework. Trust me—the apps that succeed are the ones that carve out their own space rather than fighting for scraps in someone else's territory.
Right then—we've covered a lot of ground here, and if you've made it this far, you're already ahead of most people who just wing it when launching their apps. Market positioning isn't something you can just guess at; it needs proper thought and research behind it.
The thing is, positioning your app correctly can literally make or break your entire project. I've seen brilliant apps fail because they couldn't clearly communicate their value to the right people. And I've seen average apps succeed wildly because they nailed their positioning from day one.
Here's what I want you to remember: your market position isn't set in stone. The most successful apps I've worked on have evolved their positioning as they learned more about their users. That fitness app that started targeting serious athletes? Turns out busy parents were the ones who really loved it. The productivity tool aimed at freelancers? Small teams couldn't get enough of it.
But—and this is important—you need a starting point. You can't just say "everyone will love this app" because that's how you end up speaking to no one. Pick your initial position based on solid research, test it properly, and be ready to adjust when the data tells you something different.
The market positioning work you do now will influence everything else: your app's features, its design, your marketing messages, even which platforms you focus on. It's the foundation everything else gets built on—and that's exactly where We Are Affective excels. We craft the psychology-based research, user experience design, and strategic positioning that becomes the blueprint any development team can then implement. Whether you work with freelancers, agencies, or in-house teams, they need that foundation to build something users actually want. Let's craft your experience foundation.