Legacy Apps/Watchfaces with New Pebble, should try to recompile

Watchapp/Face Developers Corner
1

Hi !

So I am using specific watchface that connects to certain personal site (nightscout) and collects data and displays (every minute). I managed to install this legacy watchface (urchins-cgm) to new PT2 and it works without any problems.

So I was wondering, would it make sense to try to recompile watchface (it has c and js code) with new SDK or would be that wasted effort… My watch uses about 7% of power per day (most of this would be from this watchface and notifications). It is connecting to site every minute, so I imagine even with newer SDK power usage would not be much less. So far I haven’t seen any problems with watchface. Would it be even possible to just recompile without bigger changes to code?
This watchface I am using was not created by me, it seems that main developer stopped maintaining it long time ago, about 7 or so years ago I made small change on js code, but I have no other experience with pebble code. Would it be hard for someone like that to “upgrade” old code to new SDK.

Thanks for any answers and hints,

Andy

2

It depends. Most of the SDK migration would just be updated the WAF build script and updating the appinfo.json to be a package.json file and using the updated schema. The more important question would be what are you aiming to do? If it’s just an upgrade for upgrahing’s sake that would not be worth the effort IMO. If you want to add more features then it may be worth it. If you’re hoping for better battery life that almost certainly won’t change by simply recompiling