Appllama/top-welcome-screens: Ten Animated Expo Welcome Screens You Can Copy
How top iOS apps say hello | 10 animated welcome screens inspired by top-earning apps. Rebuilt in React Native + Expo.
At a glance
- What is it?
- A GPL-3.0 React Native Expo gallery of ten welcome and onboarding screen studies, each a standalone TypeScript component with an authored motion timeline. Useful as a reference for motion and layout, not as shippable branding.
- Who is it for?
- Adopt it if you are building an Expo app and want to study how a specific entrance animation is structured before writing your own, or if you want a coding agent to port one component into an existing repository. Do not adopt it if you need branded, release-ready screens, or if your app cannot carry GPL-3.0 code.
- Can I use it commercially?
- Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
- Is it still maintained?
- Yes. The repository last received commits 106 days ago.
- What is it written in?
- Mainly TypeScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 22, 2026, and from our analysis. They are not legal advice.
Star history
- Appllama/top-welcome-screens616 ★ · +32
| Repository | 2026-09-17 | 2026-11-22 |
|---|---|---|
| Appllama/top-welcome-screens | 584 | 616 |
32 Stars in the last 66 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
What top-welcome-screens actually is, and who it is for
The README describes the project as a collection of animated splash screens, loading screens, welcome screens and onboarding UI studies inspired by leading iOS apps. It is not a component library in the usual sense. It is a gallery app plus ten full-height TypeScript components, each named after the app that inspired it: DuolingoWelcome, StravaWelcome, MyFitnessPalWelcome, PerplexityWelcome, YazioWelcome, OnxHuntWelcome, SpeakLearnWelcome, HallowWelcome, ScrlWelcome and SpeakLanguageWelcome.
The intended reader is a React Native developer who already has an Expo project and wants to see how a polished entrance sequence is put together: which value animates, in what order, over how long. The README frames it as a resource "built for developers studying how polished mobile onboarding works", and the components ship with an authored timeline, responsive scaling, reduced-motion handling, accessible actions and a deterministic final-state mode.
That framing matters for expectations. If you want a drop-in onboarding flow with your own copy and colors, this is not it. If you want to read one file and understand why an animation lands the way it does, it is a good deal more useful than a screenshot gallery.
How the motion is structured: one component per screen, one timeline per component
Every screen lives at a predictable path under src/welcome-screens/, for example src/welcome-screens/duolingo.tsx or src/welcome-screens/onx-hunt.tsx. Animation runs on React Native Reanimated rather than the Animated API. Shared helpers and types sit in src/welcome-screens/shared/ and src/welcome-screens/types.ts, and the README notes that a component should be copied along with only the transitive imports it actually uses.
Each screen carries a screen ID (duolingo, strava, myfitnesspal, perplexity, yazio, onx-hunt, speak-learn, hallow, scrl, speak-language) and a set of typed semantic action IDs such as duolingo.get-started. Those IDs are the hook for automation and for letting a coding agent wire up behavior without guessing at element names.
The README publishes an entrance duration per screen, from 1.467 s for onX Hunt to 8.867 s for MyFitnessPal. That range is the most interesting number in the table, because it shows the studies are not variations on one template. Perplexity is listed as "Final state" with no entrance at all, and the README is explicit about why: the research set contained only a final-state reference, so the implementation avoids inventing unsupported motion. That is a defensible choice and worth copying as a habit.
A docs/MOTION_SPEC.md file is referenced as the source of the timing details, and docs/ASSET_PROVENANCE.md records where generated assets came from. Neither file's contents are reproduced in the README, so treat the table as the summary and the spec as the detail you read before porting anything.
Running the Expo gallery locally
The repository is an Expo Router app, with "main": "expo-router/entry" and a Node engine requirement of >=22.13.0 in package.json. The README's own navigation points to a "Run the Expo gallery" section, which is the path to follow for a first run. The package is also published under the name welcome-screen-gallery with a react-native entry of ./src/index.ts, so the components can be consumed as a dependency rather than copied.
Start by installing dependencies with the lockfile, then launch the dev server. The commands below are the standard Expo workflow the project's scripts imply; check package.json for the exact script names in your checkout before running them.
npm ci
npx expo startThe dev server prints a QR code and a short list of key bindings. Press i to open the iOS simulator, or scan the code with a device on the same network. You should land on the gallery index listing all ten screens rather than on any single welcome screen.
To open one study directly, navigate to its route in the running app. The screen IDs in the table are the identifiers used by the gallery, so the Duolingo study is the one to open first if you want the shortest read: at 2.667 s it has enough motion to be instructive without a long wait.
If you would rather not clone anything, the README's copy-paste prompts are the other entry point. Each prompt is a block of text meant to be pasted into Codex, Claude Code, Cursor or another coding agent while that agent is working inside your existing Expo app. The prompt names the component, the screen ID, the required fonts (for example Nunito_400Regular and Nunito_900Black for Duolingo), the semantic action IDs, and the reference files to read. It also instructs the agent not to convert your app into the gallery.
The brand problem is the main limitation, and it is deliberate
The README opens with an important notice: this is an independent, unofficial Appllama project, not affiliated with or endorsed by any referenced company, and the screens should not be shipped unchanged. Before any public or commercial use, the notice says to replace every third-party name, logo, mascot, image, phrase, color system and other brand element, then make the final layout and motion meaningfully unique.
That is not boilerplate hedging. The value of each screen comes from the fact that it resembles a recognizable app, and that resemblance is exactly what you cannot ship. The showcase images are described as simulator captures of this implementation, with original reference clips and stills not redistributed, which keeps the repository cleaner but also means you are studying a reconstruction rather than the original.
There is a second constraint: the code is GPL-3.0-only. Whether that is compatible with your app depends on how you distribute it and how the copied file interacts with the rest of your codebase. The README does not discuss linking, relicensing or what a copy-pasted component does to your project's licence, and it does not offer legal advice. If your product is closed source, that question needs an answer from someone qualified before you paste a component in.
A third, smaller issue: the README does not document rollback. There is no stated way to revert a prompt-driven integration if an agent edits more of your app than you intended, beyond your own version control.
How it differs from a general React Native UI kit
The obvious alternative is a broad component library such as React Native Paper or the various Tailwind-style UI kits for Expo. The difference is scope, and it cuts both ways. A general kit gives you buttons, lists, dialogs and theming that you will need across an entire app, and it is designed to be adopted wholesale. It will not show you how to sequence a 6.6-second entrance animation, because that is not its job.
top-welcome-screens does the opposite. It covers ten screens and nothing else. There is no theme provider, no navigation shell, no form components. What it offers instead is the thing most UI kits omit: an explicit motion timeline per screen, a documented entrance duration, reduced-motion handling, and a deterministic final-state mode so the screen can be rendered without animating. The semantic action IDs are a smaller but real advantage when you want a test or an agent to trigger "get started" without scraping the tree.
A second alternative is to rebuild the animation from a screen recording by eye. That works, and it costs a day per screen. The value here is the recorded timing and the file structure, not the visual result, which you have to replace anyway.
Maintenance status and what an upgrade costs
The repository is not archived, and the last push was on 2026-08-08. The README advertises Expo SDK 57, React Native 0.86 and strict TypeScript, and package.json pins a Node engine of >=22.13.0. The repository has no published GitHub releases, so there is no tagged version history to reason about; treat the main branch as the only version.
That combination sets the upgrade cost. Expo SDK upgrades are typically the forcing function: when you move to a newer SDK, Reanimated and React Native versions move with it, and any file you copied has to be re-checked against the new APIs. Because each screen is a self-contained component with shared helpers under src/welcome-screens/shared/, the blast radius of an upgrade is limited to the files you actually brought over, provided you did not modify the shared helpers in place.
The licence adds a different kind of cost. GPL-3.0-only is a copyleft licence, and the package metadata declares it plainly. If you copy a component into a proprietary app, the question of what that does to your distribution obligations is a legal one, and the repository does not answer it. NOTICE.md exists precisely to track third-party attribution, which suggests the maintainers expect the attribution question to be taken seriously rather than waved away.
Editorial conclusion
Adopt it if you are building an Expo app and want to study how a specific entrance animation is structured before writing your own, or if you want a coding agent to port one component into an existing repository. Do not adopt it if you need branded, release-ready screens, or if your app cannot carry GPL-3.0 code. Before anything else, read NOTICE.md and docs/ASSET_PROVENANCE.md, then confirm that the Duolingo, Strava, MyFitnessPal, Perplexity, Yazio, onX Hunt, Speak, Hallow and SCRL names, logos, mascots and color systems are replaced in whatever you keep.
Frequently asked questions
What are some good onboarding screens for apps?
The repository collects ten welcome and onboarding screen studies inspired by Duolingo, Strava, MyFitnessPal, Perplexity, Yazio, onX Hunt, Speak & Learn, Hallow, SCRL and Speak: Language Learning, each implemented as a TypeScript component with an authored animation timeline.
What is a welcome screen?
In this project a welcome screen is the first full-height screen a user sees, built with React Native Reanimated and an entrance timeline that runs anywhere from 1.467 s to 8.867 s depending on the study. The README groups splash, loading, welcome and onboarding screens under the same collection.
Can I use these welcome screens in a commercial app?
The README states this is an educational reference only and that you should not ship the screens unchanged. Before any public or commercial use it says to replace every third-party name, logo, mascot, image, phrase and color system, then make the layout and motion meaningfully unique. The code is licensed GPL-3.0-only.
How do I install top-welcome-screens in an existing Expo app?
You can either run the gallery as an Expo Router app, or copy one named component from src/welcome-screens/ into your project along with only the transitive imports it uses. The README also provides a per-screen prompt to paste into a coding agent working inside your repository.
Which animation library do the top-welcome-screens examples use?
The README states the components are powered by React Native Reanimated, with timings documented in docs/MOTION_SPEC.md and asset origins in docs/ASSET_PROVENANCE.md.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/appllama-top-welcome-screens)Star history chart for your README
[](https://hysenlabs.com/projects/appllama-top-welcome-screens)Was this useful?