01-20-2019 02:27 - edited 01-20-2019 12:41
01-20-2019 02:27 - edited 01-20-2019 12:41
Hi,
So far I have found the followings differences between the Sideloaded apps and apps from the Gallery Manager
Sideloaded Apps
* Pros: You can see companion side logs
* Pros: Easy to install on your own device during development
* Cons: Not easy to access the settings page... "Sideloaded apps" keeps loading and not showing the app in "Developer menu".
* Cons: Not easy to share with other non-technical users (beta testers)
Private Gallery App
* Pros: Easy to install to other users (just send the private link)
* Cons: No companion logs
--------
Are there other changes?
Are there any drawbacks if I am using the sideloaded app daily ... like in production?
Thanks!
Best Answer01-20-2019 04:06
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
01-20-2019 04:06
The gallery (public or private) is only required if you want to install the app on devices other than your own.
Best Answer01-20-2019 12:56
01-20-2019 12:56
Thanks!
I understand that the App Gallery is for when I want the app installed on other devices, but
are there any drawbacks if I am using the sideloaded app daily ... like in production?
So once an app is sideloaded is behaves exactly like a normal app?
That is, the companion is loaded under the same circumstances and communication between the device and the companion is done using the same methods?
What I have observed is that loading the sideloaded app is a pain. I keep getting "Failed to retrieve apps"... even after starting and stopping the Fitbit app on the phone... while for the normal apps I can access the settings from the usual place.
Best Answer