alt Hacker NewsAlso includes news about a new Appstore, which can probably be seen as a reaction to the stories from last week:
We’ve created our own Pebble Appstore feed (appstore-api.repebble.com) and new Developer Dashboard. Our feed (fyi powered by 100% new software) is configured to back up an archive of all apps and faces to Archive.org (backup will gradually complete over the next week). Today, our feed only has a subset of all Pebble watchfaces and apps (thank you aveao for creating Pebble Archive!). Developers - you can upload your existing or new apps right now! We hope that this sets a standard for openness and we encourage all feeds to publish a freely and publicly available archive.
Replies
I read the drama last week, and after seeing this, I have to side with Rebble. I think they kept the community alive since Eric M cashed out and Fitbit shut it down. As the stars have aligned in recent years, Eric revives Pebble, but if Rebble wouldn't spend all the effort maintaining the app store, his consumer base would be much smaller and it would be much harder to bootstrap again.
With Repebble (Core Devices) and their new appstore (or/and apt-style repository system), Rebble seems obsolete, it's a bit sad. They deserve credit which they won't be able to claim anymore. They should be rewarded somehow for bridging the dark age, otherwise it seems they served purpose all until Eric returned and said "Thank You and fuck off".
Also, to me, Eric talking doesn't sound authentic, and I wouldn't be surprised if he's lying. I don't mean to insult though, mad respect for putting project like Pebble together.
Hope that there's some place and purpose for Rebble in the future.
Honestly this feels like the best possible outcome. It's pretty unusual for an appstore implementation to support multiple feeds[0], but it's great resilience to large company failures when they do. This way, users can totally still access Rebble's feed (and pay for a subscription if they like) just as before, but they are free to also use something else.
It is the *end user* who decides which feeds to trust, as it should be. And since it's built right into the app as a core concept, it doesn't take massive engineering effort to switch feeds if some sort of drama occurs.
[0] I'd normally call these repositories, but I've used Eric's term for consistency with the article.