4 ms·
i cannot think how this is a good idea you’re building a service on top of somebody else’s service, especially Google’s as someone who built a SaaS on top of
by ushakov 5y ago
i cannot think how this is a good idea
you’re building a service on top of somebody else’s service, especially Google’s
as someone who built a SaaS on top of Google APIs, i’d be afraid to build another service that depends on them
Google will change and break their APIs more often than you’d expect, introduce new API versions and deprecate old ones without any backwards compatibility
you’ll be stuck in cat and mouse game fixing every damage introduced by changes in the API and your software will break completely when they decide to deprecate the API in favour of a new one
it’s only a matter of time until this product breaks because of Google’s API policies (remember there’s no warranty?) and your users/customers won’t keep up with that for long
advice for somebody who learned it the hard way: do not build a product that depends on Google, or you risk losing your business
- erwincoumans 5y ago>> Google will change and break their APIs more often than you’d expect Spot on! Is there a full open source analytics solution (with web frontend) without such proprietary dependencies?
- ushakov 5y agoi'd recommend Plausible personally using them as API to integrate analytics for my customer's sites main reason i choose Plausible is because it is made by a EU-based company honouring EU privacy values, meaning no cookies, no personal data collection and easy data export the team is very responsive and are happy to take feedback they are sustainable and make money offering a hosted service https://github.com/plausible/analytics https://github.com/plausible/analytics
- ajcoll5 5y agoThere's Matomo, formally Piwik. https://github.com/matomo-org/matomo https://github.com/matomo-org/matomo
- psnehanshu 5y agoThe software we are building at my current job is totally dependent on Google's APIs. Is this something I should tell my manager?
- ushakov 5y agoi suggest reading terms of services first https://developers.google.com/terms https://developers.google.com/terms then go to Google’s issue-tracker and search for the API you are looking to use, check how many bugs are open currently and how long it takes them to resolve http://issuetracker.google.com/ http://issuetracker.google.com/ in case of the APIs i was using a bug could take months till it even gets accepted often the APIs don’t have versioning, so when they make a breaking change you can’t simply go back to an older version, instead you’ll have to update your code good thing is that they usually notify when the changes happen so you have some time to make adjustments
- aaaaaaaaata 5y agoWhat was your Google dependent SaaS?