I'm a big fan of Firebase and have seen a lot of projects get up and running very quickly and scale as well.
However, I think there are an increasing amount of reasons why you want to have your data stored in a SQL database that you can access. The open source tooling being built around SQL (usually Postgres) as a standard is becoming better and better and it's going to be hard for Firebase to compete with all those offerings. If I run a Postgres database I can instantly have tools like Hasura [0], Metabase [1] along with others that add a ton of value out of the box. However, maybe those tools will also integrate with Firebase.
Anyway, my point is that this is best of both worlds, so great to see!
Client side apps still have a hard time being crawled by bots. You're right that the situation is getting better, but from my research it seems it's hard to crack completely without a pre-rendering solution.
And yea, search engines don't like cloaking, but google themselves say that dynamic rendering is OK and not considered cloaking.
Yea especially when you're using things like https://github.com/nfl/react-helmet to set meta tags in JS --it's not going to work unless you're using something like this. The descriptions and titles for our pages started showing up in google after implementing dynamic rendering, and our rankings seemed improved as well.
The idea for Renderproxy came to me while at work. Our website is completely written in React and was having some SEO issues. Single Page Apps have a hard time being crawled by search engine bots, and one way to fix this is to implement dynamic rendering (https://developers.google.com/search/docs/guides/dynamic-ren...), such that bots get served up a pre-rendered version of your site. Google recommends this.
Looking online, I was hoping to find something like Renderproxy, but all the solutions I found required me to run my own server, or switch hosting providers. We ended up implementing our own custom solution.
With this solution, all you need to do is sign up for Renderproxy, and change your DNS settings.
0x v3 is now live on the Ethereum mainnet. This includes the new stake-based liquidity incentives intended to empower 0x market makers and token holders.
However, I think there are an increasing amount of reasons why you want to have your data stored in a SQL database that you can access. The open source tooling being built around SQL (usually Postgres) as a standard is becoming better and better and it's going to be hard for Firebase to compete with all those offerings. If I run a Postgres database I can instantly have tools like Hasura [0], Metabase [1] along with others that add a ton of value out of the box. However, maybe those tools will also integrate with Firebase.
Anyway, my point is that this is best of both worlds, so great to see!
[0] https://github.com/hasura/graphql-engine [1] https://www.metabase.com/