Well in my case, a simple restart of my device resolved the issue. I saw some people having the exact same issue on forums but no definitive solution was given. One time, my Fitbit Ionic would’t want to connect to the debugger displaying the message: ‘Connection error 1006’.I’ve tested on Chrome, Firefox, Safari, with the same result. ![]() Sometimes Fitbit Studio won’t find any of my devices nor simulators and will show ‘Error loading’.While developing, I encountered some issues which were out of my hands and I found very few information online about these: The returned value will be 30 if the current device is a Versa and we want to place the metric number 0. Similarly, the getIconY() returns the appropriate value depending on the passed value and the current deviceType. The returned value will be 290 if the current device is an Ionic and 250 otherwise. Now if I want to places horizontally my icon, I can simply use const x = getIconX(). Instead of using conditional clauses I used objects with specific keys. How to place visual elements according to device detection I think the CLI solution would be the better way to improve as the missing features with the Studio are erased with a local editor/IDE. Deploy to real devices (not sure it’s not possible but I couldn’t do it - feel free to comment if I’m wrong). ![]() Watch mode option to auto build & deploy on file save.One command to build & deploy to the emulator.Multiple tabs (to have multiple openned files)Īn easy way to add all these features would be to use an existing online editor like CodeSandbox but maybe there’d be business conflicts.In my opinion, the work flow need real improvements in 2 ways: Fitbit Studio I came back to Fitbit Studio where I only had to click once to build & deploy. So I had to repeat this flow process a lot of time to perfectly place my elements and this was too much. This process was fine at the beginning but became quickly tedious because developing an user interface demands you to be pixel perfect when the screen size is so small. Switch to the emulator to see the result.Execute fitbit$ install to deploy the app to the simulator.Execute fibit$ build to build the clock.But I was disappointed because the CLI has not a watch mode yet, neither a single command to build & deploy. When I saw that the dev team had created a Command Line Interface, I was super enthousiastic because I was going to code inside my familiar Text Editor/IDE ( VS Code) with auto-completion and other tools to speed up my work. I already had a clear idea of the design I wanted to create. ![]() So I took the time to draft a quick clock that I wanted and went to Fitbitdev to start developing. But after using almost all free clock faces, I thought there were missing designs (it always begins like this). I’ve a Fitbit Ionic since several months and I regularly switch clock face ( some are really great). The associated project to this article is my metrix clock face available on GitHub. In this overview, I’ll explain why my development was longer than I expected and how I faced different problems. The first result and prototyping can be fast but handling specifics scenarios and multiple devices support add a good level of complexity. When I started coding my clock face, I wasn’t expecting the need to work several weeks on it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |