Onboarding that doesn't feel like an interview
Three steps, no progress bar gymnastics, and a sensible default at every fork. The onboarding variants in the Webapp Parts collection cover the patterns Arc, Notion, and Linear actually use.
For consumer products
Onboarding, empty states, modals, motion, and the consumer landing pages worth copying — with prompts that produce real components, not demos.
Consumer products live or die on the first ninety seconds: the hero, the onboarding, the first empty state, and the first piece of feedback the app gives the user. onedb collects the patterns the best consumer teams ship — Apple, Arc, Linear, Notion — and pairs each one with the references and the prompts so your version doesn't look like a tutorial. If you build for consumers, this is the reference desk to keep open.
Learn from the best examples for each part of the web
OpenHandpicked from the best of the web.
OpenAnimation libraries, scroll choreography, and illustration packs.
OpenTypefaces, palettes, and icon sets you should use.
OpenThe kits people actually paste into their apps.
OpenThree steps, no progress bar gymnastics, and a sensible default at every fork. The onboarding variants in the Webapp Parts collection cover the patterns Arc, Notion, and Linear actually use.
An empty state is the most-viewed screen in your app. We cover the variants that convert, the ones that delight, and the ones that just take up space.
Framer Motion, GSAP, Rive, Lottie. The Motion & Illustration collection ranks them by where they earn their bytes — and where they don't.
Both. The patterns under app-structure are framework- and audience-agnostic — pricing and dashboards lean B2B, while onboarding, empty states, modals, notifications, and motion lean consumer.
Yes. Many parts are tagged for web + mobile + desktop. The platform tag on each category tells you where the pattern is grounded.