Alternative to TripIt = TripWaffle

[tripwaffle]

@tripwaffle congratulations on a terrific app.

It seems intuitive and more visually appealing than others apps on the market.

It doesn't seem to be handling historic imports from Tripit. The three I've imported from earlier this year all appeared as "active trips" and it seems to have assumed they're 2027 despite clearly being 2026.

Would you mind contacting us through the app, so we can look up the specifics in this case. Much obliged.

 

[RooFlyer]

Just pushed a new iteration on the trip maps. Hope this ticks all your boxes...

Coo, yes, thank you.

 

[tripwaffle]

Also I just noticed it didn't pick up the right date and time from my trip it import for the first flight, this was either during the initial tripit import or when I added the seat number to the flight. This also happened with the first accommodation booking, picked up 12th instead of 13th.

If you wouldn't mind contacting us via the app, happy to debug these specifics. Thanks for the feedback.

 

[kpc]

Forwarded train trips from Amsterdam to Brussels return.

Tripwaffle: 1 vs Tripit: 0


kpc, there was a problem with your TripIt submission.
We received your email (Subject line: "FW: Confirmation, name: kpc, booking reference: xx_xx_, departure date: 12/07/2026") and placed it as a Note in your Unfiled Items.

Please visit our help page to see why TripIt might be unable to import your confirmation email.

But tripwaffle filed it exactly in the right place in my itinerary! Well done @tripwaffle !

 

[kpc]

Forwarded bus trip from Llubjana to Venice.

Tripwaffle filed it exactly in the right place in my itinerary but Tripit had a hissy fit!

Tripwaffle: 2 vs Tripit: 0

 

[V1213]

The print itineraries are pretty neat, in case anyone missed them.
Display of confirmation numbers + notes is optional...

Love the agenda view as a model for how a streamlined view could work on the app and online. I note that non-flight transportation shows up as a single line including both departure and arrival, while flights show up as separate departure and arrival lines.



In general, I prefer the single line approach, but some tweaks to the summary (at least for an online/app streamlined view) would be useful. In particular, if I were to glance at this for a rail journey I'd want to see my carriage and seat numbers so I can board the train without having to click through for more details. Additionally, the summary lists the station/stop addresses instead of their names (as demonstrated in the above screenshot). While knowing where the Linköping Central Station is is useful, in the summary I just want to know that it's "Linköping Central Station". The existing online/app view has this correct, but the summary pulls the address instead of the name.

Thanks for improving the non-flight transportation fields during the week. I note that rail doesn't have a spot for train number (although I've used the "Name" field for that in the above screenshot), and no non-flight transportation modes have a spot for operator or route (again, I've used the "Name" field in the above example). Operator is definitely useful in some contexts, where multiple providers serve a station (e.g. Europe).

 

[V1213]

Confirmed: we'll add support for TripIt's "driving directions" item type today, and see if we can back process existing imports.

I can now manually add driving, which is helpful - thanks. I see that TW adds an expected duration to the overall trip view, but doesn't generate a full event end time. An auto end time would help when it comes to calendar sync and agenda view, without me having to go and manually add it based on the estimate that TW is already generating.

Also, less importantly, driving trips are still not populating on TripIt imports, including new imports undertaken today.

 

[A321]

I'd love more customisable fields to be able to add more details into flight, cruises, hotels etc - i.e. able to edit all the fields that pull across from confirmation emails sent to the Robot - whether from new or editing incorrectly pulled across info.

 

[tripwaffle]

Love the agenda view as a model for how a streamlined view could work on the app and online. I note that non-flight transportation shows up as a single line including both departure and arrival, while flights show up as separate departure and arrival lines.

View attachment 504566

In general, I prefer the single line approach, but some tweaks to the summary (at least for an online/app streamlined view) would be useful. In particular, if I were to glance at this for a rail journey I'd want to see my carriage and seat numbers so I can board the train without having to click through for more details. Additionally, the summary lists the station/stop addresses instead of their names (as demonstrated in the above screenshot). While knowing where the Linköping Central Station is is useful, in the summary I just want to know that it's "Linköping Central Station". The existing online/app view has this correct, but the summary pulls the address instead of the name.

Thanks for improving the non-flight transportation fields during the week. I note that rail doesn't have a spot for train number (although I've used the "Name" field for that in the above screenshot), and no non-flight transportation modes have a spot for operator or route (again, I've used the "Name" field in the above example). Operator is definitely useful in some contexts, where multiple providers serve a station (e.g. Europe).

Work in progress today- acknowledged with thanks. Main part is overhauling the various fields we store against different event types.

 

[tripwaffle]

I'd love more customisable fields to be able to add more details into flight, cruises, hotels etc - i.e. able to edit all the fields that pull across from confirmation emails sent to the Robot - whether from new or editing incorrectly pulled across info.

Acknowledged thank you- will work on this today.