Connectivity resilience
Design workflows that do not require a round-trip for every calculation, subject to the licensed runtime's coverage.
If your application needs calculations on the device, evaluate a native engine licence separately from hosted API access. Platform binaries, size, coverage and redistribution rights must be confirmed in a written technical and commercial scope.
A local runtime can be relevant to unreliable networks, privacy-sensitive products and predictable on-device behavior. Suitability depends on the exact platform and feature set tested—not a general promise that every API endpoint runs offline.
Design workflows that do not require a round-trip for every calculation, subject to the licensed runtime's coverage.
Evaluate whether sensitive birth inputs can remain on the user's device in your intended architecture.
Define your own interface, cache and release process around the calculation component.
The source documentation verifies a Formula-Lite provider built on VSOP87 series arithmetic. It does not, by itself, prove that a packaged public SDK is ready for every mobile platform. A meaningful evaluation should include evidence for your target environment.
No. On-device distribution and hosted API use have different technical and commercial implications, so they need separate scoping.
Ask for a platform-specific evaluation. Do not rely on a claimed size or compatibility until the exact build is tested on your targets.
That depends on the licensed calculation coverage and your own product architecture. The enquiry should specify which operations must be offline.
Send platform, required calculations, offline constraints and distribution model.