Career journal for

Mobile Engineers

Mobile platform work is bursty and release-cycle-driven. The 47 small craft decisions that made the v3.4 release polished are invisible by v3.5.

Bloomly is the career journal built for the moments the work actually happens, not the night before the review.

A captured day for a Mobile Engineer

1. 01

   9am: tuned the widget snapshot lifecycle; reduced cold-start memory 18%.

2. 02

   12pm: shipped the App Store build (v3.4.0); reviewer questions resolved in 4 hours.

3. 03

   3pm: code review with Marcus on his first SwiftData migration.

4. 04

   5pm: wrote the rollback runbook for the new feature flag.

What a Mobile Engineer captures

• App Store / Play Store releases owned
• Crash-rate and ANR improvements
• Native-platform features adopted (Widgets, Live Activities, Wear)
• Build and CI improvements
• Design-system contributions

Shipped Lock Screen widgets (23% week-1 adoption). Cut crash-free sessions 99.4% to 99.8%. Authored shared-snapshot pattern adopted by 4 teams.

Promotion rubric, mapped to capture

• Shipped releasesCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.
• Performance and stabilityCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.
• Native-platform craftCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.
• Cross-team partnershipCaptured automatically through dated entries, auto-tagged against this dimension, and surfaced in your generated Performance Report and Period Recap.