What’s Next?
As I mentioned at the end of Chapter 5, Render Native Screens with SwiftUI, you can use this approach to build any native screen or interaction you want. You could swap out the map and render data from the Health Platform API. Or convert the list of hikes to native elements and cache it for offline access. The list goes on.
But because of how expensive native screens are to build, each native feature should only be reserved for the most critical pieces of your app.
The good news is that there is a middle ground. When you want a little extra fidelity, you can upgrade individual components to native without committing to an entire SwiftUI or Jetpack Compose screen. The next chapter covers how to integrate bridge components to add ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access