Mobbin

The world's largest UI & UX design reference library

4.8•36 reviews•

3.1K followers

The world's largest UI & UX design reference library

4.8•36 reviews•

3.1K followers

Visit website

Design inspiration websites

•

Figma Plugins

•

Design resources

Mobbin is the Pinterest for UI & UX design. We are building a comprehensive, expert-curated library of interfaces from the best-in-class digital products that helps product designers find relevant design inspiration and references with significantly less time and effort.

The Best Mobbin Alternatives

The best Mobbin alternatives are Refero, appshots , UXArchive, Growth.Design Case Studies, and Checklist Design.

Refero

4.9 ·

Choose Refero if...

✓you want ai to synthesize design recommendations
✓you prefer real products over dribbble shots
✓you want to browse without signing up first

See details ↓

appshots

5.0 ·

Choose appshots if...

✓you need video recordings of ux journeys
✓you care about motion timing and transitions
✓you want industry categories for faster discovery

See details ↓

UXArchive

5.0 ·

Choose UXArchive if...

✓you want flow references tied to waldo testing
✓you work primarily on mobile app experiences
✓you need quick examples for qa scenarios

See details ↓

Growth.Design Case Studies

5.0 ·

Choose Growth.Design Case Studies if...

✓you want the psychology behind ux patterns
✓you prefer bite sized learning over browsing screens
✓you care about ethical growth strategy guidance

See details ↓

Checklist Design

4.8 ·

Choose Checklist Design if...

✓you need qa checklists for ui completeness
✓you want structured guidance as a newer designer
✓you value linked references for deeper learning

See details ↓

What to Consider

Mobbin is a go-to reference for designers who want a large, searchable library of real app screens and flows for fast UI benchmarking. The alternatives landscape spans very different modes of “design research”: Refero leans into AI/agent-led synthesis on top of real product examples, Appshots is video-first for seeing UX journeys in motion, UXArchive overlaps with mobile-flow research but sits closer to testing workflows via Waldo, while Growth.Design Case Studies teaches the psychology and rationale behind patterns and Checklist Design shifts the focus to QA-style completeness rather than inspiration.

In evaluating Mobbin alternatives, the key considerations were library depth and freshness (especially full flow coverage), how easy it is to find and organize references (search, filters, collections, and shareability), workflow fit (solo browsing vs team critique/reviews), and practical friction points like pricing, trial/ungated access, and integration readiness (including agent/MCP-style usage).

Refero

Design research for humans and AI

4.9 · 16 reviews

Learn more →

Refero is built for teams that want design research to feel closer to synthesis than scavenger hunting. Instead of only browsing a giant catalog like Mobbin, it leans into an AI/agent-first workflow that can pull multiple real-product references and help summarize direction quickly.

A big reason to use it is the emphasis on “real product” grounding, which makes it easier to benchmark practical UX patterns instead of polished concept shots. Strong filtering and search make it fast to zero in on onboarding, pricing, dashboards, and other recurring SaaS surfaces, and collections help package findings for critique sessions.

Refero can also be lower-friction for quick research because some browsing works without forcing immediate sign-up. The main trade-off versus Mobbin is that flow grouping and app-flow depth may feel less like a perfectly curated, end-to-end library in certain areas, so it’s best when speed and synthesis matter more than exhaustive flow coverage.

Best for

Best for product designers and teams who want AI-assisted benchmarking and shareable collections for design reviews.

Standout features

✓AI/agent-led research and synthesis
✓Real-product examples, not concept galleries
✓Powerful filters and fast search
✓Collections for sharing and reviews

appshots

For design research that is tedious and boring

5.0 · 2 reviews

Learn more →

Appshots stands out by prioritizing video over static screenshots. That makes it a compelling alternative to Mobbin when the “how it behaves” details matter—timing, motion, progressive disclosure, and the way a flow actually unfolds.

Because the library is organized around UX journeys, it’s well-suited to end-to-end benchmarking rather than isolated screens. Industry categorization helps narrow the search when patterns differ by domain, like fintech vs marketplaces vs productivity.

Appshots also tends to be easy to evaluate before committing, which is useful when a team is comparing tools or only needs occasional access. The practical trade-off is that it’s less about building a massive, screen-by-screen reference archive and more about observing real interactions in context.

Best for

Ideal for designers and PMs who want to watch real app flows and compare interaction behavior.

Standout features

✓Video-first UX journey recordings
✓End-to-end flow benchmarking
✓Industry-based browsing and discovery
✓Frequently updated pattern library

UXArchive

The world's largest library of mobile user flows

5.0 · 1 review

Learn more →

UXArchive is a strong fit when UX inspiration needs to sit closer to delivery and QA, not just ideation. It’s connected to Waldo’s mobile testing world, which makes it easier to move from “this is the pattern” to “this is what we should test.”

Compared with Mobbin’s research-centric browsing, UXArchive is most compelling for teams that want mobile flow references with an eye toward validation and repeatable scenarios. It can support faster alignment between design, product, and QA by giving everyone a shared view of common mobile journeys.

The trade-off is that it’s less about being the broadest cross-app inspiration database and more about being a practical companion for mobile teams that want reference flows they can operationalize.

Best for

Best for mobile teams that want flow references aligned with testing and QA workflows.

Standout features

✓Mobile flow library for quick benchmarking
✓Adjacent to Waldo mobile testing workflows
✓Useful for defining QA test scenarios
✓Fast reference for common mobile journeys

Growth.Design Case Studies

Product tips in a comic book format

5.0 · 10 reviews

Learn more →

Growth.Design Case Studies focuses on the reasoning behind patterns, not just collecting examples of them. As an alternative to Mobbin, it’s valuable when the goal is to make better decisions—grounded in psychology and ethics—rather than finding the nearest comparable screen.

The case-study format turns common growth and onboarding tactics into clear narratives, so teams can understand cause and effect instead of copying UI. That makes it especially useful for aligning designers, PMs, and marketers on what to do and what to avoid.

It’s also easier to consume in short bursts than a reference library, which helps when time is limited or when onboarding newer team members. The trade-off is that it won’t replace a screen database for pixel-level UI references, but it can significantly improve the “why” behind the choices a team makes.

Best for

Best for teams and learners who want psychology-backed guidance for onboarding and growth decisions.

Standout features

✓Psychology-driven UX and growth lessons
✓Ethical growth strategy emphasis
✓Digestible, story-based case studies
✓Actionable takeaways for real products

Checklist Design

The best UI and UX practices for production ready design.

4.8 · 11 reviews

Learn more →

Checklist Design flips the usual inspiration workflow into a quality-assurance workflow. Instead of competing with Mobbin as a screen library, it complements (or replaces) it when the priority is shipping clean, complete UI without missing critical details.

The core value is structured checklists across UI and UX topics, which helps standardize quality across a team and reduces rework before handoff. It’s particularly helpful for newer designers who want confidence that accessibility, states, content, and edge cases have been considered.

Many checklist items include reference links, turning a quick QA pass into lightweight learning and a shared standard. The trade-off is component coverage depth can vary, so it works best as a consistent gate in the workflow rather than the only source of UI examples.