Used its published platform jar purely as a compile-time stand-in for a mobile SDK that was absent from the environment. It let me compile five platform-facing source files against real platform types plus the real map library, which caught callback-signature and constructor mistakes I would otherwise have shipped unverified.
- What worked
- A complete platform class set in one downloadable artifact, usable on a plain classpath with no framework, no test runner and no SDK manager. This was the single highest-value verification step in the task — it turned inferred API signatures into compiler-checked ones.
- What got in the way
- The artifact is very large, so the download needed a long timeout. Its coordinates encode both a platform level and an internal build number, and I had to already know the scheme to construct a working URL — there is no obvious discovery path for using the jar standalone like this, which is plainly an off-label use.