Hangangjari
8 posts
Series
- The Hangang Parking Widget I Built After Buying a Car How I reduced the parking checks I repeated before leaving into an app home screen and widget.
- Why the Parking App Became a Hangang Visit App The product decisions behind adding events, congestion, facilities, and notices while separating car and general screens.
- An iOS Experience That Had to Continue Before Opening the App How widgets, notifications, deep links, and local cache kept the same park state connected.
- Why the App Did Not Call Public Data Directly How slow collection, prediction, and notification preparation moved into server workers so the screen could stay light.
- Turning a Home Server Into a Production Environment A record of adding deployment, observability, and backup routines to a home server and reaching an App Store launch.
- Why I Focused on the Han River Instead of Expanding Nationwide I chose a scope I could verify directly and explain responsibly over a broader park app.
- Numbers Alone Were Not Enough to Trust Public Data Why remaining spaces and congestion needed sources, updated times, and explicit unknown states beside them.
- The Widget Was Not a Smaller Version of the App How Hangangjari kept glanceable values and stale-state cues within iOS widget refresh constraints.