Turn one app into everyone's app

A weather page with four hardcoded cities is really just one person's app wearing a website's clothes. The build log is about peeling that off: same code, but now anyone can spin up their own version with their own cities. The interesting part was figuring out where 'my config' ended and 'the app' began.

A weather page hardcoded to four family cities is one person's app wearing a website's clothes. The build log is about finding where 'my config' ends and 'the app' begins. https://www.jakelawrence.xyz/blog/spin-up-your-own-weather-board

A weather page hardcoded to four family cities is really just one person's app wearing a website's clothes. This build log is about peeling that back: same code, but now anyone can fork their own version with their own cities. The interesting work was figuring out where 'my config' ended and 'the app' began.

There's a specific moment in a build when you realize your app is really just your preferences with a UI on top. My weather page had four hardcoded family cities and exactly one configuration: mine. The build log is about fixing that. Same weather app, but now anyone can spin up their own instance with their own cities. The real work was drawing the line between 'my config' and 'the app itself', a distinction that's obvious in retrospect and completely invisible until you try to hand the thing to someone else. https://www.jakelawrence.xyz/blog/spin-up-your-own-weather-board

A weather page with four hardcoded cities isn't really a weather app. It's my weather app. The build log is about finding where 'my config' ends and 'the app' begins.

A weather page hardcoded to four family cities isn't a weather app. It's my weather app. The build log is about finding where 'my config' ends and 'the app' begins.