What stages should the work be divided into?
Posted: Mon Jan 06, 2025 4:56 am
It is best to build the work itself from simple to complex.
How it was for us :
First, we made a function to search for an address in the application without building a route.
Added the ability to build a walking route to the nearest scooter with an estimated travel time.
We have developed a full-fledged router that plots the route to the desired point, taking into account the specifics of riding electric scooters - this is the current stage.
The next step is to add a navigator function that will “guide” the user along the constructed route with voice prompts, as in classic navigators.
The time it takes to complete the work depends on belize whatsapp phone number the size of the team, its competencies, and the amount of available data. For us, the entire development process from team creation to implementation took about 9 months. But there was a prehistory: we had already tried to approach creating our own router earlier and even participated in hackathons with this task. There, we were looking for guys who would be interested in this idea and who would offer a fresh solution.
What to do next
Like many products, especially those aimed at a broad audience, the router is never finished. Routes need to be continually refined, analyzing where people actually find it convenient to travel and where they don’t. It’s a never-ending process of improvement, fueled by feedback, new data about user trips, and city infrastructure.
It is necessary to think a couple of steps ahead and make a product that can be upgraded, improved, and have new features added. Because the industry does not stand still: users are very sensitive to comfort, to the speed of applications and are accustomed to improvements.
Our next step is to create a classic navigator based on the router, which will "guide" the user along the route. We also plan to add intermediate points along the route to our router and create several route options. The user will be able to choose, for example, "the most convenient", where there will be no crossings and stairs, or "the fastest". If the navigator for cars has the option "no toll roads", then in the case of another type of transport it can be a filter "no underground crossings" or "no speed limit zones".
In any case, all new products should be built on analytics of user trips and be flexible for algorithm improvements and implementation of new developments. This is the only way to give users the functionality they really need.
How it was for us :
First, we made a function to search for an address in the application without building a route.
Added the ability to build a walking route to the nearest scooter with an estimated travel time.
We have developed a full-fledged router that plots the route to the desired point, taking into account the specifics of riding electric scooters - this is the current stage.
The next step is to add a navigator function that will “guide” the user along the constructed route with voice prompts, as in classic navigators.
The time it takes to complete the work depends on belize whatsapp phone number the size of the team, its competencies, and the amount of available data. For us, the entire development process from team creation to implementation took about 9 months. But there was a prehistory: we had already tried to approach creating our own router earlier and even participated in hackathons with this task. There, we were looking for guys who would be interested in this idea and who would offer a fresh solution.
What to do next
Like many products, especially those aimed at a broad audience, the router is never finished. Routes need to be continually refined, analyzing where people actually find it convenient to travel and where they don’t. It’s a never-ending process of improvement, fueled by feedback, new data about user trips, and city infrastructure.
It is necessary to think a couple of steps ahead and make a product that can be upgraded, improved, and have new features added. Because the industry does not stand still: users are very sensitive to comfort, to the speed of applications and are accustomed to improvements.
Our next step is to create a classic navigator based on the router, which will "guide" the user along the route. We also plan to add intermediate points along the route to our router and create several route options. The user will be able to choose, for example, "the most convenient", where there will be no crossings and stairs, or "the fastest". If the navigator for cars has the option "no toll roads", then in the case of another type of transport it can be a filter "no underground crossings" or "no speed limit zones".
In any case, all new products should be built on analytics of user trips and be flexible for algorithm improvements and implementation of new developments. This is the only way to give users the functionality they really need.