--- title: How to choose an iOS app designer in london description: Choosing an iOS app designer in London takes more than browsing portfolios. This guide covers what to look for, what to ask, and which red flags to avoid. image: https://weareaffective.com/hubfs/learning-centre-images/how-to-choose-an-ios-app-designer-in-london.webp --- [Skip to content](https://weareaffective.com/learning-centre/how-to-choose-an-ios-app-designer-in-london#main-content) [![we\_are\_affective\_logo\_200](https://weareaffective.com/hs-fs/hubfs/we_are_affective_logo_200.png?width=175&height=48&name=we_are_affective_logo_200.png "we_are_affective_logo_200")](https://weareaffective.com) - [Home](https://weareaffective.com) - About Us - [Our Story](https://weareaffective.com/about) - [How We Work](https://weareaffective.com/how-we-work) - Our Services - [App Planning & Strategy](https://weareaffective.com/app-planning-strategy) - [App Design](https://weareaffective.com/app-design-agency) - [App UX Design](https://weareaffective.com/app-ux-design) - [App UI Design](https://weareaffective.com/app-ui-design) - [App Technical Architecture](https://weareaffective.com/app-architecture) - [Existing App Audits](https://weareaffective.com/app-audit) - [Case Studies](https://weareaffective.com/case-studies) - [Pricing](https://weareaffective.com/pricing) - [Learning Centre](https://weareaffective.com/learning-centre) - [Get Started](https://weareaffective.com/get-started) Expert Guide Series # How to choose an iOS app designer in london Table of Contents Finding an iOS designer in London is not the hard part. The city has hundreds of them, and a few minutes on Dribbble or LinkedIn will surface more portfolios than you can read in an afternoon. The hard part is knowing which ones will actually serve your product well, and which ones will hand you beautiful screens that your users never quite warm to. > The surface signals of a good portfolio do not tell you whether a designer thinks in behaviour and emotion. The distinction matters more than it sounds. A designer who thinks in pixels will give you something that looks right in a presentation and feels slightly off in someone's hand. A [designer who thinks in behaviour, emotion](https://weareaffective.com/app-design-agency), and context will give you something that earns the kind of attachment people feel toward products they genuinely rely on. London's market is large enough that both types are in plentiful supply, and the surface signals, a polished portfolio, a confident introductory call, a respectable day rate, do not reliably tell you which you are talking to. This guide is about how to tell them apart. It covers where to look, what to read in a portfolio, what questions to ask, and what answers should give you pause. The framework we use at We Are Affective draws on our own experience working with lifestyle brands on iOS products where the [emotional experience of the app is as load-bearing](https://weareaffective.com/learning-centre/5-things-that-make-the-difference-between-so-so-apps-and-stellar-apps-what-your-) as the functional one, sometimes more so. ## What an iOS Designer in London Actually Does The job title covers a wide range of actual work, and the range matters when you are choosing someone. At one end, an iOS designer produces screens: layouts, components, colour choices, and typography set up in a tool like Figma and handed to a developer. At the other end, an iOS designer runs discovery work, maps user psychology, defines interaction patterns, writes copy for interface moments, and stays close to development to make sure what ships matches what was intended. Apple's Human Interface Guidelines set a floor for iOS design. Any competent designer working on the platform will know them. But the guidelines describe what Apple considers structurally sound, not what makes a particular product feel right for a particular audience. A wellness app and a fitness tracker can both follow the guidelines perfectly and still feel completely different in someone's hands, because the emotional register of each, the pace, the warmth, the way the product speaks, is a layer above the structural rules. When we design an iOS product, we treat the interface itself as doing emotional work. On a meditation app we reviewed, the breathing animation was already slowing users down before they had read a single line of copy. The product was doing the calming, not the text. That is the level at which strong iOS design operates, and it is what separates a designer who understands Apple's platform from one who also understands your users. ## Where to Find iOS Designers in London Dribbble and Behance are the obvious starting points, and they are worth using for a first pass on visual quality. The limitation is that both platforms reward presentation skill. A case study on Dribbble is a curated artefact, not a working account of a project. Treat it accordingly. LinkedIn is more useful for understanding someone's career arc: where they have worked, how long they stayed, whether they have experience in lifestyle categories similar to yours. Agencies that specialise in product design, rather than generalist digital studios, are worth seeking out because they tend to have a more developed point of view on user psychology. #### Referrals carry more signal than search A referral from a founder who has shipped a product you respect carries more information than any portfolio page. Ask who designed it. Ask what the process was like, not just whether the result was good. Process quality is harder to fake across a whole working relationship than a finished artefact is. #### Consider the fit for your category A designer with a strong track record in fintech may have no feel for the emotional warmth that a food and drink brand or a beauty app needs. The aesthetic conventions are different, the user expectations are different, and the emotional register is different. When you are scanning for candidates, check whether their previous work sits anywhere near the lifestyle space your product lives in. ## UX/UI design built around *real* psychology We design app interfaces around how people actually think and behave. User research, psychology-driven UX/UI design and technical specs delivered as one complete package. [See how we work](https://weareaffective.com/how-we-work) [Get started](https://weareaffective.com/get-started) No commitment ## How to Read a Portfolio Critically The first thing to check is whether the portfolio shows thinking or only outcomes. Outcomes, final screens, polished mockups, app store screenshots, tell you that someone can produce a presentable artefact. Thinking, sketches, research notes, decision rationale, before and after comparisons, tells you how they got there and whether that process is one you want applied to your product. Look for evidence that the [designer challenged a brief rather than executed it](https://weareaffective.com/learning-centre/how-to-tell-whether-your-digital-problem-is-a-format-problem-or-a-brief-problem). A case study that moves cleanly from client goal to finished screens with no friction recorded anywhere is probably incomplete. Real projects have moments where the initial direction was wrong and someone had to say so. > A case study that moves from brief to screens with no friction recorded is probably incomplete. Pay attention to the emotional claims made in the case study text. Any designer can write "we wanted to create a calming experience." The question is what specific decisions followed from that: what colour temperature, what animation timing, what copy tone, and how do those choices connect to the emotional goal rather than just accompanying it in the same document? #### Check the breadth of deliverables A strong portfolio shows more than screens. Look for user journey maps, personality documents, interaction notes, or anything that suggests the designer is building a coherent model of the user rather than a collection of individual screens. These artefacts are harder to fake and harder to produce without genuine discovery work behind them. Ask whether the case study includes any design decisions that were reversed or changed after user feedback. A portfolio with no reversals is either hiding the messy parts or the designer never tested anything. ## What a Portfolio Cannot Tell You A portfolio cannot tell you how much of the work was actually the designer's. In agency environments and larger studios, multiple people touch a product. The person presenting the portfolio may have owned the visual language and had very little to do with the interaction model, or vice versa. Ask directly what their specific contribution was on each piece they show you. A portfolio also cannot tell you how the designer behaves when a project goes wrong. The wellness genetics product we worked on, brought in to improve the emotional layer of a data-heavy product that had been built in a functional way that did not match the brand's premium feel, required several rounds of back and forth with the development team after a third-party designer in the handoff chain produced something that looked luxurious but was extremely difficult to implement on the existing codebase. That kind of situation tests a designer's judgment, patience, and ability to problem-solve under constraints. None of that is visible in a portfolio. A portfolio cannot tell you what the designer does when a client is pushing in the wrong direction, either. We have seen two projects, a fitness app and a grassroots football product, where founders with strong personal conviction in their own vision ignored data coming out of research, focus groups, and user surveys. Both products became shaped by the founder's preferences rather than user evidence, and both exhausted their budgets in design and build without ever reaching a fully live product. A designer who cannot hold a position in that situation will follow the founder off the edge. ## Whether They Understand Your Users Before Your Screens The question to ask, early and directly, is what they do before they open Figma. The answer tells you almost everything. A designer who talks immediately about components, navigation patterns, and platform conventions is working from structure outward. A designer who asks who the user is, [what they feel at the moment they arrive](https://weareaffective.com/learning-centre/what-curiosity-looks-like-in-a-first-session-and-why-most-products-design-past-i) at the product, and what emotional state you want them to leave with is working from the inside out, and that is the direction that produces products people return to. Our discovery process at We Are Affective is built around exactly this. Simon and Josh, our strategy and UX lead, run structured sessions with clients that are designed to surface answers the client often did not know they had. The sessions involve games that feel slightly unconventional, including exercises around brand personality and competitor psychology, and clients are asked to come relatively unprepared, because pre-submitted answers tend to be polished rather than true. One of those exercises asks clients to picture their product or brand as a person at a dinner party: how do they dress, how do they talk, are they the loudest voice in the room or the quiet listener, who gravitates toward them? It sounds unusual and it works, because it shifts client thinking from functional to emotional in a way that a briefing document rarely does. Ask your candidate designer whether they have anything equivalent in their process. Ask your candidate: what is the first thing you do after you read a brief? If the answer goes straight to research formats or screen structure, probe further. The answer you are looking for starts with the user's emotional state, not the product's feature list. ## Whether They Will Challenge a Founder's Assumptions This quality is harder to assess than visual skill, but it matters more on most projects. A designer who defers to the client on every substantive decision is an execution service. Execution services have their place, but if you are building a product from the ground up, you need someone who will push back when pushing back is warranted. Ask them directly: can you give me an example of a time you disagreed with a client about a design decision, and what happened? The content of the answer matters less than whether they have one. A designer who cannot recall a single disagreement has either had no opinions or has not been in the room when opinions were needed. We declined a project involving [a fairly standard social product](https://weareaffective.com/learning-centre/why-your-social-media-app-needs-more-than-just-pretty-design) because the client wanted to go straight into redesigns without any discovery work. They were not willing to engage with our emotionally led, user-centred discovery phase, and we walked away. That is not a decision we made reluctantly. A process built around understanding users before building screens is not a preference we set aside for projects where the client is in a hurry. #### Signs a designer will hold their position - They can describe a specific instance where they pushed back and what their reasoning was - Their proposals include rationale, not just options - They ask about your users before they ask about your preferences - They are willing to say, in the introductory conversation, that they do not know yet what the right answer is ## How They Handle the Gap Between Design and Development The handoff between design and development is where projects go wrong quietly. The screens look finished, the developer receives the files, and then weeks later something ships that looks almost right but feels slightly off in a way nobody can immediately name. The gap accumulates across dozens of small decisions: an animation timing that changed, a spacing value that drifted, a colour that shifted one step in translation. According to [Zeplin](https://blog.zeplin.io/four-ways-to-overcome-handoff-challenges-between-design-and-development/), 66% of designers and 65% of developers spend four to eight hours weekly on handoff inefficiencies. That is a significant amount of time disappearing into the space between two disciplines that should be working from the same understanding. Ask your candidate how they manage handoff. The answer should include more than "I use Figma and write annotations." It should include how they stay involved after files are delivered, how they handle developer questions, and how they check what ships against what was designed. A designer who considers their job finished when the files are handed over will leave your development team interpreting intent rather than implementing it. #### What good handoff practice looks like 1. Interaction notes and animation specs included with every component 2. A named point of contact for developer questions throughout build 3. A review of the live build before any release, not just a review of the files Ask specifically what happens if a developer says a design element is too complex to build as specified. A designer who immediately simplifies the design without exploring alternatives is working from development constraints rather than user needs. The right response is a conversation about what matters most in that specific element, not a reflexive reduction. ## What Their Discovery Process Looks Like in Practice Discovery is a word that gets used broadly. For some designers it means a kick-off call and a competitive audit. For others it means structured research, user interviews, emotional mapping, and a set of documents that define the product's personality and the emotional arc of its users before a single screen is drawn. The difference in outcomes between these two versions of discovery is large. Ask for a specific account of what discovery looked like on a recent project. Ask what documents came out of it, what changed in the design direction as a result of what was found, and whether there were any findings that surprised them. If the answer is that nothing surprising emerged from discovery, the process was either very shallow or the findings were not really engaged with. The artefacts that come out of a strong discovery phase include emotional arc documents that map [how users feel at each stage of their journey](https://weareaffective.com/learning-centre/how-to-read-a-user-session-recording-for-emotional-signal-rather-than-task-compl) through a feature, brand personality documents that define how the product speaks to people, and competitive teardowns that look at emotional register rather than feature parity. These are the documents that make subsequent design decisions defensible, not because they were ticked off in a process, but because they capture real understanding of real people. According to [Nielsen Norman Group](https://www.nngroup.com/articles/discoveries-in-industry-revealed/), investing more time in discovery reduces the risk of project failure by 75%. The figure aligns with what we observe: the projects that struggle tend to be the ones where discovery was treated as a formality rather than a foundation. ## How to Assess Fit Before You Sign Anything Run a paid diagnostic before committing to a full engagement. Ask the designer to spend a half day or a full day on a defined problem: a single user journey, a specific emotional tension in your product, or a brief audit of a competitor's interface. Pay them properly for it. The output matters less than the process: how do they think out loud, what questions do they ask, what do they notice first? A good diagnostic reveals working style, intellectual curiosity, and whether their instincts align with yours on the things that matter. It also gives you something concrete to disagree about before you are deep into a multi-month engagement, which is a much better time to discover a fundamental misalignment. #### What to watch for in a paid diagnostic A designer who delivers a polished presentation at the end of a diagnostic day has probably spent most of the time on presentation rather than thinking. A designer who shares rough working, talks through what they found confusing, and asks several questions they could not answer from the brief alone has probably done the more valuable work. Presentation quality at this stage is a distraction from process quality. Assess how they talk about your users. If they generalise, "users want simplicity", "people don't read", they are working from received wisdom rather than the specifics of your audience. Push them: which users, in what context, at what moment in their day? Specificity here is a good sign. ## What to Expect on Fees and Timelines in London London day rates for experienced iOS designers working independently run broadly between £450 and £850 per day, depending on seniority and specialisation. Agencies with a defined process and senior people across research, UX, and visual design charge more and deliver a broader scope of work. The right comparison is not rate against rate but scope against scope: what does each engagement actually include, and [what does it leave for you to manage](https://weareaffective.com/learning-centre/what-a-development-team-actually-needs-to-know-about-the-user-before-sprint-one)? A thorough discovery phase typically runs two to four weeks for a product of moderate complexity. Visual design for a core set of screens runs four to eight weeks after that, depending on how many states, edge cases, and interaction details need specifying. Development-ready files with full annotations and handoff support add time that is worth budgeting for explicitly. | Engagement type | Typical scope | Indicative London rate | | --- | --- | --- | | Freelance iOS designer | Visual design and Figma files | £450-£650 per day | | Senior freelance with UX | Discovery, UX, visual design, handoff | £650-£850 per day | | Specialist product agency | Full discovery, research, design, dev support | Project-based, typically £25k-£80k+ | [Be cautious of any engagement that does not include discovery](https://weareaffective.com/learning-centre/what-makes-users-trust-a-product-enough-to-enter-their-card-details) time in the budget. The cost of skipping discovery does not show up on the invoice, it shows up later, in redesigns, poor retention, and features that never quite fit the people they were built for. ## Red Flags Worth Walking Away From A designer who sends you a proposal within 24 hours of a first call has almost certainly written a template with your name in it. A real proposal for a real product requires time to think about what you actually said, what was left unsaid, and what the right process looks like given both. Speed here is a signal about how much of their process is genuinely tailored. A designer who shows you only their best work and cannot talk fluently about what went wrong on a project should make you cautious. Every honest practitioner has a project that taught them something uncomfortable. If they cannot name one, they have either not reflected on their work or they are not going to tell you about it, and neither of those is a good sign in someone you are about to trust with your product. > A designer who cannot name a project that went wrong has either not reflected or will not tell you the truth. Watch for a designer who talks about what competitors have done and suggests you do the same. We have seen clients try to lift interaction patterns directly from competitor products and drop them into their own, expecting the same clarity of experience. The context is different, the brand is different, the use case is different, and the result is a product that feels borrowed rather than built for its own users. #### A short list of departures worth making - No discovery process, or discovery described as a brief review of existing materials - Portfolio shows screens but no evidence of thinking or rationale - Cannot name a project where they pushed back on a client decision - Handoff described as "sending files" with no follow-through - Proposal arrived in under 24 hours and reads like a template ## Conclusion Choosing an iOS designer in London is, at its core, a question about what kind of thinking you want behind your product. Visual skill is a given at this level. What separates a designer who builds something people return to from one who builds something people tolerate is how deeply they understand the emotional experience of using the product, and how willing they are to let that understanding drive decisions rather than just decorate them. The signals are accessible if you know what to look for. Read portfolios for thinking, not just outcomes. Ask about discovery processes and listen for specificity. Run a paid diagnostic before any long commitment. Check whether they have walked away from work that compromised their process, a designer who has done that once will do it for your benefit when the situation calls for it. The concierge app we built for a property developer is a useful illustration of what happens when you ask the right questions early. The client wanted a building management tool and a community platform in one product. We ran focus groups with social housing tenants to understand what actually builds community between neighbours. The answer was familiarity, knowing names, interests, families. The product we designed put mundane building management tasks in the app and actively encouraged face-to-face conversations rather than replacing them. That direction came from discovery, not from assumption. The right iOS designer will do that kind of thinking for your product. They will ask what your users actually need, sit with the gap between that and what you originally requested, and build something that serves the people using it rather than the brief that described it. [Let's talk about your iOS product](https://weareaffective.com/get-started) ## Frequently Asked Questions What is the difference between an iOS designer who thinks in pixels and one who thinks in behaviour? A designer who thinks in pixels will produce screens that look polished in a presentation but feel slightly off when a real user interacts with them. A designer who thinks in behaviour and emotion will create an experience that users genuinely rely on and feel attached to, because the interface is doing meaningful work beyond looking correct. What does an iOS designer in London actually do day to day? The role ranges widely, from producing layouts and components in Figma at one end, to running discovery work, mapping user psychology, and staying close to development at the other. The scope of what a designer takes on matters enormously when you are deciding who to hire. Are Apple's Human Interface Guidelines enough to guarantee a good iOS app? The guidelines set a solid structural floor, and any competent iOS designer will know them well. However, they describe what is structurally sound rather than what makes a product feel right for a specific audience, so following them perfectly is a starting point rather than a finish line. Where is the best place to find iOS designers in London? Dribbble and Behance are useful for a first pass on visual quality, but they reward presentation skill rather than genuine process. LinkedIn gives a clearer picture of someone's career history, and specialist product design agencies are worth seeking out because they tend to have a more developed point of view on user psychology. Can I trust a designer's portfolio to tell me whether they are the right fit? A portfolio shows you visual quality and presentation ability, but it does not reliably tell you how a designer thinks about behaviour, emotion, or context. Treat a case study as a curated artefact rather than a full account of how a project actually unfolded. Why does emotional experience matter in iOS app design? Emotional experience is often as load-bearing as functionality, particularly in lifestyle and wellness categories. A well-designed app communicates through pace, warmth, and interaction patterns before a user has read a single line of copy, and that layer of experience is what earns long-term user attachment. How do I tell a strong iOS designer apart from one who simply looks impressive? The key is to look beyond polished visuals and confident introductory calls, and instead ask about process, user research, and how decisions were made on past projects. The questions a designer asks you, and the answers they give you, are more revealing than their day rate or the gloss of their Dribbble profile. Should I choose a specialist app design agency or a generalist digital studio? Specialist product design agencies tend to have a more developed point of view on user psychology, which is particularly valuable if your product operates in a lifestyle or emotionally driven category. Generalist studios may offer broader services, but depth of thinking about user behaviour is often more important than breadth. ## Related Articles [![Can I Sell My App to Another Company?](https://weareaffective.com/hubfs/learning-centre-images/can-i-sell-my-app-to-another-company.webp)](https://weareaffective.com/learning-centre/can-i-sell-my-app-to-another-company) ### [Can I Sell My App to Another Company?](https://weareaffective.com/learning-centre/can-i-sell-my-app-to-another-company) Selling an app to another company is more common than most people assume, and the process is far... by [Simon Lee](https://weareaffective.com/learning-centre/author/simon-lee) [![What a Fitness Social App Changed When It Realised Precise Location Was the Wrong Trust Decision](https://weareaffective.com/hubfs/learning-centre-images/what-a-fitness-social-app-changed-when-it-realised-precise-location-was-the-wrong-trust-decision.webp)](https://weareaffective.com/learning-centre/what-a-fitness-social-app-changed-when-it-realised-precise-location-was-the-wron) ### [What a Fitness Social App Changed When It Realised Precise Location Was the Wrong Trust Decision](https://weareaffective.com/learning-centre/what-a-fitness-social-app-changed-when-it-realised-precise-location-was-the-wron) The fitness social app had a sensible idea at its core: find people nearby who want to run or cycle... by [Simon Lee](https://weareaffective.com/learning-centre/author/simon-lee) [![How long should it take to fix a bug in my app?](https://weareaffective.com/hubfs/learning-centre-images/how-long-should-it-take-to-fix-a-bug-in-my-app.webp)](https://weareaffective.com/learning-centre/how-long-should-it-take-to-fix-a-bug-in-my-app) ### [How long should it take to fix a bug in my app?](https://weareaffective.com/learning-centre/how-long-should-it-take-to-fix-a-bug-in-my-app) A client came to us after their development team told them a checkout bug would take three weeks to... by [Simon Lee](https://weareaffective.com/learning-centre/author/simon-lee) [![We Are Affective](https://weareaffective.com/hubfs/we_are_affective_logo_mark.svg)](https://weareaffective.com) 20-22 Wenlock Road London, N1 7GU United Kingdom +44 20 4572 8062 [hello@weareaffective.com](mailto:hello@weareaffective.com) Services [App planning & strategy](https://weareaffective.com/app-planning-strategy) [App design](https://weareaffective.com/app-design-agency) [App UX design](https://weareaffective.com/app-ux-design) [App UI design](https://weareaffective.com/app-ui-design) [App technical architecture](https://weareaffective.com/app-architecture) [Existing app audits](https://weareaffective.com/app-audit) Legal [Privacy policy](https://app.termly.io/policy-viewer/policy.html?policyUUID=b8fa9921-7518-4fb5-8ddd-9dc7f5977ed2) [Terms](https://app.termly.io/policy-viewer/policy.html?policyUUID=8b6a6ad5-91bd-4176-a5f7-6d36b0398f70) Case studies [TravAI](https://weareaffective.com/case-studies/travai) [Meditech](https://weareaffective.com/case-studies/harley) [WorkingWeight](https://weareaffective.com/case-studies/workingweight) [SkinSync](https://weareaffective.com/case-studies/skinsync) [Three Lochs](https://weareaffective.com/case-studies/three-lochs) [Drift](https://weareaffective.com/case-studies/drift) About us [Our Story](https://weareaffective.com/about) [How We Work](https://weareaffective.com/how-we-work) Guides [Creating an app](https://weareaffective.com/how-to-create-an-app) [Building an MVP](https://weareaffective.com/building-an-mvp) [Cost and budgeting](https://weareaffective.com/app-development-cost) [App technology](https://weareaffective.com/app-development) [Planning and strategy](https://weareaffective.com/app-planning-strategy) [User research](https://weareaffective.com/app-user-research) [Onboarding design](https://weareaffective.com/app-onboarding-design) [User psychology](https://weareaffective.com/user-psychology-app-design) [Launch and growth](https://weareaffective.com/app-launch-growth) Copyright © 2026, weareaffective.com. All rights reserved.