I understand that like other OS-AID apps, PwDs can use a variety of insulin pumps. This is great, and supports a variety of options for people.
The issue is for PwDs who review their data in the Tidepool Data Platform, the information from AAPS is being sent as a Tandem insulin pump. This either shows as "Tandem Insulin Pump" or Tandem Tandem (b/c I think it's sending both Maker and Model as "Tandem").
I would suggest (I'm both an employee who works in Support at Tidepool and a PwD using Trio) that Android APS represent itself as Android APS or AndroidAPS or AAPS, whichever is the preferred naming for users.
On the iOS side, this comes from the bundle ID e.g. com.nightscout.Trio or com.Loopkit.Loop. I'm not sure how Android apps work, but if you can tell me what information is being sent I can update our name list for the "friendly name" that users see in the platform.
I understand that like other OS-AID apps, PwDs can use a variety of insulin pumps. This is great, and supports a variety of options for people.
The issue is for PwDs who review their data in the Tidepool Data Platform, the information from AAPS is being sent as a Tandem insulin pump. This either shows as "Tandem Insulin Pump" or Tandem Tandem (b/c I think it's sending both Maker and Model as "Tandem").
I would suggest (I'm both an employee who works in Support at Tidepool and a PwD using Trio) that Android APS represent itself as Android APS or AndroidAPS or AAPS, whichever is the preferred naming for users.
On the iOS side, this comes from the bundle ID e.g. com.nightscout.Trio or com.Loopkit.Loop. I'm not sure how Android apps work, but if you can tell me what information is being sent I can update our name list for the "friendly name" that users see in the platform.