Skip to main content

ScreensDesign Alternatives: 9 Places for Real App Screens

ScreensDesign alternatives compared: Mobbin, Page Flows, Refero and more, with what each library is best for and how to turn references into your own screens.

Roundups11 min read2,022 words

If you use ScreensDesign to study how real apps handle onboarding, paywalls and subscription flows, you have probably wondered whether another library would fit your work better. This guide is for founders, PMs and designers who need real app screen examples, not concept shots. You get nine alternatives, what each one is actually good for, and a workflow for turning references into screens of your own.

TL;DR: Mobbin is the broadest library of real iOS, Android and web screens; Page Flows is strongest for recorded end-to-end flows; Refero is a fast, well-tagged option for web and iOS. For paywalls and App Store presentation, combine a library with first-hand recordings of the apps you compete with. A library shows you what exists; you still have to design what fits your product.

What ScreensDesign is good at (and why people look elsewhere)

ScreensDesign is a reference library built around real mobile apps, with a strong focus on the parts of an app that drive revenue: onboarding, paywalls, subscription upsells and the flows around them. Its value is that you see what shipping apps actually do, not what a designer imagined on Dribbble.

People look for alternatives for a handful of practical reasons:

  • •Coverage. They need Android, web or SaaS dashboards, or a category the library covers thinly.
  • •Format. Some people want static screenshots they can drop into a moodboard; others want video of the full flow with transitions.
  • •Search. Finding "every app that asks for notification permission on screen three" depends on how well a library tags screens by pattern, element and flow.
  • •Budget and team access. Most serious libraries are paid, and seat pricing matters for small teams. Check current pricing on each site, because plans change often.

Keep those four criteria in mind as you read the list.

The 9 best ScreensDesign alternatives

1. Mobbin

Mobbin is the library most designers name first. It covers iOS, Android and web apps, organised by app, by screen type (login, checkout, settings, empty state) and by UI element (bottom sheet, toast, stepper). It also groups screens into flows, so you can step through a sign-up from start to finish.

  • •Best for: broad pattern research across platforms and categories.
  • •Strengths: large catalogue of well-known apps, strong filtering, flows as well as single screens, copy-to-Figma for screens.
  • •Watch out for: breadth over depth on monetisation; if paywall testing is your main job, you will want recordings of the specific competitors you care about.

We compared it in depth in our Mobbin alternatives roundup if you want the next layer of detail.

2. Page Flows

Page Flows records real user journeys as video and screenshots: onboarding, cancelling a subscription, inviting a teammate, upgrading a plan. Each flow is captured end to end, so you see loading states, error messages and the emails that follow an action.

  • •Best for: understanding a complete journey, including the moments between screens.
  • •Strengths: video captures transitions and timing that static screenshots miss; covers web and mobile.
  • •Watch out for: the catalogue is organised around flows, so it is slower for "show me 30 tab bars" style browsing.

3. Refero

Refero is a reference library for web and iOS with detailed tagging by page type, UI element and pattern. Its search is fast and the screenshots are clean, which makes it a good day-to-day tool when you are designing a specific screen and want ten examples in a minute.

  • •Best for: quick, well-tagged lookups while designing.
  • •Strengths: search quality, consistent capture quality, good SaaS and web coverage.
  • •Watch out for: Android coverage is lighter than Mobbin's, so check it fits your platform mix.

4. Screenlane

Screenlane collects UI screens and components from web and mobile apps, with a newsletter of recent additions. It is lighter than the big libraries but useful for keeping a steady stream of fresh examples coming.

  • •Best for: passive inspiration and trend-spotting.
  • •Watch out for: smaller catalogue; not a replacement if you need systematic research.

5. Pttrns

Pttrns is one of the original mobile pattern libraries, organised by pattern (activity feeds, calendars, maps, sign-up). It is older and updated less often than newer libraries, but the pattern-first structure is still a sensible way to think about screens.

  • •Best for: classic pattern categories and historical context.
  • •Watch out for: some examples are dated; always check the live app before copying a pattern.

6. Nicelydone

Nicelydone focuses on SaaS web products: onboarding, settings, billing pages, empty states and dashboards, often captured as flows. If your "app" is a web dashboard rather than a phone app, it is more relevant than a mobile-first library.

  • •Best for: B2B SaaS and web app flows.
  • •Watch out for: little or no native mobile coverage.

7. App Store and Google Play listings

The stores themselves are an underused library. Product pages show how competitors frame their value in screenshots, which features they lead with, and how they describe in-app purchases. For paywall and pricing research, the in-app purchase list on a product page tells you which price points an app sells.

  • •Best for: positioning, store screenshots and pricing signals.
  • •Watch out for: store screenshots are marketing, not the real UI. Use them to understand the pitch, then check the app.

For a teardown-style view of store screenshot sets, browse floow's ASO screens library and our App Store screenshots guide.

8. Your own screen recordings

The most accurate reference library is the one you build. Install the five apps you compete with, start the built-in screen recorder on iOS or Android, and go through onboarding, the paywall, the core task and cancellation. You see the current version, in your region, with the experiments you are bucketed into.

  • •Best for: competitive research on the exact apps that matter to you.
  • •Strengths: current, free, complete. You catch permission prompts, timing and haptics that libraries cannot.
  • •Watch out for: paywalls and onboarding are often A/B tested, so a second account or device may see something different. Respect the apps' terms and never publish other people's UI as your own.

9. Dribbble and Behance (with care)

Dribbble and Behance are full of beautiful concept work, which is exactly the problem: much of it never shipped and never met real content, real edge cases or real users. Use them for visual direction (colour, illustration, type mood) and use the libraries above for patterns.

  • •Best for: visual mood and style exploration.
  • •Watch out for: unrealistic content lengths, missing states and contrast that fails accessibility checks.

Comparison table

LibraryPlatformsFormatBest forMonetisation depth
ScreensDesignMobileScreens and recordingsOnboarding and paywallsHigh
MobbiniOS, Android, webScreens and flowsBroad pattern researchMedium
Page FlowsWeb, mobileVideo and screensEnd-to-end journeysMedium
ReferoWeb, iOSScreensFast tagged lookupsMedium
ScreenlaneWeb, mobileScreensFresh inspirationLow
PttrnsMobileScreensClassic patternsLow
NicelydoneWeb SaaSScreens and flowsB2B dashboardsMedium
App storesiOS, AndroidStore pagesPositioning, pricingHigh (pricing only)
Your recordingsWhatever you installVideoDirect competitorsHighest

"Monetisation depth" is a judgement of how useful each source is for paywall and upgrade research, not a measured score.

How to choose in two minutes

  1. •Mobile-only consumer app with subscriptions? Keep ScreensDesign or pair Mobbin with your own recordings of direct competitors.
  2. •Cross-platform app that needs Android references? Mobbin first.
  3. •Web dashboard or SaaS? Refero or Nicelydone.
  4. •Need to understand a whole journey, including emails and error states? Page Flows.
  5. •Tight budget? App stores plus your own recordings cost nothing and are often more accurate.

A workflow for turning references into your own screens

A library is only useful if you leave it with decisions, not a folder of screenshots. This is the process that works for most small teams.

  1. •Write the question first. "How do top meditation apps ask for notification permission?" is a research question. "Look at meditation apps" is browsing.
  2. •Collect 8 to 12 examples of one screen type. Fewer and you copy one app; more and you stop noticing differences.
  3. •Annotate what varies. For a paywall: trial length shown or not, annual plan pre-selected, close button position, social proof, number of plans. A simple table works.
  4. •Spot the convention and the outliers. If nine apps put the close button top-left and one hides it, the convention is what users expect. The outlier is either a deliberate experiment or a dark pattern.
  5. •Decide your version in one sentence per element. "Two plans, annual pre-selected, monthly price shown for both, close button visible from the first frame."
  6. •Design with your real content. Your product name, your prices, your longest localised string.
  7. •Test it on a device before you polish anything. Our guide to usability testing a mobile app covers quick, cheap ways to do this.

Reference annotation template

Copy this into a doc or spreadsheet for each screen you research.

Screen type:        Paywall
App / version:      Example App, iOS, recorded on 2026-11-01
Entry point:        After onboarding question 5
Plans shown:        2 (annual pre-selected)
Trial:              7-day free trial on annual only
Close control:      X top-left, visible immediately
Price framing:      Annual shown as per-week price
Social proof:       Rating + one testimonial
Primary CTA copy:   "Start free trial"
Legal text:         Under CTA, small
What I would steal: Plan comparison layout
What I would skip:  Per-week framing (feels evasive for our audience)

Common mistakes when using screen libraries

  • •Copying the market leader wholesale. Their paywall is tuned to their brand, traffic and price. Yours is not.
  • •Ignoring states. Libraries mostly capture happy paths. You still need empty, loading and error states; see our empty state design guide.
  • •Treating screenshots as specs. Screenshots rarely tell you tap target sizes, safe areas or dynamic type behaviour. Check platform rules separately.
  • •Researching forever. Set a time box: one hour per screen type is usually plenty.

Once you have your notes, you can generate a first draft of the screen in floow from a written description of your decisions, then compare it against your references side by side.

FAQ

Is there a free alternative to ScreensDesign?

The App Store, Google Play and your own screen recordings are free and often more accurate for direct competitors. Most dedicated libraries offer a limited free tier and paid plans for full access, so check current pricing on each site.

Is Mobbin better than ScreensDesign?

They overlap but lean differently. Mobbin is broader across platforms, categories and UI elements; ScreensDesign leans into onboarding, paywalls and subscription flows. Many teams pick based on whether they need breadth or monetisation depth.

Can I copy screens from these libraries into my app?

Use them to learn patterns, not to copy branded UI. Common patterns like tab bars or sign-in forms are fine to follow, but copying another company's distinctive visual design, illustrations or copy can create legal and brand problems.

Which library is best for paywall examples?

A monetisation-focused library plus your own recordings of competitors is the strongest combination, because paywalls are heavily A/B tested and change often. Our paywall screen design guide explains what to look for.

Design it with floow

Once your references have turned into decisions, describe the screen and let floow draft it on a real device frame. Try: "Design an iOS paywall for a meditation app with two plans, annual pre-selected with a 7-day trial, a visible close button top-left, one testimonial and a 'Start free trial' button."

Design your mobile app with AI.

Generate pixel-perfect iOS and Android screens in seconds, then export to Figma or code.