Plan Mate
Write down one appointment and the rest follows: the weather at that hour and that place, what to wear, when to leave, roughly what it costs. It is less a calendar than the sheet of things that appointment needs from you today. Every number carries its reasoning, because a number you cannot justify is indistinguishable from a random one.
Try it here
Press the button and it runs inside this page. Nothing is downloaded until you do, so reading and leaving costs you nothing. No install, no sign-in.
Who it is for
People who do write appointments down, but still look up the umbrella, the jacket and the departure time separately every single morning
What it does
- Weather for the hours of the appointment, not a daily average: temperature, feels-like, chance and amount of rain, wind, humidity, UV and air quality
- Clothing and precautions come from rules, and each line shows why. 'Hot. Breathable clothes, water' sits next to 'feels like 31°C at its worst'
- Departure time comes first. It is the appointment time minus travel, which is the number you actually open the app for
- Distance comes from the public OSRM server: real road distance, no key needed, cached for 30 days. When it fails the app falls back to straight-line distance times a detour factor, and says so on screen
- The travel time OSRM returns alongside it is thrown away. It ignores congestion entirely — it called 8.3km across Seoul a nine-minute drive. Travel time is computed instead from per-distance average speeds with rush hour, late night, weekend and rain factors
- Transit and driving sit side by side. The driving cost counts fuel only, and the screen says tolls and parking are not in it
- Open 'where this number came from' and you get the speeds, distances and fare rules behind it
- What to eat and where to go are decided by time of day, weather and formality. Rain, dust or heat means indoor only; outdoor is suggested only while daylight lasts
- No restaurant list is fabricated. The only keyless source is OpenStreetMap, and it lists 21 restaurants within 500m of Gangnam Station where there are hundreds. Calling those 21 'nearby restaurants' would be a lie, so the rules stop at the search term and hand the actual places to a map app
- Monthly and yearly statistics: appointment count, real spending, spending by category, type and weekday distribution, frequent neighbourhoods, distance travelled
- Spending totals only what was actually entered. Filling the blanks with estimates would turn 'I spent 200,000 won this month' from a fact into a plan. The screen says how many of how many entries have real numbers
- Estimate and actual are compared over the same set of appointments. Putting a full estimate next to a partial actual always produces the illusion of being under budget
- Appointments live in the phone's own storage. Moving them to another device means exporting one file and sending it wherever you like
- Importing merges rather than overwrites: the more recently edited version of an appointment wins, and a deletion travels as a tombstone
- Runs in the browser with no install. Add it to the home screen and it opens offline
- The manual lives inside the app, and the build fails if the app changes without it. Left to willpower, a manual always falls behind
- One web codebase wrapped with Capacitor for Android — not two separate front ends
- Place search falls through three tiers: your own Kakao key, then my proxy, then OpenStreetMap. The screen says which one answered
- With an ODsay key, transit stops being an estimate and becomes a real lookup — the chip flips from 'estimated' to 'looked up' so you always know which you are reading
- Keys never ride along in the backup file. That file is meant to be sent over a messenger, so a separate check refuses an export that contains one
- Ads exist in the Android app only. The web version has none
- The interstitial appears only when you open statistics, twice a day at most, four hours apart. Never on launch, never when you save an appointment
- Banner height is taken from what the device reports rather than guessed, and the layout steps aside by exactly that much
Where it is going
The web build has been public for a while, and the Android app was released on Google Play on 3 October 2026 — anyone can install it from the store, no tester registration. The rules are all pure functions with tests around them, but the thing that matters most is still unverified: the travel estimates have never been checked against a real map app. All that is pinned down is that known routes land in a non-absurd range. Using it for real and comparing against Kakao Map is what will fix the speed factors, and once API keys arrive the estimate becomes an actual route lookup. Server sync is written and then deliberately hidden: the store has no per-user separation, so a single PIN would expose every appointment in it. Publishing that would mean holding other people's personal data in my account, so file export is the supported way until proper multi-user separation exists.
Written while building it
Status
On the web · on Google Play
Google Play 프로덕션에 출시된 앱입니다. 2026년 10월 3일 기준 스토어 상세 페이지가 모두에게 열려 있고, 테스터 등록 없이 설치할 수 있습니다.
- StartedSeptember 2026
Before you start
- Released on Google Play on 3 October 2026. Anyone can install it from the store
- Travel times and costs are estimates. They have not been validated against a real map app
- Appointments are stored on your device only. Private windows and clearing site data lose them
- To move to another device, export a file in settings and import it on the other one
- Weather is Open-Meteo, place search is Nominatim, road distance is public OSRM. All keyless, which is also why Korean shop data is thin
- The app carries ads: a banner, plus an interstitial when you open statistics, twice a day at most. The browser version has none
Links
Tried it?
Tell me what worked, what did not, or what broke. Feedback is read before it is published. The feedback page is in Korean.