If they clicked on a registered slot, they would see the relevant contact details and could choose to call the driver. If they were already parked, it would take the data from the browser’s local storage. Users would see all parking spots and click on an empty one to fill in their details. The database was FireBase, so we had realtime support and JSON support, and no need for a back end. It was hosted by using GitHub’s free static page hosting. No webpack and no JS bundles at all! Just vanilla JavaScript. To make the process better, I created a web app. If so, they would have to call the other driver and hope that they were not in the middle of a meeting so they could go and move their car out of the way. Before leaving the office, a driver had to check whether anyone was blocking their car.
All drivers marked where they were parking, and their names and phone numbers. From a Whiteboard to a Web Appīefore there was an app, there was a big board. In every double-parking space, the first driver parks inside, and the second parks outside. The parking space is very limited, so people park in spaces intentionally designed for double-parking, where one car is blocking another. The company I worked for had an office for around 2,000 employees in the middle of downtown Tel Aviv. And beyond: Will chatbots one day replace all traditional apps? Chatbots have so much potential! In this WhatsApp chatbot tutorial, I wanted to share my learning journey, best practices I discovered, and my predictions on the app vs. What would happen if I were to create a WhatsApp chatbot to solve the specific use case, instead of a web app? Would people like it better? Would it be more useful?īut the story is much bigger than that. Feedback on the web app prompted me to do an experiment.
Long ago, I built a web app for an enterprise (200k+ employees).
0 kommentar(er)
