Ship apps people keep on their phones: native Android or iOS, or one codebase for both, with design, data and release done properly.
Finish this and you can design, build and publish a mobile app with offline data, a backend and the platform's own design conventions.
Native Android, native iOS, or cross-platform: pick one to start and go deep before going wide.
Build this
Small, useful, finishable.
Done when: The source, screenshots, and the list of fixes you made after a week of use.
SwiftUI architecture, data flow and the platform frameworks, from Stanford's long-running course.
For web developers: reuse JavaScript and React skills on both platforms.
The platform conventions users expect, so your app feels native rather than ported.
Build this
Use your habit tracker with the screen reader on and the largest text size.
Done when: The fixes and the screen-reader video.
Sign-in, sync and notifications, then the release process and store listing.
Build this
Turn the habit tracker into a published app.
Done when: A test-track link and the store listing.
Not sure this is your direction?
A three-minute counselling sample is free.