https://potniq.comIt's a travel tool for business travelers that figures out your suggested departure times for your entire itinerary based on predicted traffic patterns. Think Flighty but for all the non-flight parts of your trip.
You first build a travel itinerary with your legs - flights, activities, hotels (and hotel returns) and it tells you things like "leave your hotel at 7:40am" before your 8:30 meeting - in a single itinerary, no need to do the google maps acrobatics for every two items in your itinerary.
While it's aimed at frequent business travellers I personally use it for all family leisure travel and daily itineraries around town as well - "do I have time for lunch at home after my son's class or should we bring packed lunch".
I built it as during my time working in developer relations I traveled a lot, and always built unnecessary buffers and kept nervously glancing at my watch or phone to see if my planned time to leave still holds.
Tech-wise, currently it's Remix web app with a NodeJS/Fastify backend and Supabase for storage, and relying on google maps for route duration calculations. I want to expand it to native mobile clients in the future as well.
I am using it as playground on product thinking, ruthless prioritisation based on user benefit, figuring out unit pricing and economics, sensible architectural design, and exploring how including AI-enhanced features here and there can help make the product better, not just include them for their own sake.
It's a travel tool for business travelers that figures out your suggested departure times for your entire itinerary based on predicted traffic patterns. Think Flighty but for all the non-flight parts of your trip.
You first build a travel itinerary with your legs - flights, activities, hotels (and hotel returns) and it tells you things like "leave your hotel at 7:40am" before your 8:30 meeting - in a single itinerary, no need to do the google maps acrobatics for every two items in your itinerary. While it's aimed at frequent business travellers I personally use it for all family leisure travel and daily itineraries around town as well - "do I have time for lunch at home after my son's class or should we bring packed lunch". I built it as during my time working in developer relations I traveled a lot, and always built unnecessary buffers and kept nervously glancing at my watch or phone to see if my planned time to leave still holds.
Tech-wise, currently it's Remix web app with a NodeJS/Fastify backend and Supabase for storage, and relying on google maps for route duration calculations. I want to expand it to native mobile clients in the future as well.
I am using it as playground on product thinking, ruthless prioritisation based on user benefit, figuring out unit pricing and economics, sensible architectural design, and exploring how including AI-enhanced features here and there can help make the product better, not just include them for their own sake.