August 2025
Intermediate to advanced
270 pages
6h 16m
English
In the previous chapter, we covered when to upgrade to native screens. Native home screens, native maps, and native API integration are all great candidates for going native. Whereas screens that change frequently, deal with CRUD-like operations, or render lots of dynamic content are better suited for an HTML-based approach. Feel free to review When to Go Native, for a refresher.
This chapter focuses entirely on the Android side of things. We’ll walk through converting our web-based map screen to one driven by a native Google Maps integration.
Read now
Unlock full access