I've got to side with @bentossell, I use Citymapper in Berlin, London and SF and would use it everywhere if possible. The bot seems very gimmicky and slower than opening the app and picking your locations.
Maybe they'll bring it to their apps. I still wonder what the right interface for bots is. Pressing a button is faster than writing text, what about speech or using native APIs like GPS etc to enhance a bot.
Bots are exploding, @rickats is correct, but what is the best use case ?!
OK, sorry but how is this a bot?
It's just a normal step-based interface glued into some sort of fake conversational UI with buttons instead of real textual responses.
Citymapper is the perfect example of a product that gets value from its UX/UI. It loses value if you remove the interface.
Report
My only quibble with the app itself is I feel like I've saved a bunch of routes or commutes that are supposed to appear on my home screen, but then they only appear there sporadically, if at all. If somehow the bot could always remember precisely the same "usual" routes in the morning and at night, I'd find it helpful!
Ha! After I answered a few questions, one of the possible options was "Show me my stuff" and it listed for me exactly what I mentioned a few minutes ago I'd find useful. Kudos to Gobot and Citymapper!
Report
I like it, i'll keep testing it. CItymapper in general is the only reason I would buy a wearable (watch) after eons without one. It's interface, interaction and experience make it even more useful than it already is in any other gadget.
I like this as a web interface, when I'm sitting at my desk and planning a trip, but I'd need to fling it to my phone eventually to "take it with me" to make it useful.
That said, Citymapper is one of my all-time favorite mobile apps. It works so well and so fast, and the app's UI is really well done that I doubt I'd use this bot as the process seems slower.
Replies
Papermark
Noti
Tribe Games
Showbox
The Un-official Messenger Button
Delphi