Book a call
Max Tymoshyn, founder of Norml Studio
Max TymoshynFounder, Norml Studio

Mobile app UX and UI design: flows, screens and a prototype to try on a phone

We design apps that people use mostly on a phone: the flows they follow, the screens and the states each one can be in, and a clickable prototype your team tries on a real device before development. The work can start with a new idea, with reference screens you already have, or with an app your team has already built. Developers receive organized Figma files with the components, states and notes they need to build it.

A few clients we’ve worked with

99Legal / Kremenchuker Law GroupAstraZenecaCoxitDiet vs DiseaseFlorida seal — Regional Counsel projectMetroplex HomebuyersNasdaq Private MarketOffice of Criminal Conflict and Civil Regional Counsel, Second Region of Florida — Ita M. NeymotinPolaclubThe Farm Soho

What we do

Norml owns the design side of a mobile app: how people move through it, what each screen shows, and the Figma components and prototype the developers build from. Native development, backend services and app-store release stay with your development team.

What mobile app design covers

A project can be a first prototype, new features for an existing app, or a refinement of screens already in use. Every part is designed for the phone first and uses one shared component set.

Solution
Websites
  • User flows and a screen mapWe map the steps people take to finish the app's main tasks, such as signing up, finding a product or a specialist, or paying, and list each screen and decision point along the way. The screen map is agreed before visual design starts.
    01
  • Wireframes before visual designLow-fidelity wireframes settle the content, order and navigation of each screen. Visual design begins once your team approves them, while structural changes are still quick to make.
    02
  • Every screen with its statesHigh-fidelity screens in your visual direction, each drawn with its loading, empty, error and success states, plus what people see offline or after they decline a permission such as location or notifications.
    03
  • A clickable prototype on a phoneThe main flows linked in Figma with real content, transitions and the key error states, so tapping through it on a phone feels close to the finished app. It is the version your team and test users try before development.
    04
  • A component system for the appColors, type, spacing, icons, buttons, cards, inputs and navigation set up as Figma components with variants. New screens reuse them, so features added later match the rest of the app.
    05
  • Refining an app you already haveWhen the interface exists only in the built app, we capture its screens, list the styles and components it actually uses, and fix the most-used screens first. The agreed versions become Figma components your developers apply to the current code.
    06
  • Maps, nearby results and routesA map with a matching list, filters, saved searches and route screens, including the states for location access turned off or no results nearby. Your developers' services calculate distances and routes; we design how people see and change them.
    07
  • Store, checkout and order statusStore and product browsing, cart, checkout, order confirmation and tracking, with a screen for each status your system records, delays and cancellations included. In a service app, appointments, messages and progress updates follow the same pattern.
    08
Josiah BallCo-Founder & CEO, HOMEEC

“Norml Studio's professionalism and responsiveness were impressive.”

Clutch review
Lucas SeyhunCEO, The Farm Soho

“They were proactive in suggesting improvements we hadn't considered.”

Clutch review
Gaius CooperDirector, Streamline Pump Solutions

“They delivered what they said they would, on time.”

Clutch review
Emma EstefaClient Success Manager, Metroplex Homebuyers

“They focused on how to make our daily operations easier, not just on building features for the sake of it.”

Clutch review
Bret MillerManager, Door Knock Pro

“They understood that the app needed to be practical for someone sitting in a car, not just look good on a desktop.”

Clutch review
Saima AhmedFounder, GoPetZen

“Their level of dedication to the success of the project and GoPetZen's business as a whole is unique.”

Clutch review

What we need from you

  • The idea and its main tasksWhat the app is for, who uses it and which tasks they must be able to finish, plus any requirements, notes or reference screens you already have.
    01
  • Brand files or a directionLogo, colors, fonts and brand guidelines. If the app has no visual direction yet, the first design round sets one with you before the remaining screens.
    02
  • The current app, if there is oneA test build or the released app, screenshots or screen recordings, and a walkthrough of the journeys people use most.
    03
  • Your development setupWho builds the app, whether it is native, cross-platform or a web app, and any component library they already use, so the designs match what they will build.
    04
  • The person who approves designsSomeone who approves each design round and settles conflicting comments, so every round ends with a clear decision.
    05

How a mobile app design project runs

  1. [Inputs and the screen list]

    We read your requirements, brand files and any existing screens or builds, then agree the flows and screens in scope and the limits your developers' platform sets.

    Step 01
  2. [Flows and wireframes]

    We map the main flows and lay out each screen in low fidelity. Your team clicks through them on a phone before visual work starts.

    Step 02
  3. [Screens and components]

    Approved wireframes become high-fidelity screens built from one component set, with every state drawn and text contrast and touch target sizes checked.

    Step 03
  4. [Prototype sessions]

    Your team runs the main tasks in the prototype, then target users do the same when you can invite some. We revise the screens after each session.

    Step 04
  5. [Handoff to developers]

    Developers receive organized Figma files: screens, states, components with their variants, spacing and type values, and notes on gestures, transitions and error messages.

    Step 05
  6. [Design check of the build]

    When a build is ready, we compare it with the designs on real phones and list what to fix before release.

    Step 06

The people who do this work.

Meet the whole team

No account layer between you and them. These are the Norml specialists this work runs through.

Max Tymoshyn, founder of Norml Studio

Let's chat

“I've spent 10 years working across development and marketing. I started as a developer, but design, SEO and advertising were already part of the job. That taught me to treat a website as one system: the business, the content, the design and the code have to work together. At Norml, I lead the architecture behind our work and stay involved wherever strategy, design, development and search meet.”

Max TymoshynFounder & Architect

From the Norml blog.

Questions about mobile app design

Who builds the app after the design?
Your developers or agency, working from the handoff files; we answer their questions while they build. When the product is a web application, Norml can also build it as a separate stage.
Which platforms do you design for?
Phones first, then tablets or desktop where the product needs them. Before screens are drawn, we confirm with your developers whether the app is native iOS, native Android, cross-platform or a progressive web app, because that decides which navigation patterns, system controls and prompts the screens use.
Will refining our app mean redesigning all of it?
No. The structure people already know stays unless it blocks a main task. Changes are delivered as components your developers apply one screen at a time, so the app keeps working while it is refined.
Can you start from screens we already have?
Yes. We check them against the flows first and keep what works. The visual direction is then set for your product instead of copied from the references or from competing apps, and the remaining screens follow it.
Can you design screens that show a score or recommendation from a model?
Yes. Your team decides how the score is calculated and when it appears. We design how it is shown, the short reason beside it, and what people see when it is missing or looks wrong to them.
Can you design screens before the data behind them exists?
Yes. We list the fields each screen shows, for example an item's current value and when it last changed, and fill the designs with realistic sample records. Missing and out-of-date values get their own states, charts are drawn at phone width first, and your developers receive the field list with the designs.
Can the app share a design system with our website?
Yes. The app can start with the website's colors, type and components, adapted for touch and small screens, while app patterns such as tab bars, bottom sheets and status screens join the same library. Designing the website itself is a separate project; when it comes first, its system is set up so the app can extend it later.
Which parts of an app project are not included?
The data and rules behind features such as prices, scores and routes, and the app's store listing. Changes to the logo or app icon are brand work, added as their own item when you need them.

See more of our design and product work

Read what each project needed and which screens and flows we designed for it.

See all case studies