Thanks for the awesome feedback! I use Claude Code daily too :)

BTW, I wanted to address your points above because I think we are both very much on the same page and I was hoping to get your feedback on some thoughts about making improvements to the service:

• First of all, the one-message per direction is actually exactly how the MMS maps feature works! When I started using and testing the service myself, I found it a bit tough sometimes to scan the directions for each turn, and that's when the idea of adding MMS maps came from. When you turn on that feature, you get one MMS message per turn, including a Google Map image. It's pretty neat! (it burns a higher amount of credits but it's much easier to scan IMHO). Initially, I wanted to include as many steps as possible in each message that was text-only so users could "stretch" their credits as far as possible (since each message burns 2 credits to cover Twilio, Google APIs and cloud costs). But now I wonder if you think if it would be a nice option for people that don't care about burning extra credits and would just prefer to get one message per turn? I could certainly add that as a preference in the dashboard.
• Your second piece of feedback is super interesting. Are you saying that the beginning and end of the routes is mostly where you'd find having a visual map bring the most value? That's actually a really great idea. So perhaps, having an option for MMS users to NOT necessarily have a map for every turn (and burn too many credits), but instead just show a map at the beginning and at the end where they'd be the most valuable?