Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
thinkgear.net_sdk_dev_guide_and_api_reference [2014/07/01 12:49] neurosky [MENTAL EFFORT (BETA)] |
thinkgear.net_sdk_dev_guide_and_api_reference [2014/11/21 14:16] (current) Tai-Ting Tseng [Proper App Design] |
||
|---|---|---|---|
| Line 494: | Line 494: | ||
| Mental Effort is included in a Beta form. The Mental Effort Algorithm is not a formal inclusion of the Developer Tools 2.5 release but can still be tested in your application design. Questions or feedback? Email: [[[email protected]]] | Mental Effort is included in a Beta form. The Mental Effort Algorithm is not a formal inclusion of the Developer Tools 2.5 release but can still be tested in your application design. Questions or feedback? Email: [[[email protected]]] | ||
| - | For the most up to date versions of this algorithm and the corresponding documentation, please refer to [[developer.neurosky.com]] and any specific new algorithm preview packages. | + | For the most up to date versions of this algorithm and the corresponding documentation, please refer to [[http://developer.neurosky.com]] and any specific new algorithm preview packages. |
| </note> | </note> | ||
| Line 693: | Line 693: | ||
| ====== Proper App Design ====== | ====== Proper App Design ====== | ||
| <important>Before releasing an app for real-world use, make sure your app considers or handles the following:</important> | <important>Before releasing an app for real-world use, make sure your app considers or handles the following:</important> | ||
| - | |||
| - | * If your app's Handler receives a ''MSG_STATE_CHANGE'' Message with any value other than ''STATE_CONNECTING'' or ''STATE_CONNECTED'', it should carefully handle each possible error situation with an appropriate message to the user via the app's UI. Not handling these error cases well in the UI almost always results in an extremely poor user experience of the app. Here are some examples: | ||
| - | * If a ''STATE_ERR_BT_OFF'' Message is received, the user should be prompted to turn on their Bluetooth adapter, and then they can try again. | ||
| - | * If a ''STATE_ERR_NO_DEVICE'' Message is received, the user should be reminded to first pair their ThinkGear hardware device to their Android device's Bluetooth, according to the instructions they received with their ThinkGear hardware device. | ||
| - | * If a ''STATE_NOT_FOUND'' Message is received, the user should be reminded to check that their ThinkGear hardware device is properly paired to their Android device (same as the ''STATE_ERR_NO_DEVICE'' case), and if so, that their ThinkGear hardware device is turned on, in range, and has enough battery or charge. | ||
| - | * See [[#TGDevice States]] for more info. | ||
| * Always make sure your app is handling the [[#POOR SIGNAL/SENSOR STATUS]] Data Type. It is output by almost all ThinkGear devices, and provides important information about whether the sensor is properly in contact with the user. If it is indicating some sort of problem (problem == not 0), then your app should notify the user to properly wear the ThinkGear hardware device, and/or disregard any other reported data values while the [[#POOR SIGNAL/SENSOR STATUS]] continues to indicate a problem, as appropriate for your app. | * Always make sure your app is handling the [[#POOR SIGNAL/SENSOR STATUS]] Data Type. It is output by almost all ThinkGear devices, and provides important information about whether the sensor is properly in contact with the user. If it is indicating some sort of problem (problem == not 0), then your app should notify the user to properly wear the ThinkGear hardware device, and/or disregard any other reported data values while the [[#POOR SIGNAL/SENSOR STATUS]] continues to indicate a problem, as appropriate for your app. | ||