Overview
A one-page launch site for a mobile app, built with Next.js.
Each feature is one big sentence. A clear glass phone settles on it, the words frost over and turn into your real screenshot, then the phone lifts to show it up close. You change one file — app name, store links, feature sentences, screenshots, prices, reviews and questions — and the page, the 3D phone, the phone layout and the reduced-motion layout all follow.
What you get
- The Next.js page with the glass phone story, feature tiles, ratings and reviews, pricing, questions and the download block.
- A static HTML version in the
html/folder for any web host. - Store details done right: official App Store and Google Play badges shown the way Apple and Google ask, a QR code that sends each visitor to the right store, and a pre-launch mode with a waitlist.
- The pages the stores ask for: privacy, terms, support and account deletion, filled from the same file.
- A screens checker (
npm run screens) that tells you exactly what to fix before you publish. - A step-by-step guide in
Documentation/index.htmlinside the download (it works offline).
What it needs
- Node.js 22.18 or newer (22 or 24 LTS recommended).
- Any host that runs Next.js (Vercel, Netlify, your own Node server), or any static host for the HTML version.
Quick start
npm ci # installs the exact versions in package-lock.json
npm run dev # http://localhost:3000Then follow Getting started.
Getting started
Six steps, about 15 minutes the first time: unzip, install, run, make it yours, build, go live.
Before you start
- Node.js 22 or 24 (LTS). 22.18 or newer works. Check with
node -v. Not installed? Get the LTS installer from nodejs.org. - A terminal (macOS Terminal, Windows PowerShell or Windows Terminal, any Linux terminal).
- A code editor. Any will do; VS Code is free and has a terminal inside (View → Terminal).
1. Unzip
Unzip the download into a folder where you keep projects, for example Documents/sites/under-glass. Avoid a synced folder (iCloud Drive, OneDrive, Dropbox): syncing node_modules makes everything slow. Open the folder in your editor and open a terminal in it.
2. Install
npm ciThis installs the exact library versions we tested. You should see "added … packages" and no red ERR! lines. Yellow npm warn lines about deprecated sub-packages are normal.
3. Run it on your computer
npm run devOpen http://localhost:3000. The first load takes a few seconds while it compiles. Leave the terminal open while you work; every save shows up in the browser by itself. Ctrl + C stops it.
4. Make it yours
Everything you change is in src/content/app.config.ts. Replace the sample app (Neap) with yours and save — see Your app's content.
5. Build and check the real thing
Stop the dev server, then:
npm run build
npm startYou should see "Compiled successfully", then "Ready". Open http://localhost:3000 again — this is exactly what your visitors will get, so click through it once before going live.
6. Go live
- Vercel (easiest): put the folder in a private GitHub repository, import it on vercel.com/new, keep the defaults and press Deploy. Add your own domain under Project → Settings → Domains. Every push redeploys the site.
- Your own server: on the server (Node.js 22.18+) run
npm ci,npm run buildandnpm start -- -p 3000. Keep it running with a process manager (for examplepm2 start npm --name under-glass -- start) and put Caddy or Nginx in front for your domain and HTTPS. - Static host: upload the
html/folder (see below).
Your licence does not allow public repositories of the source, so keep the GitHub repository private.
The static HTML version
A ready-built copy of the demo is already in the html/ folder. npm run html rebuilds it from your app.config.ts (it runs a production build first, so it takes a minute). Upload the html/ folder to any host — Netlify Drop, GitHub Pages, S3, cPanel. To change only the words, edit the .html files; screens, focus boxes and phone poses are in the <script id="ug-data"> block near the end of index.html. It must be served over http(s) (browsers block 3D textures opened straight from disk); try it from the project folder with npx serve html.
Sections and pages
The launch page, top to bottom
- First screen — your headline sentence and the line under it, the store badges, a QR code on computers and the rating line. The glass phone rests clear on the headline, then turns into your app.
- The scroll tour — one chapter per feature. The glass lies on the sentence, the words frost and pour into it, the screen blooms from the part of the app the sentence is about, and the phone lifts to show it.
tour.maxsets how many features get a full chapter (the first screen counts as one); the rest become tiles. - Feature tiles — the remaining features as smaller cards; tap or press Enter on a tile to play its glass.
- Ratings and reviews — your store rating and reviews, with the glass as a loupe. Leave
sample: trueuntil they are real, and the page labels them as samples. - Pricing — your plans with a monthly / yearly switch and free-trial days; the page works out the weekly price and the saving.
- Questions — your FAQ.
- Download — the closing sentence; on computers the phone shows a QR code, on phones one tap opens the visitor's own store.
- Footer — your app's name and line, links to the legal pages, your support email and the store trademark lines.
The other pages
/privacy,/terms,/supportand/delete-accountare filled from the same file (company, contact, what data you collect). Apple asks for a privacy and support address, Google asks for an account-deletion page, and subscriptions need terms. They are templates, not legal advice — have them checked for your company and country. Turn any page off inlegal./get— one link for every phone: it sends iPhones to the App Store and Android phones to Google Play. The QR code points here.- A 404 page in the same style.
The glass phone
- The phone is our own design, drawn in code — it is nobody's real phone, so it is safe to publish. There are no 3D files to manage.
- Desktop and tablet (wider than 768 px) show the 3D glass. Phones get a lighter glass made with CSS — just as clear, kinder to batteries. Visitors who turn on "reduce motion" see every screen in place, without movement.
- The glass needs a graphics card. On computers that would draw it slowly (under about 30 frames a second) the page first draws it at a lower resolution, then switches to the still layout — just as finished, nothing moves.
- Pick the finish in
brand.finish:sea-glass,smoke,roseorclear, with asatinorgraphiteband.
Sound
A small set of glass sounds made in code (no audio files). Sound starts from the visitor's first tap or key press, and the Sound on · M switch in the top bar remembers their choice. Turn it off for good with sound: { kit: null, ambient: null }.
Your app's content (one file)
Everything you change is in src/content/app.config.ts. Open it, replace the sample app (Neap) with yours, save — the page updates as you type.
| Part | What to set |
|---|---|
app | name, icon (a 512 × 512 PNG in public/app/), one-line description, company, support email, website |
status | "live" shows the download badges; "pre-launch" shows a waitlist |
store | your App Store id (the number in your App Store link), your Google Play package name, the address of your /get page |
brand | two accent colours and the glass phone's finish (sea-glass, smoke, rose or clear; band satin or graphite) |
hero | the first sentence and the line under it; screen picks which feature's screenshot the first screen shows |
features | one entry per feature: tab label, icon, the sentence, one plain line, the screenshot, light or dark, the focus box |
tour.max | how many features get a full chapter on the scroll tour; the rest become tiles |
rating, reviews | copy them from your store listing; leave sample: true until they are real |
pricing | your plans, monthly and yearly prices, free-trial days |
faq, download, legal, sound, seo | questions, the closing sentence, which legal pages to show, sound on/off, search title and description |
Sentences: wrap ONE phrase in *asterisks* to set it in italic accent colour, for example "Know the sea before you're *in it.*". Short sentences (under about 48 characters) read best at this size.
Your screenshots
- Use raw screenshots straight from the phone or the Simulator — no device frame, no caption. The page draws the phone.
- Best size: 1290 × 2796 (iPhone) or 1080 × 2400 (Android). Save them in
public/screens/and pointscreenat them. - Screen recordings work too: a portrait
.mp4(6–10 seconds, no sound) with aposterstill. Your App Store preview video is perfect. - Dark screens: set
theme: "dark"and the glass frosts to smoke instead of milk. - Focus box: each feature's
focusmarks the part of the screen the sentence is about (in %, from the top-left); the screen blooms from there. Runnpm run dev, open http://localhost:3000/screens, drag a box on each screenshot and press Copy the line. - Run
npm run screensbefore you publish. It checks every file, size, focus box, the store ids and prices, and tells you exactly what to fix.
Store badges and the QR code
- The badges are Apple's and Google's official artwork (in
public/badges/, untouched), shown the way both guidelines ask: black, App Store first, the same visible height, clear space around them, never animated or tilted. For another language, or the Pre-order / Pre-register versions, download them from Apple Marketing Tools and the Google Play badge page and pointstore.badges.appStore/store.badges.googlePlayat the new files. - One link for every phone: set
store.smartLinktohttps://your-domain.com/get. The QR code and the/getpage send iPhones to the App Store and Android phones to Google Play. - While the sample store ids are in the file, tapping a badge shows a short demo note instead of opening a store page that does not exist. Put in your real ids and the badges link straight to your listings.
- On iPhone Safari the page also shows Apple's own app banner once your App Store id is real.
Pre-launch mode
Set status: "pre-launch" to show a waitlist instead of the download badges, and connect it to any form service by setting store.waitlistAction (for example a Formspree or Basin form address). When the app is live, switch status back to "live".
Images
Keep the same file name and roughly the same shape as the image you replace, and use .webp or .jpg under about 400 KB for photos. Then nothing else needs to change.
Troubleshooting
"node" or "npm" is not recognised / command not found
Node.js isn't installed, or the terminal was opened before you installed it. Install the LTS version from nodejs.org, close and reopen the terminal, and check node -v.
npm ci fails with EBADENGINE, or the build shows a syntax error in node_modules
Your Node.js is too old. Install Node.js 22 or 24 LTS (22.18 is the minimum), delete node_modules, and run npm ci again.
npm ci says package.json and package-lock.json are out of sync
You (or your editor) changed package.json. Run npm install once instead; it updates the lockfile.
Port 3000 is already in use
Another app is using it. Run on another port: npm run dev -- -p 3001 and open localhost:3001.
The build fails with odd React or "non-standard NODE_ENV" errors
Your terminal sets NODE_ENV to something other than production. Clear it for the build: on macOS / Linux env -u NODE_ENV npm run build; in PowerShell Remove-Item Env:NODE_ENV; npm run build.
I replaced an image but still see the old one
Hard-refresh the browser (Ctrl/Cmd + Shift + R). If the file name changed, update the reference to it too.
The 3D phone is blank or slow
3D needs WebGL. Turn on hardware acceleration in your browser settings and update graphics drivers. Visitors without WebGL, on slow computers or with reduced motion on automatically get the still layout.
The static HTML version shows no 3D when I open index.html from my disk
Browsers block 3D textures opened straight from disk. Serve it over http(s), for example npx serve html.
Windows: errors about long paths or permissions
Keep the project near the drive root (for example C:\sites\under-glass), outside OneDrive, and run the terminal as your normal user. If an antivirus slows npm ci, exclude the project folder.
Everything is slow in npm run dev
Normal for the very first load of each page (it compiles on demand). The production build is the real speed.
Speed and accessibility
- The first screen is plain HTML and text. The 3D loads after it, only on screens that can show it, and pauses when it is off screen.
- Every sentence is real text for search engines and screen readers; the 3D layer is hidden from assistive tech.
- The feature tabs and tiles work with the keyboard.
- All text meets WCAG AA contrast.
- Visitors who turn on "reduce motion" see every screen in place, without movement.
Browser support
Current Chrome, Edge, Safari and Firefox on desktop, iOS and Android.
Licence and support
- Licence — one licence: use Under Glass for as many websites as you like, yours or your clients', personal or commercial, and in products you sell to many users. Change anything you like, but never resell, share or give away the files (or a modified copy) as a template, theme or kit. Summary in
LICENSE.txtin the download. - Updates — your Pulse account always has the latest version and your licence key.
- Support — write to us from the Pulse support page with your order email, what you ran and the last 20 lines from the terminal. A person replies within 6–24 hours (weekends can be slower).
Credits
Fonts: Fraunces, Geist and Geist Mono (SIL Open Font License). Animation: GSAP (GSAP Standard "No Charge" License). 3D: three.js (MIT). Next.js, React, Lenis, Sonner, Vaul and uqr (MIT). Demo photos and app screens were made for this theme — replace them with your own. Apple, the Apple logo and App Store are trademarks of Apple Inc.; Google Play is a trademark of Google LLC.