Just a handful of comments on 1.0.58 since I will not be able to attend today's review meeting:
After I set the target location, I see a yellow dialog telling me 'Travel direction not recognized'. I think this dialog should not tell me about a problem, but about a solution. For example, if the problem is that my device is not being held horizontally: tell me I need to hold device horizontally. If azimuth cannot be calculated because I am not moving, tell me I need to move etc.
I was expecting the arrow to point to the direction of the target even if in stationary mode. Kind of like the compass in my phone is able to tell my azimuth even if am not moving.
In general, it seems to me like the arrow is showing erratic direction as I move. Testing around Esri Campus.
There is a tiny blue arrow on top of the circle which never moves. I am not sure what is the meaning of this arrow. In the BeeLine app they use a couple of small circles to provide fixed points in the UX. It seems more appropriate to me. I suggest we only have ONE arrow in this app.
Qt Sensor includes capability to tell the tilt of the device. I think this could be useful (when available). For example, if I have my phone vertically, then it will be hard for us to get the user's Azimuth. The app should probably tell me that I need to hold it somewhat horizontally for the arrow to be accurate.
The moon icon is cool. The sun icon is way too similar to settings,
Yes 'Travel direction not recognized' is not great - we don't have a better sentence yet. Here are some suggestions. Please contribute others:
This app doesn't work when you are stationary, start moving.
Move to determine direction.
Start moving!
Version 1 of this app does not use a compass. Not all devices have a compass built in, so compass behavior would need to be incorporated in the app as an optional extra. Future version.
Every day of this project we have discussed and debated the use of the circle and small arrow. This ongoing discussion and your comment really tell us there's a problem. To see the difference we will add a switch to remove it completely to try the app out in both 'states'.
Just a handful of comments on 1.0.58 since I will not be able to attend today's review meeting: