After some discussion, we have elected to go the "framework" route for recalculation. While users of Ferrostar will always be able to access state updates, including whether the user has deviated from the route, recalculation is common enough and annoying enough that we see value in offering a "full-service framework" approach to recalculation for the common case.
What this means:
The FerrostarCore at the imperative shell level (iOS / Android) will watch for route deviations.
When a deviation is detected, it will do some sanity checks (did we recalculate recently? Do we already have a request in flight? etc...) and, if applicable, invoke getRoutes and then invoke a delegate method informing the application of the available alternative routes.
After some discussion, we have elected to go the "framework" route for recalculation. While users of Ferrostar will always be able to access state updates, including whether the user has deviated from the route, recalculation is common enough and annoying enough that we see value in offering a "full-service framework" approach to recalculation for the common case.
What this means:
FerrostarCoreat the imperative shell level (iOS / Android) will watch for route deviations.getRoutesand then invoke a delegate method informing the application of the available alternative routes.