Is it still worthwhile to learn how to develop for Sense

[Biceboca]

I have a Fitbit Sense (not Sense 2) which means I could still make apps and clock faces for it. I know that this would not be widely distributable (like in Europe), and likely the ability to publish to Gallery will go away in the not-too-distant future, but if that's the only (big) downside, I'm considering learning to do it for my own amusement anyway. But I don't want to invest the effort if my ability to modify even just my own watch will go away. Am I dependent on Google keeping the door open to that? Can I transfer files from my computer to phone (fitbit app) and then to my watch, no matter what Google does in the future? I have the developer menu activated already in my (old version) app. I like the older style app and don't plan to upgrade it at least on some devices, so I'm hoping I could just keep using the old app even if developer options are no longer possible in some future fitbit/google app. I have some coding skills (not too much Javascript or CSS, mostly Python and C++ which won't be too useful, but the point is, I am able to learn what I need to).  Mostly, I don't want to spend time learning about Fitbit OS and starting to make stuff if it is likely to be a complete waste, because even my ability to transfer to my watch goes away. I'm pessimistic because the developer option is linked to my fitbit account (which I haven't even yet converted to google account), so I'm guessing Google could take away that privilege. But I wonder what experienced developers think about this.

[Gondwana · Accepted solution]

Good question. The Fitbit OS development process can't be used off-line and, for authentication, it requires logging in to servers that are now managed by Google. Therefore, Google could indeed make development impossible. However, I'm not aware of any announcement that Google plans to do this imminently.