Company · Legal
Sources & rights
Where every reference in the library comes from, who it belongs to, and how to ask us to take one down.
Draft — last updated
On this page
01What a reference is
A reference on UI Discovery is an image of a real, shipped product — a website section, a full page, or an app screen — plus details we extract from it, such as colours, fonts, headings and layout. Today the library holds 2,647 websites, 62 web apps and 3,835 iOS apps, broken into 111,073 individual references. Every reference page names its product and links back to where it came from.
02Website and web-app sections
Website references are captured from publicly accessible web pages by our crawler. It loads a page the way a browser does, takes a screenshot, and cuts it into sections — hero, pricing, footer and so on. It also reads the page's public styles to record the palette and fonts.
We capture only what anyone can see without logging in. We don't bypass paywalls, log-ins or access controls.
03App screens
App references come from a few places, and each app page says which applies:
- Public App Store listings — the screenshots a developer publishes on their app's App Store page.
- Recordings and screenshots made by our team — taken while using the app, to show real flows screen by screen.
- Imported collections — a number of app screen sets come from third-party reference archives. Those app pages name the collection as their source.
Text read from screenshots by machine is used to make screens searchable. It can be wrong, and it isn't a verified name for the screen.
04Who owns what
All product designs, screenshots of them, logos and trademarks belong to their respective owners. They appear on UI Discovery for design reference, research and commentary — to show how real products solve design problems. Showing a product doesn't mean its owner endorses UI Discovery or is affiliated with us.
What we add — section labels, extracted palettes and fonts, descriptions, prompts, templates and flow kits — is our own work. Our terms of use explain what you can and can't do with references.
05Provenance and citation
Each reference records its source product, capture date and, where it came from a third party, that collection. Use the API or /llms-full.txt for machine-readable provenance, and /api/v1/facts for current counts. When citing a reference, link to its page on UI Discovery and to the original product.
06By the numbers
As of 2026-11-09: 2,647 websites, 62 web apps, 3,835 iOS apps, 111,073 sections, 94,131 graphics. Machine-readable: /api/v1/facts and /llms-full.txt.
07Removal requests
If you own or represent material shown on UI Discovery, or a reference exposes your personal information, visit Request content removal for the request process and contact details. Please include:
- the UI Discovery link(s) to the reference, app or website;
- your name and your connection to the product (for example, you work there or represent the owner);
- whether you want specific screens removed, or the whole product.
We review requests and may ask for clarification before taking action.
08Corrections
If a reference is mislabelled, out of date, or credited to the wrong product, email townmedialabs@gmail.com with the link and what's wrong, and we'll fix it.