I spent way too much time on this yesterday! Love it but it's super tricky.
I'd love a (realistic) "cheat" that lets me see the departure boards without being at the station - that way you can plan the journey at least a little upfront. I'd do that on my phone anyway
I'm a solo dev founder working on Potniq (https://potniq.com) - a business travel tool that tells you exactly when to leave based on your entire itinerary.
I used to work in devrel, and traveled a lot for events, and I always struggled skipping things like workouts, looking at the time on the last day of a conference trying to check whether it's time to leave yet - so this gives me the opportunity to build a tool I would have loved to use.
Currently I'm working on a LLM-powered booking email parser, that ingests forwarded booking confirmations and adds flights, hotels, etc. to your itinerary.
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.
- Netflix shouldn't charge cards without verifying email addresses. Security should be an integral part of UX, and not subservient to it.
- Individual email address canonicalisation/resolve _could_ actually be a standard. I'm not sure whether it is or not, but if we can agree on emoji we could also maybe agree on something that binds the internet together. Email is infrastructure, Netflix is not.
- There is still a potential issue by having configured catch-all email addresses on some domains, but we should in that case optimise for the hundreds of millions of gmail.
Frankly this title is worthy of the Daily Mail. I expected more of GitHub.
It merely describes one individual proposal currently going through the process of consultation before being debated in the parliament, nothing else.
"FUTURE-PROOFED FOR IOS & ANDROID
When you use Supersonic, you can be sure you are using the most up-to-date visual and functional paradigms of both platforms. That means iOS8 and Android KitKat today, and future-proofed for the next generations."
For me it was just the experience with both.
Coming from Java background it was exactly the opposite when I was first dynamic languages, but it got easier eventually (quickly).
I guess you just have to try out different approaches (and mixed ones, Dart and ActionScript come to mind) and gradually understand benefits of each way.