I'm seeing slow load times on clockfaces (subjectively speaking), generally around 2 or 3 seconds. There is this thread, but even after the latest update seems to take this long. I'm logging the times before my app does anything (similar to other thread) so it's just a load of the app.
My clockface is nothing too crazy, though it does display heart rate, steps, etc. so reasonably stats heavy, a few text elements and svg arcs. I first figured it may be because I'm in development, but if I try a similar 3rd party clockface, I'll see similar load times. I'm testing it by allowing the clockface to load/run, then going into something like Today which will close the clockface app. I then try to go back to the clockface, and it takes 2, sometimes 3 seconds. Maybe my expectations are off, but that seems like a really long time (relatively speaking -- if I'm looking at an app and click back/home to look at my main screen, I'd expect a faster load time than 2 or 3 seconds).
The fitbit provided clockfaces seem to load much faster, so perhaps they were developed differently. Any suggestions? Any potential future work being done to streamline this a little? If the clockface stays running (by not launching another app) going back to it is fine, so it's only when the clockface is explicitly closed.
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.
Best Answer