A native iOS and Android mapping toolkit for interactive 2D maps and 3D globes with shared rendering code.
WhirlyGlobe-Maply is a native mapping toolkit for iOS and Android that provides both interactive 3D globe and 2D map components. It solves the problem of building high-performance, interactive mapping applications with a unified codebase that supports both mapping paradigms. The toolkit is used in numerous production applications ranging from simple utilities to complex enterprise solutions.
Mobile developers building mapping applications on iOS and Android who need native performance and flexibility for both 2D and 3D geographic visualization.
Developers choose WhirlyGlobe-Maply because it offers a proven, production-ready solution with shared rendering logic between 2D and 3D modes, reducing code duplication while providing specialized interfaces for each use case. Its extensive track record in published apps provides confidence in stability and capability.
WhirlyGlobe Development
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Separate view controllers for interactive 3D globe and 2D map with 95% shared rendering code, enabling easy switching between mapping paradigms as described in the Philosophy section.
Native implementations for both iOS and Android with consistent APIs, highlighted by platform badges in the README, ensuring a unified development experience.
Used in many published apps, as listed on the project site, indicating reliability and optimized rendering for complex geographic data.
Offers precompiled binaries to simplify setup, reducing initial build complexity compared to compiling from source with submodules.
The README explicitly states the project is not actively maintained, which risks unresolved issues, lack of new features, and potential long-term obsolescence.
Requires syncing large submodules and building dependencies, making initial setup more involved and time-consuming than simpler mapping libraries.
Upgrades, such as from version 3.3, necessitate manual adjustments like import changes and modular headers, increasing maintenance overhead and potential migration issues.