Question 1

1. BLE connection states

Accepted Answer

Do we know exactly how the app behaves when the device connects, disconnects, times out, reconnects, or has weak signal? Rate 0–2: 0 = Not defined yet, 1 = Partially defined, 2 = Clearly defined and tested.

Question 2

2. Android/iOS permission handling

Accepted Answer

Do we handle Bluetooth, location, background behavior, notification permissions, denied permissions, and OS-specific differences clearly? Rate 0–2: 0 = Not defined yet, 1 = Partially defined, 2 = Clearly defined and tested.

Question 3

3. Firmware compatibility

Accepted Answer

Can the app detect which firmware version is installed and whether it is compatible with the current app version? Rate 0–2: 0 = Not defined yet, 1 = Partially defined, 2 = Clearly defined and tested.

Question 4

4. Device state model

Accepted Answer

Do we have a clear model for device states such as ready, busy, measuring, updating, disconnected, error, low battery, and recovery? Rate 0–2: 0 = Not defined yet, 1 = Partially defined, 2 = Clearly defined and tested.

Question 5

5. Error recovery

Accepted Answer

When something fails, does the user know what happened, what to do next, and whether their data and device are safe? Rate 0–2: 0 = Not defined yet, 1 = Partially defined, 2 = Clearly defined and tested.

Question 6

6. Update interruption

Accepted Answer

Do we know what happens when an app update, firmware update, or configuration update is interrupted? Rate 0–2: 0 = Not defined yet, 1 = Partially defined, 2 = Clearly defined and tested.

Question 7

7. Offline behavior

Accepted Answer

Can the product still behave safely and understandably when the phone or device is offline? Rate 0–2: 0 = Not defined yet, 1 = Partially defined, 2 = Clearly defined and tested.

Question 8

8. Cloud sync rules

Accepted Answer

Do we know when data is synced, retried, overwritten, delayed, or rejected? Rate 0–2: 0 = Not defined yet, 1 = Partially defined, 2 = Clearly defined and tested.

Question 9

9. Conflict resolution

Accepted Answer

If app, device, and cloud disagree, do we know which source wins and why? Rate 0–2: 0 = Not defined yet, 1 = Partially defined, 2 = Clearly defined and tested.

Question 10

10. User account and device ownership

Accepted Answer

What happens when a device changes owner, user, phone, account, or company? Rate 0–2: 0 = Not defined yet, 1 = Partially defined, 2 = Clearly defined and tested.

Question 11

11. Remote configuration

Accepted Answer

Can cloud configuration changes be applied safely without breaking app or device behavior? Rate 0–2: 0 = Not defined yet, 1 = Partially defined, 2 = Clearly defined and tested.

Question 12

12. Data history and auditability

Accepted Answer

Can the team understand what happened after the fact, especially when users report issues days later? Rate 0–2: 0 = Not defined yet, 1 = Partially defined, 2 = Clearly defined and tested.

Question 13

13. Support diagnostics

Accepted Answer

Can support export or view a diagnostic report with phone model, OS version, app version, firmware version, BLE status, last sync, last error, battery, and cloud status? Rate 0–2: 0 = Not defined yet, 1 = Partially defined, 2 = Clearly defined and tested.

Question 14

14. Logging and observability

Accepted Answer

Can the team understand recurring failures without asking users to reproduce everything manually? Rate 0–2: 0 = Not defined yet, 1 = Partially defined, 2 = Clearly defined and tested.

Question 15

15. Architecture ownership

Accepted Answer

Is there a clear technical architecture across firmware, app, cloud, data, and support? Rate 0–2: 0 = Not defined yet, 1 = Partially defined, 2 = Clearly defined and tested.

Question 16

16. Product requirements clarity

Accepted Answer

Are the important edge cases written down before development becomes expensive? Rate 0–2: 0 = Not defined yet, 1 = Partially defined, 2 = Clearly defined and tested.

Question 17

17. Test strategy

Accepted Answer

Are weak signal, offline mode, failed sync, firmware mismatch, permission denial, and interrupted updates part of testing? Rate 0–2: 0 = Not defined yet, 1 = Partially defined, 2 = Clearly defined and tested.

Question 18

18. Launch readiness

Accepted Answer

Do product, development, support, and management share the same understanding of what “production-ready” means? Rate 0–2: 0 = Not defined yet, 1 = Partially defined, 2 = Clearly defined and tested.

Online Launch Readiness Score

Send your result

Is your connected product ready to launch?

Almost there: check your inbox

Launch readiness questions

Send your result