...
SAF-231: Green “No known contact” is shown even when no HA is configured. The screen should be Greay and direct the user to configure an HA.
LOC-1: The code assumes that if the App cannot access location this is an App permissions issue. It might not be. It might be that Location is disabled at the Device level. When this happens the APp confusingly keeps directing the user to an App permissions screen that already has the right settings, and never helpd them to find the actual Device-level setting to turn location on.
LOC-2: In states where the In-App setting is “on”, but App location permissions are denied OR location is disabled at Device scope, the “Dashboard” shows “Location Active” with a green check. This can be a source of confusion in several scenarios (ee details belowsee details below). We could consider a different UX in these cases (although a red X might be equally confusing as it won’t show the toggling of the in-app setting).
LOC-3: During onboarding, if I choose to “Enable Location” but then deny the App location permissions, the in-app setting gets set of “off”, which makes the later flow for enabling location complex& unintuitive. In this scenario it seems it would be better to set the app setting to “on”.
LOC-4: At the end of Onboarding, the “all finished” screen does not correctly reflect the Device-level location settings, so it can show a green tick, even though location is not properly enabled, and the immediately following main screen shows Red: Unknown.
LOC-5: Some inconsistency in language: location history / location data / location inactive; Settings screen / Dashboard
LOC-6: Clumsy wording: “enable the app to access your location”
...