This is a bit of a what-if, but I had a Pebble watch back then and was considering trying to make an app for it. The idea that, if I had succeeded and published the app, that Rebble would be claiming ownership over my binary and threatening legal action against the original Pebble creator, to be really quite ridiculous and affronting.
I am one of the developers who did make Pebble apps - here's a screenshot with the Pebble version of Weathergraph on Eric's watch: https://x.com/weathergraph/status/1959253197664469246 Today is the day I found out Rebble is claiming the ownership of my app's binaries. All I can say is that they don't have it.
Pebble, Rebble, and a path forward
231–240 of 258 posts
Re: Pebble, Rebble, and a path forward
#232Earlier quoted context omitted.
Updated themselves
Are they still open source? If so, why does it matter who updated them?
Re: Pebble, Rebble, and a path forward
#233Summarizing the dispute, for anyone interested: Rebble's "one red line" is "there has to be a future for Rebble in there." They fear being replaced/made irrelevant after Core builds their own infrastructure using Rebble's work. They want guarantees that if they give Core access to the app store data, Core won't build a proprietary/walled garden that cuts Rebble out. There's also emphasis on "our work," "we built this…
They sent an email a few minutes after I posted, saying that their fulfillment centre dropped the ball and they're escalating internally. I guess complaining on HN worked. Hope they can figure out the dispute with Rebble. Maybe they end up hosting apps on a package manager and create some binding contract?
Re: Pebble, Rebble, and a path forward
#234Earlier quoted context omitted.
What? Absurd. It gives them the right to nothing at all. They can make an app store themselves any time they want.
Well... I have a watchface on the old store. It is non functional because external APIs changed. I just recently decided to update it, and there is now a much improved version in my github account. I asked Rebble weeks (!!) ago to give me back access to my own account and binaries on their store and to this day, I heard nothing from them. Nada. If Core start a new store, I will immediately put the new, much improved…
Re: Pebble, Rebble, and a path forward
#235Earlier quoted context omitted.
Seems cheap to me. Host anything and you're gonna need developers. Developers are expensive. A hundred thousand dollars is pretty much what you'd pay for a single developer in a year. 5 Devs is still a small team and that's half a million dollars per year.
There are countries other than the US.
Re: Pebble, Rebble, and a path forward
#236Earlier quoted context omitted.
Well... I have a watchface on the old store. It is non functional because external APIs changed. I just recently decided to update it, and there is now a much improved version in my github account. I asked Rebble weeks (!!) ago to give me back access to my own account and binaries on their store and to this day, I heard nothing from them. Nada. If Core start a new store, I will immediately put the new, much improved…
Do you mean that you uploaded it to Pebble back in the day before Rebble? Have you gone through these steps? https://help.rebble.io/recover-developer-account/?viewall=tr...
Re: Pebble, Rebble, and a path forward
#237Earlier quoted context omitted.
There are also a bunch of cancelled order right now, so maybe they suddenly had a surplus of available devices...
Yeah. I bought a black duo out of nostalgia and wanting pebble to succeed, but not interested in the time and realized I don't love them enough to want to wear a white one. Fickle me, I guess.
Re: Pebble, Rebble, and a path forward
#238Re: Pebble, Rebble, and a path forward
#239Earlier quoted context omitted.
I think you're 100% right WRT the open-source code Rebble developed publicly. The big open question right now seems to be about the private app store data Rebble archived (and further developed) - which looks legally murky to me.
But they don’t have any rights to that data. They don’t own redistribution rights for the apps.