Looks like it only had 130 users and as far as I can tell, you weren't making money from it, so I'd move onto something else, and accept that it's the nature of the beast when augmenting a platform that's out of your control.
Keep the project and results as a resume item. Take what you've learnt into that next project.
I'm sorry your project got pulled. You may or may not want to hear this but I would love if your talents were layered on, say Matrix/Element or XMPP, in part because I want those projects strong and they don't have the same risk of killing your project.
But I admit that's more ideological.
Question about your project: was there any warning? Any sign Google was taking inspiration from you?
I can understand your frustration, but this is one case where this is such an obvious product decision it would be a criminal for Google to keep meet and chat separate. Perhaps they took inspiration from Teams or many other chat products that integrate the two. The surprise is that they didn't just do this in the first place. This being Google, that is no surprise though.
I've never heard of Google Meet, but I usually see the successful devs who get Sherlocked are the ones who jump to a bigger pond.
As for platform dependency you want to have all your code internal and an API layer negotiating between the platforms' API (DOM/browser/rest/firebase/aws etc anything that isn't code you wrote) and your code
Then after accepting that the google specific stuff is a write off you can see how much work you are doing for yourself vs for google. Once you have that distinction you can make a velocity/ownership, feature orchestration/feature providing tradeoff
Following that you could quickly swap over to using Google's or Zooms or whoevers APIs (Meet add-ons SDK)
Looks like it only had 130 users and as far as I can tell, you weren't making money from it, so I'd move onto something else, and accept that it's the nature of the beast when augmenting a platform that's out of your control.
Keep the project and results as a resume item. Take what you've learnt into that next project.
I'm sorry your project got pulled. You may or may not want to hear this but I would love if your talents were layered on, say Matrix/Element or XMPP, in part because I want those projects strong and they don't have the same risk of killing your project.
But I admit that's more ideological.
Question about your project: was there any warning? Any sign Google was taking inspiration from you?
Its laughable to think a corporation got inspired by this tiny extension for obvious chat features. Its just an overlap.
I can understand your frustration, but this is one case where this is such an obvious product decision it would be a criminal for Google to keep meet and chat separate. Perhaps they took inspiration from Teams or many other chat products that integrate the two. The surprise is that they didn't just do this in the first place. This being Google, that is no surprise though.
This reads like a Linkedin post, I'm sure A) you can make something else B) you didn't think this would last forever
Good luck!
You still built it and learned a lot. I think that is what really counts. Learn from this one and build another cool project
I've never heard of Google Meet, but I usually see the successful devs who get Sherlocked are the ones who jump to a bigger pond.
As for platform dependency you want to have all your code internal and an API layer negotiating between the platforms' API (DOM/browser/rest/firebase/aws etc anything that isn't code you wrote) and your code
Then after accepting that the google specific stuff is a write off you can see how much work you are doing for yourself vs for google. Once you have that distinction you can make a velocity/ownership, feature orchestration/feature providing tradeoff
Following that you could quickly swap over to using Google's or Zooms or whoevers APIs (Meet add-ons SDK)
"sherlocked"