How I built the TrainFinder app for Alexa and Google with Conversation.one

Similarly to a lot of new ideas, Train Finder is a result of frustration by the Israel Railways app.

I live in Israel and I use the train to get to work and back home every day. Also, I ride a scooter so I know the exact time it takes to get to the train station and I don't even need to calculate the traffic time. 

On morning times, I found myself, struggling with the railways smartphone app more than once. sometimes it doesn't load and sometimes it just crashes. This way or another it was a waste of precious time. 

The immediate idea was asking Google Home for the train times, but it failed to provide a human understandable response. Then I realized I must do it myself. 

I remembered I was at a meetup a couple of weeks back where I heard about conversation.one solution and how I can write voice apps with almost no code.

I opened the railways timetable and write a short app with hard-coded train times from my home to work stations. 

After using it via my Google Home every morning for a few weeks, I understood it is really convenient and I decided to write a more generic app for the public.

Looking backward, choosing conversation.one was a smart move. After I wrote the code once I was able to use it in more than 5 different platforms with just a few clicks, including both voice and chat interactions. I honestly don't think I could have supported this variety if it wasn't for them.

Now that the app is running for a few days. I find conversation.one to be more effective than ever. The ability to update and track all the platforms in one place is priceless.

Try Conversation.one for free today!