a chainsaw is a coarse tool and I liken it to vibe coding. you maintain at least some level of control, but the edges are rough and you might slice off more (or less) than you meant to. I want to model my usage more like a table saw, a precision instrument that can make the exact cut just as I planned it

In terms of velocity, let me offer some numbers. In 6 months I generated >150k lines of code and merged 10k PRs to ship and iterate on https://plotalong.app

I follow best practices and isolate agents to continuously deployed dev environments, semi-manually review PRs and gate the release process between multiple protected envs. The project is getting close to 500 end-to-end tests in Playwright.

That’s just working nights and weekends. Before AI, it took my team at the office 4 years to produce this much work. There are some qualitative differences but the speed and results are real

I like your emoji suggestion. I realized little while ago I need to distinguish between different types of waypoints so this is great validation

I think you’re right about getting people into the actual app faster, before signup. I’ll have to prioritize that sooner than later

The idea is everyone opens the same route for coordinating and there’s just one source of truth for the group. And then when you’re all about to hit the road, everyone can use the nav app they’re already familiar with (or that’s built into their vehicle)

I will tackle the navigation aspect at some point if I do keep up on feature dev, though!

I got to the MVP state which was useful for my personal use case in about a month. I took it further than that as a learning exercise and as a means to share it with others. Some features that came later are live cursors (like Figma), elevation chart and grade overlay, and QR-code enabled collaboration links to make in-person sharing simple.

Check it out! https://plotalong.app

Figuring out the exact UI/UX I wanted was the hardest part. I did the branding myself, handdrawn on paper, traced in Procreate, and vectored in Sketch. Fast iterations and a good test suite made it possible to try lots of different approaches and refine the one I liked the most. There are roughly 4000 unit tests and over 300 e2e tests that run on multiple environments with fully automated CI/CD.

I’m using Mapbox for the frontend and the whole app is basically just a monolithic Cloudflare Worker. Claude pretty much implemented the entire thing. I got a lot of mileage out of self hosting a Gitea project and recording all my planning sessions as Milestones and Issues. Claude has his own account without admin privileges. The process of managing a team of agents to build this practically autonomously was a bit jaw dropping and eye opening to be honest.

I would love to hear from other pleasure & sport drivers about the features they use or want the most in a routing app. I have an Android app in Play Store review, if you’d like to be an early access tester shoot me an email at my handle @plotalong.app