1. PageFlows
A polished interface can look convincing while revealing very little about how the product actually works. PageFlows focuses on recorded user flows, app screens, and UI patterns from real products. It covers web, iOS, Android, and email experiences. This makes it useful when the research question involves a sequence of actions rather than a single attractive screen. Onboarding, checkout, search, account upgrades, and other common tasks can be studied as connected experiences.
For designers looking for UI inspiration, the useful part is the context around each screen. A button can be evaluated together with the state that follows it. A form can be compared with the steps that came before it. This makes it easier to study product decisions instead of collecting disconnected screenshots.
2. Landbook
Landbook is a curated collection focused on website design. References can be explored by categories, page types, and individual website sections. This works well when the task involves landing pages, pricing pages, portfolios, ecommerce sites, or marketing pages. Complete websites also make it easier to see how typography, navigation, content, and layout work together.
A homepage rarely exists as an isolated design problem. Looking at the rest of the site can reveal whether a visual idea remains consistent across several pages. That is useful when building a system rather than copying one strong hero section. Landbook provides enough surrounding context to make those comparisons practical.
3. Refero
Refero collects real web and mobile interface references and organizes them around pages, patterns, and elements. The structure is useful when there is already a clear research question. A designer can look for navigation, pricing, search, dashboards, or other familiar product areas. This reduces the amount of unrelated browsing and keeps research closer to the problem being solved.
4. SaaSFrame
SaaSFrame focuses on SaaS websites, product interfaces, and email sequences. That combination matters because many SaaS experiences begin before a user enters the dashboard. Pricing, signup, onboarding, billing, upgrade messages, and retention emails can all influence the overall experience. Researching them together gives more context than looking at the app screen alone.
Some useful areas to compare include:
- landing and pricing pages
- onboarding sequences
- dashboard layouts
- product emails
- upgrade and conversion screens
A signup flow can make more sense after reviewing the pricing page that sends users into it. An upgrade screen can also be easier to evaluate when its surrounding product context is visible. SaaSFrame is especially relevant when acquisition and product design need to be considered together. It keeps the research centered on real SaaS experiences rather than abstract concepts.
5. Nicelydone
Nicelydone collects SaaS screens, user flows, and interface components from real products. It can be useful when one screenshot raises more questions than it answers. A dashboard, settings page, filter, or onboarding step can be viewed within a wider product context. That makes it easier to understand which choices belong to a broader system.
Research can start with a whole product and then narrow toward a specific component or flow. This works well during early exploration when the exact design question is still changing. Instead of saving the first attractive reference, several related screens can be compared first. That often reveals patterns that are easy to miss in standalone images.
6. SaaS Interface
SaaS Interface concentrates on SaaS application design. Its narrow focus is useful for projects built around dashboards, tables, account settings, filters, navigation, and other common business software patterns. Consumer app examples often solve different problems and may not transfer well to these products. A focused SaaS collection gives designers references that operate under more similar constraints.
The value is not limited to visual styling. Dense business interfaces need clear hierarchy and predictable interaction patterns. Comparing several real examples can show how different products handle similar amounts of information. That can be more useful than searching for a visually striking dashboard concept.
7. ScreensDesign
ScreensDesign, available through the UISources domain, focuses on real iOS screens and mobile flows. It includes areas where mobile conventions matter strongly, including onboarding, paywalls, navigation, and other recurring app experiences. Keeping the research inside one device category removes many irrelevant desktop patterns. This can make comparisons more consistent.
8. Design Systems Repo
Design Systems Repo collects public design systems, pattern libraries, style guides, articles, and related resources. It is useful when screenshots show what an interface looks like but not why it was built that way. Design system documentation can explain component usage, spacing, content rules, accessibility decisions, and visual standards. Those rules often reveal more than the finished screen.
A strong design reference should answer more than one question. It can show how a component looks, when it should appear, and what should happen in different states. Public design systems can provide that extra layer of information. They are especially useful when a team needs consistency across many screens rather than one isolated design.
9. The Component Gallery
The Component Gallery organizes examples of common interface components across multiple design systems. Designers can compare tabs, pagination, accordions, empty states, popovers, alerts, and many other recurring elements. This is useful when the broader page structure already works and the open question is smaller. Instead of searching through complete websites, the research can stay focused on one component.
Some details worth checking across systems are:
- naming and labels
- component states
- accessibility guidance
- interaction behavior
- usage recommendations
The differences can be more informative than the similarities. Two organizations may use the same component but document different rules around it. That shows where design decisions depend on context rather than convention. Component research becomes more useful when those rules are considered alongside appearance.
A Better UI Inspiration Habit Starts With the Question
No single source fits every design problem. User flow libraries help with sequences, website galleries help with complete pages, SaaS collections help with business software, and design systems help explain reusable rules. The best starting point depends on what needs to be learned. Choosing the source before defining the question usually leads to unnecessary browsing.
A more useful research process is to define the interaction first, collect several real examples, compare how they solve the same problem, and then return to the needs of the current product. The goal is not to reproduce the most attractive reference. It is to understand why certain decisions appear repeatedly and where products choose different approaches. Good inspiration becomes evidence for a design decision rather than decoration for a mood board. That makes real interfaces far more useful than concepts that were never required to survive actual users, content, and product constraints.
