sebag1507
Very impressive, congrats, and thank you for being a Firebase user!
Let us know what we should add to our MCP server.
You can reach out to me on X at sgnagnarella@ or post in our UserVoice forum:
https://firebase.uservoice.com/forums/948424-general
Cheers
Congratulations Mayank, this is very cool! I'd love to learn more about your journey building this platfrom.
One of the advantages we offer is ease of use backed up by GCP scale, reliability, and wide variety of additional products.
For example if you use Firestone and Cloud Functions with Firebase, you will still see your instances in GCP.
In that sense Amplify offers a similar experience but a higher complexity and a smaller community.
Realtime Database (RTDB) client update latency (in ideal situations) is below 100ms (blazing fast). You could absolutely track the state of the game in RTDB (e.g. players' position, artifacts, etc). You do that using the RTDB SDK and all clients listening to the same document will get updated.
For time dependant events (like bombs) you can use scheduled functions : https://firebase.google.com/docs/functions/schedule-function...
The client setting the bomb calls the function, the function updates RTDB with the location of the bomb and schedules the explosion. 10s later it updates RTDB with the explosion happening.
My 2c
You can see the size of each bundle in here: https://firebase.google.com/docs/web/sdk-metrics
Hey I recommend checking Firebase and our support for Web Frameworks.
"Firebase Hosting integrates with popular modern web frameworks including Angular and Next.js. Using Firebase Hosting and Cloud Functions for Firebase with these frameworks, you can develop apps and microservices in your preferred framework environment, and then deploy them in a managed, secure server environment. "
https://firebase.google.com/docs/hosting/frameworks-overview
- https://blog.google/products/android/earthquake-detection-an...
https://blog.google/products/android/earthquake-detection-an...
https://www.theverge.com/2021/4/28/22407676/google-expands-a...
Support during this early preview includes the following functionality: - Deploy Web apps comprised of static web content - Deploy Web apps that use pre-rendering / Static Site Generation (SSG) - Deploy Web apps that use server-side Rendering (SSR)—full server rendering on demand
Cheers,
I appreciate the concern though :).
First and foremost I appreciate the time you spent putting together the article. Feedback is a gift and always welcome.
I'll address your main point: Firebase and GCP.
Over the past decade, developers have consistently turned to Firebase as the fastest way to take their idea to market, thanks to an innovative client-first model and a singular focus on developer experience. Our goal is to provide a comprehensive and "opinionated" platform that just works, saving considerable development and maintenance time.
We consciously build some of our services on top of GCP primitives like Cloud Storage and Cloud Functions. This allows us to best apply our team in continuing with our mission, while also making sure that our users never outgrow the platform in any dimension (security, scalability, compliance, etc).
You bring up excellent points as far as our UX and better integration opportunities. My goal is not to necessarily push developers to GCP. The way I see it is that both platforms serve users with different use cases and preferences. Some will use one over the other, and many will use both.
I would love to continue the conversation and I hope you don’t mind if I try to reach out.