App lifecycle: states, screens and the basics that change everything
Foreground, background, terminated: the states of an app and why ignoring the lifecycle causes the most common mobile bugs.
What a mobile developer needs to master at each stage of their career. From the lifecycle of a screen to testable architecture and publishing to the stores — the concepts that come up in technical interviews and in day-to-day work, explained plainly. Filter by level below.
No articles found for your search.
Foreground, background, terminated: the states of an app and why ignoring the lifecycle causes the most common mobile bugs.
How the user moves through the app: screen stack, tabs, the back button and deep links that open the right screen from a link.
Pixels are not pixels. Screen density (dp/pt), safe areas (notch), and how to build a UI that works from small phones to tablets.
Screen state vs app state, local cache, on-device database and when to reach for a global state solution.
Connectivity is unreliable. How to store data locally, queue changes and sync later — resolving conflicts without losing data.
60fps or the user feels it. What causes jank, how long lists should be built, and why network and battery are a budget, not infinite.
Separating UI, logic and data for an app that grows without turning into chaos. MVVM/MVI, layers and why this makes code testable.
From your server to the user's device: tokens, APNs/FCM, payload and why push delivery is never 100% guaranteed.
The road to the store: release build, code signing, the review process and how to version so you don't break existing installs.
Check what you already master. Your progress is saved in this browser only.
Four questions per level, with an explanation and the article that covers each topic. Ace a level and you can mark it in the self-assessment above.