Every Dekimu web app now installs from the browser. Each one serves a manifest and icons, runs standalone once added to a home screen, respects the safe areas around a phone's notch, keeps inputs at 16px so iOS stops zooming into them, and gives touch devices 44px targets. The behaviour lives in shared packages, and a phone-and-tablet check in CI keeps it there.
Every app has a manifest with its own start URL, scope and id, an icon route, Apple web-app meta tags, and a viewport that reaches into the notch. Layouts use dynamic viewport units, wide tables scroll sideways instead of spilling off the screen, and modals become bottom sheets on narrow screens.
Before this pass, none of the apps could be installed, and dashboard inputs zoomed on iOS because the shared shell set form controls below 16px. The checkout screen at id.dekimu.com had no responsive layout at all. After the rollout, every manifest was checked live and came back with the right content type.
The shared shell, the landing shell and the design tokens carry the rules. An app adopts them by updating those packages and adding three small pieces: a viewport export, a manifest route and icon routes. The starter template for new apps carries the same pieces, so the next app is installable on its first day.
Touch rules apply only under the coarse-pointer media query. On a desktop with a mouse, the dense editorial layout looks exactly as it did.
A native app would have wrapped the same broken pages. The fix belongs in the web layer, once.
Every surface is signed in and shows live data. An offline shell would add stale caches and logout bugs for no present gain, so there is deliberately no service worker. Offline behaviour gets decided when there is a real requirement for it, not before.
Sign-in works the way it did: same-origin httpOnly cookies and plain HTTPS redirects, nothing that depends on a cached copy of a page.
A phone-and-tablet pass now runs in CI against real page renders. It checks for sideways overflow, input size, touch-target size, the viewport meta tag and the manifest.
Its first run passed inputs, viewport and manifest everywhere, and failed the 44px target rule on most pages, along with a few overflows. Follow-up releases fixed the targets in each app and in the shared shell. That is what the check is for: it found what the first pass missed, and it will find the next regression the same way.
This post was drafted by an AI system from Dekimu's public engineering record and published with automated checks, without per-post human editing.
← Back to blog