Choose the Library by the Design Question
A useful UX inspiration library should answer a design question, not simply provide more screenshots. Product designers need different references when working on onboarding, checkout, mobile navigation, pricing, account settings, or SaaS dashboards. Complete journey libraries are better for sequence decisions, while large screen collections make visual comparison easier. Website galleries help with public facing pages but are less useful for studying what happens after sign in. Microinteraction collections solve another problem by showing how small moments of feedback and motion are handled. The best resource therefore depends on the task sitting in front of the designer.
|
Library |
Best use |
|
Page Flows |
Complete journeys, onboarding, checkout, UX research |
|
Mobbin |
Broad mobile and web screen research |
|
SaaSFrame |
SaaS pages, product interfaces, email sequences |
|
Nicelydone |
SaaS flows, screens, and UI components |
|
Refero |
Web and iOS reference research |
|
ScreensDesign |
iOS onboarding, paywalls, mobile screens |
|
Lapa Ninja |
Landing pages and full website references |
|
Landbook |
Website sections, ecommerce, visual direction |
|
Godly |
Current visual ideas and motion |
|
Design Spells |
Microinteractions and small interaction details |
The 10 Best UX Inspiration Libraries by Use Case
For complete sequence research, page flows is useful because it organizes real product experiences around recorded user flows, app screens, and UI patterns. Its flow library includes onboarding and checkout, so the order of steps can be studied instead of treating every screen as an isolated reference. The collection also covers web and mobile experiences, which helps when the same product problem appears in more than one environment. Mobbin serves a different need with a very large searchable collection of mobile and web app screenshots. It is a stronger fit when the goal is to compare many implementations of navigation, settings, search, cards, or account pages. Together, the two resources cover both journey level research and broad screen comparison.
SaaSFrame is built around recurring SaaS design needs, including product interfaces, landing pages, onboarding, dashboards, and email sequences. That focus makes it useful when the assignment starts with a familiar SaaS problem rather than a broad request for inspiration. Nicelydone also centers on SaaS and web apps, with screens, complete user flows, and UI components from real products. Its search and filtering make it practical for narrowing a large research question to a specific page or pattern. SaaSFrame fits well when the brief is tied to a SaaS conversion or product scenario, while Nicelydone works well for studying a broader SaaS interface system.
Refero covers web and iOS references and organizes its collection through page types, UX patterns, UI elements, fonts, and other filters. It works well when the research starts broad and needs to be narrowed through several visual or structural criteria. ScreensDesign has a tighter mobile focus, with real iOS screens, onboarding flows, and paywalls. That makes it particularly relevant for mobile products where activation and monetization are central design questions. Refero offers wider reference discovery, while ScreensDesign gives more direct access to common mobile product moments.
Lapa Ninja is mainly useful for landing page research, with thousands of real page examples plus full website screenshots and filtering across many categories. Landbook also focuses on websites, but its filters extend across industry, style, type, typography, and site technology. These collections are most valuable when the assignment concerns a marketing site, ecommerce presentation, product page, or public facing section. They should not replace full flow research when the core question is what happens across several product steps. Their strength is giving product designers a fast way to compare page structure and visual direction before building the public layer around a product.
Godly and Design Spells are better used later in the process. Godly curates current design work across websites, app screenshots, motion, and other visual categories. Design Spells focuses on microinteractions, small details, and playful interaction ideas found in digital products. Neither is primarily about mapping a complete onboarding or checkout sequence. Their value appears once the main structure is clear and the designer needs references for motion, feedback, transitions, or small interface behaviors. This makes them useful complements to flow and screen libraries rather than replacements for them.
A Better Way to Use UX Inspiration
The useful habit is to search by decision instead of browsing by mood. If the problem is onboarding sequence, begin with recorded journeys. If the problem is a SaaS dashboard, move to collections with dense product screens and components. Landing page work belongs in a website focused library, while mobile paywalls deserve a mobile focused collection. Microinteraction references make more sense after the core flow has already been defined. This order keeps research connected to a real product question and reduces the amount of irrelevant material a designer has to sort through.
There is also no reason to choose one permanent favorite for every project. A small research stack works better because each library can handle a specific stage of the work. One resource can establish the sequence, another can widen the screen comparison, and a third can help refine visual or interaction details. Comparing several products also makes it easier to identify recurring patterns without following one competitor too closely. The strongest research process is not the one with the most saved screenshots. It is the one that turns references into clearer design decisions.

