Keep the project and results as a resume item. Take what you've learnt into that next project.
But I admit that's more ideological.
Question about your project: was there any warning? Any sign Google was taking inspiration from you?
Good luck!
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)