Manaurum Platform v2
Mobile support
Declare support honestly and implement the layout that matches it. A manifest badge does not make desktop UI responsive.
Contracts reviewed: · SDK version: 2.6.1
Declare platforms
The optional platforms block declares desktop/mobile support, optimization, entrypoint, supportLevel and navigationPattern. full means dedicated UI, adaptive means responsive UI, fallback means desktop UI with a banner, and none blocks mobile launch. Navigation patterns include stack, tabs, list-detail, single-view and composer-first. Omitted support keeps the app desktop-first. Optimized and supported declarations determine Store badges.
{
"platforms": {
"desktop": {
"supported": true
},
"mobile": {
"supported": true,
"optimized": false,
"supportLevel": "adaptive",
"navigationPattern": "stack"
}
}
}Read device context
Read ctx.device and ctx.platform from onReady or app.device/app.platform/app.isMobile, then subscribe to onDeviceChange. Use ctx.screen, safeAreaInsets, navigationMode and shell.tabBarHeight where present. Before readiness, device and platform default to desktop; isMobile is false. Do not assume hardcoded notch or tab-bar dimensions and do not infer the shell device from the user agent.
Test the real reading flow
Use the SDK test harness and its Device/Notch controls. Check widths 320, 360, 390, 430 and 768 px, portrait/landscape, zoom and dynamic browser toolbars. Verify that touch scrolling reaches the end and that code/table overflow stays local. Test iOS Safari and Android Chrome; desktop viewport emulation is useful but does not replace them.