Unit 02 of 02
Platform Realities
The differences between platform design languages, the need for native modules, performance expectations, and store and release constraints.
Published Updated
Lessons
- 01 Platform Design Language Differences The two platforms do the same job with different design languages. The lesson classifies a single function that picks the navigation pattern from the screen type, and gives different results on each platform, as branched, then measures how an adapted design raises sharing. 11 min read
- 02 The Need for Native Modules Shared code cannot reach every platform capability. The lesson classifies a biometric authentication request, written separately on each platform as a native module, as split, and measures that a capability present on only one platform comes out single. 11 min read
- 03 Performance Expectations Taking a frequently running path out of shared code and writing it natively is done for performance. The lesson classifies thumbnail decoding, written separately on each platform, as split, and counts bridge crossings as a unit of work. 10 min read
- 04 Store and Release Constraints App store rules, store review, and the in-app update also shape how code is shared. The lesson classifies an update flow written on only one platform as single, and measures that code switched off by a flag still counts as branched. 12 min read