Building a Public Website Without Breaking an Existing App LinkBuilding a Public Website Without Breaking an Existing App Link
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Otto's link used to open straight onto a sign-in card. Anyone who followed it learned nothing about what Otto does.
Now a signed-out browser tab gets a 3-page website (Home, Product, Pricing & access), and sign-in moved to /signin.
The trade-off: a second HTML entry would have broken shared report links, the voice pairing QR, the installed phone app and the desktop app. So the website and the app share one index.html, and the code decides which to show before React mounts.
Measured on the production build: → entry chunk: 897 KB → 155 KB → a website visit loads 123 KB of gzipped JS → the app's own JS: unchanged at 269 KB gzipped
The site is built from the app's own design system, and the three AI reviews lead, because they are what Otto does that a project tool does not.
Lesson: split the code before you split the URL.
What does your product's link show a stranger?
Post image
Back to feed
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started