←back to thread

Show HN: Ambulate – Detailed Trip Planning

(ambulate.app)
93 points _phnd_ | 1 comments | 22 Oct 24 12:19 UTC | HN request time: 0.2s | source

Ambulate was created because planning hiking trips using spreadsheets and various map solutions got chaotic. I wanted an app to manage and map multi day trip itineraries in the outdoors/backcountry.

Features - Manage itineraries - Add activities and map markers - Add routes (upload GPX or plot by hand on map) - Desktop and mobile

It is free to try (login using Google or create a user). Alternatively the slides on the home page give an idea of the UI.

I'll appreciate any thoughts and feedback you care to share:)

Show context
jll29 ◴[22 Oct 24 20:22 UTC] No.41918304[source]▶
If anyone needs a good (related) startup idea, here's one for free:

Complex trip planning for professionals, but in a different way from Ambulate - not hiking trips, but transactions across Web sites: I really hate the way how today you cannot "properly" book a flight, hotel, train like you would do it in a SQL transaction

  BEGIN TRANSACTION
    book train
    book flight
    book hotel
  COMMIT;
Only if all three are available and execute the reservation without error do I also want to execute the other ones; that's a prime use case for DB-like transactions, but across Websites. Because no point getting only the flight if I have no-where to stay etc.
replies(7): >>41918513 #>>41919031 #>>41919123 #>>41920769 #>>41921149 #>>41923935 #>>41926200 #
1. Karrot_Kream ◴[22 Oct 24 21:55 UTC] No.41919123[source]▶
It sounds like the difficulty is mostly in the "book train", "book flight", and "book hotel" steps along with the associated rollback actions. Booking.com and Expedia probably have built their moat around aggregating these steps. If anyone works in this industry, I'd love to know if that's not the case.