The problem with this model is that if you aren't able to do due diligence yourself due to technical restrictions, how are your end users supposed to overcome the even greater technical restrictions on due diligence that using your service imposes?

Fantastic concept! But I'm completely turned off by the IP terms ([1] below). This suggests LogoFox is pushing icons without doing IP checks, and selling them as finished logo designs without any assurance that the user won't get sued because of this.

Don't take this as negative feedback, but as a tip to re-think the legal side approach. Better would be that you

(a) you do some copyright checks and your terms state what checks have been done; and (b) once someone pays for the logo, they own the IP rights in the logo.

[1] "Third Party Design Resources – You may use purchased End Products outside of the Site, whether for commercial or personal purposes. Prior to creating and using any End Product, LogoFox highly recommends you to perform due diligence to determine that the use of the Design Resources is free of any adverse claims and is not subject to any third party rights. LogoFox may also use symbols provided by The Noun Project, a third party content provider that obtains the symbols from other third party contributors. All use of these Symbols is AT YOUR OWN RISK. "

This is great news. My last few web projects have all been based on Firebase because I focus on the front-end these days and I don't have to worry about scaling, databases, API endpoints and other nonsense which consumes a lot of my day. The pain of even getting a VPS deployed with support for Node.js, database and then figuring out some kind of redundancy to keep Node and my database running can also consume your day.

I used to favour Node.js for my REST API backend, but you can't beat the pricing for Firebase and generous free tier. One of the lesser known features is the cloud configuration service which gives you an SDK, it allows me to remotely turn settings on and off, syndicating them in realtime across all devices.

Oh, and the authentication functionality that Firebase offers with the painless SDK is absolutely fantastic. It's crazy easy to add Google/Facebook login functionality to my application and not worry about dealing with the pain of JSON Web Tokens, oAuth authentication and the other pain points of integrating social login. Implementing authentication used to be painful, fortunately services like Auth0 and Firebase are making it easier.

To those wondering who would use Firebase, I am a prime example. I am a front-end developer, but I come from a full-stack background. As I focus on the front-end, I've lost interest in configuring API's and backends, so Firebase handling this for me without needing to really do anything is a huge plus. I have no want, need or desire to ever touch a backend if I can avoid it.

For prototyping, you can't beat Firebase's cloud hosted database which utilises a JSON format to store data aka NoSQL without the scaling pain like MongoDB inflicted upon us. The rules engine that sits ontop of it allows you to configure it however you want, support for indexes and more.

Makes me happy to see that Google is doubling down on Firebase, it truly is a great product and I would be sad to see it discontinued.