Skip to content
academia.sh
tr
Log in

Course Advanced

Cross-Platform Production Practice

Published Updated

By the end of this course

Start course

01

Shared Architecture

Shared and platform-specific layers, adapting one design language to the expectations of two platforms, multiple environments and secret values, accessibility on both platforms.

  1. 01 Modular Code Sharing Modular code sharing splits common code into a shared module and a platform-specific layer. The lesson builds the course's operability measure and measures how a fully shared module can still be disabled on one platform.
  2. 02 Design System Adaptation Design system adaptation tunes one design language to the expectations of two platforms. The lesson measures that an adapted component works fully on both platforms and that another component stays degraded under a version condition.
  3. 03 Configuration and Environment Management Configuration and environment management lets the same app run with different values in development, staging, and production. The lesson measures that a flag opened from its default leaves the feature full.
  4. 04 Accessibility Accessibility lets an app do its job under different ways of use such as a screen reader, large text, and touch. The lesson measures that a gesture drops to a menu and works in a degraded way when a screen reader is turned on.

02

Offline and Synchronization

Design that makes local data the source of truth, the change queue and conflict resolution, the platform's background processing limits, user experience on an intermittent network.

  1. 01 Offline-First Design Offline-first design makes local data the source of truth and uses the network only for refreshing. The lesson builds the same flow with two designs and measures how well each one works when there is no network.
  2. 02 Synchronization Strategies Synchronization strategies queue a change made offline, send it to the server when the network returns, and resolve conflicts. The lesson measures that offline note editing stays deferred and shuts down when storage is full.
  3. 03 Background Processing Limits Background processing limits describe the rules the operating system sets for running work while the app is not visible. The lesson measures that media backup is deferred and live location is disabled when background capability is restricted.
  4. 04 Connectivity State Management Connectivity state management covers monitoring the connection, adapting to a weak connection, retrying, and showing the state to the user. The lesson measures that an image gallery is degraded and messaging stays deferred on a weak connection.

03

Release and Operations

Signing, build and upload automation, version numbering, staged rollout and the limits of rollback on mobile, forced updates, app size, unified monitoring from both platforms.

  1. 01 Mobile Continuous Delivery Mobile continuous delivery turns a code change into a signed build and passes it through a test distribution channel and store review. This lesson measures how well a feature works when the same signed build ships to production with a closed flag.
  2. 02 Version Management Version management governs which build of an application ships under which number and how the client talks to the server. This lesson measures how well a feature works when it asks for a new contract from a server that offers only the old one.
  3. 03 Staged Rollout and Rollback A staged rollout opens a new version to only a portion of the users; if a problem appears, the rollout is halted or the feature is turned off. This lesson measures how well a feature works in each bucket the rollout has reached.
  4. 04 Forced Update Strategy A forced update strategy decides when, with which prompt, and for which reason old clients that the server no longer supports are directed to the new version. This lesson measures how well the payment feature works on a client below the minimum version.
  5. 05 App Size Management App size management decides what the first download contains and which parts are fetched later on demand. This lesson measures how well a feature that depends on an asset pack not delivered in the first download works.
  6. 06 Crash and Usage Monitoring Crash and usage monitoring describes how to collect, from both platforms in a unified form, what a released build does in the field. This lesson measures that a crash report created in an offline session stays deferred and that user consent turns usage events off.

Final exam

Cross-Platform Production Practice — Final Exam

In preparation

This course's question bank is not complete yet. The exam opens here automatically once enough questions are added.

Start typing to search.

↑↓ ↵ Esc navigate · open · close