After the user updated the CSV file and started to calculate.
The calculation itself will/may be very fast? But there maybe some possible delay we don't know yet.
From Steve:
I believe the main response delay will be in fetching data from the open-meteo weather API -- we don't know yet how long that will take and whether it will vary from a lot. Therefore we need to assume it could take several seconds, hopefully never more than 10-15 seconds, after the .csv file is read to fetch the data and do the calculations. The UI should show the user that the app is calculating during this possible wait time.
From me:
Is it possible that estimating the waiting time could be challenging? It might be difficult to be entirely accurate and it needs to consider if there is any connection issue from the user's side. Instead, I suggest:
Setting up a transition screen to inform the user that the system is 'calculating' and they may need to wait.
Additionally, I wonder if we can configure it so that if the waiting time exceeds 5 seconds, the 'waiting screen' will appear. Prior to that, it might be acceptable to skip the 'waiting screen'?
After the user updated the CSV file and started to calculate.
The calculation itself will/may be very fast? But there maybe some possible delay we don't know yet.
From Steve: I believe the main response delay will be in fetching data from the open-meteo weather API -- we don't know yet how long that will take and whether it will vary from a lot. Therefore we need to assume it could take several seconds, hopefully never more than 10-15 seconds, after the .csv file is read to fetch the data and do the calculations. The UI should show the user that the app is calculating during this possible wait time.
From me: Is it possible that estimating the waiting time could be challenging? It might be difficult to be entirely accurate and it needs to consider if there is any connection issue from the user's side. Instead, I suggest:
--
Original conversation screenshot: