Four decisions before sharing code across web and apps
One feature can serve five platforms when the screen roles, source of truth, platform boundaries and release units are clear.
Sample article for design review. Content will be reviewed before publication.
01
Organize screens by role, not device size
Start with the job of each screen: list, detail or form. Reflow a shared implementation for each device instead of maintaining separate feature logic.
02
Keep the source of truth on the server
Orders, payments and permissions belong on the server. Cache local preferences where appropriate, and design offline records deliberately.
03
Isolate platform differences
Payment, notifications and file picking use platform adapters behind one interface. New platforms add adapters without changing screens.
04
Release separately, build together
App store reviews and web deployment have different schedules. Build previews from the same commit so each platform demonstrates the same feature.
Other articles
View all articles
You can read about how we work and our benefits on the careers page.
See careers