-
It depends - what happened with Bangle.js 1 is often apps stopped being maintained after the first 6 months - and then if there's a problem it was me that had to sort it. The 'Run' app is an attempt to replace 'BangleRun' that had exactly that issue and turned into a maintenance nightmare because it was written in TypeScript and mostly undocumented... So I guess with this one I'm a bit more worried about maintenance precisely because the last one was such a pain.
Maybe not my place to say, but I don't think you should feel obliged to take over unmaintained apps. If an app that someone else contributed has a problem, and the original authors have lost interest, that is a gap for someone else to step in and take part - either by adopting the existing app, or creating a new one. In some cases, it might inspire someone to do something even better than the original. I can understand how having all the apps under one roof (repository) with one list of issues could give you the feeling that you need to take responsibility, but you've already provided an amazing platform, you don't need to shoulder everything yourself.
You are reading a single comment by @Gordon and its replies.
Click here to read the full conversation.
myownself
@Gordon
A fork is no problem at all - but what I want to avoid is duplicated code for calculating stats. For instance when I first did the app, distance recording was wrong and @HughB fixed it. Maybe after there are forks someone discovers a similar issue - we don't want to have to copy/paste that change to every fork. Same for adding more options or types of stat - ideally we make it so if someone adds another type of stat to display, you can then get that stat in other apps pretty easily - when someone contributes everyone benefits.
Right now the app was pretty simple, but when you start adding configurable locale settings/etc things are going to start getting more complicated.
It depends - what happened with Bangle.js 1 is often apps stopped being maintained after the first 6 months - and then if there's a problem it was me that had to sort it. The 'Run' app is an attempt to replace 'BangleRun' that had exactly that issue and turned into a maintenance nightmare because it was written in TypeScript and mostly undocumented... So I guess with this one I'm a bit more worried about maintenance precisely because the last one was such a pain.