Newbie question about sideloading vs publishing

[PatTheDog]

I've made a clock face for a specific personal use case that I don't intend to make available in the Fitbit Gallery. Having side loaded it from Fitbit Studio, it's running fine but battery life isn't great.

I see in the guides that it's possible to publish the .fba but keep the link private.

Are there any advantages to doing this? For example I'm wondering if the app will run more efficiently I install the clock face via the private link rather than sideloading from Fitbit Studio.

[MarioDings]

You can always use a private link before publishing for the world via Fitbit. That’s the only way to do some good field testing. I use it a lot. Testing midnight, testing with other apps, testing with stupid users (Me, myself and I).

But it doesn’t change the battery consumption. I think you make the app too difficult and let the interpreter do too much.There are a lot of improvements to be made theoretically.

There is no difference between sideboard, private or public, other than  the use of OATH or app cluster storage.

[PatTheDog]

👍

[PedanticPete]

---

@MarioDings wrote:

[…] testing with stupid users (Me, myself and I) […]

---

How true! Thanks for making me Laugh!