Runtime & Internals

Everything else on this site describes how to write a Maximo Mobile app. This section describes the machinery the app runs inside — the layer IBM does not document.

What actually runs on the device (the native Android shell, the container app, and NAVIGATOR, and the boot chain between them). How a save really reaches Maximo, online and offline. Why offline login is not a login at all but an encrypted-database open. How attachments get to a device and back. The fourteen private /graphite/mobile/* routes between client and server. And the three server-side mechanisms — preloaded database, data pregeneration and advanced delta — that decide whether a technician’s first sync takes four minutes or forty.

This material comes from pulling the shipped Android package apart, reading the unminified framework sources, decompiling Manage, and probing a live MAS 9.2 install. Overviews are free; the complete guides are 🔒 members-only. (Roadmap Level 11.)