Core Web Vitals (CLS and LCP) errors for a client-rendered Single Page Application (built with React + Firebase)

I have a SPA (single page website) build with React + Firebase and I’ve been getting these Core Web Vitals errors (see images below).

My website is loading normally both on Desktop and Mobile. And I think it’s rendering in a very reasonable time. At least I think it’s way faster than most websites I visit, even though it’s client side rendered.

I’m guessing these errors on Core Web Vitals are being triggered because there’s a Spinner that runs while the app is loading its data.

For example: that report is probably measuring the Spinner vs Loaded content as layout shift. Because I can guarantee that my app has ZERO layout shift. Once the Spinner is gone and you see content on your screen, the app is 100% ready for you to browse and interact with.

Maybe to get rid of those errors I would have to do SSR + hydration, which I really don’t want to, because it’s a dynamic website and I would have to either remove caching completely, or to risk a content (state vs fresh) flickering on the screen once it’s fully hydrated.

Should I care about these results? Is anybody that also manages a SPA also getting these kind of errors? Is there a way to fix this?

Found some related articles:


enter image description here

enter image description here

How to integrate Firebase to Libgdx?

I have an android game built with libgdx and what I’d like to do is to add some kind of authentication so I can connect the game with user data to firebase database.

I have some experience with firebase using it in native android apps, but I have no idea on how to connect "native code" with libgdx.

Researching I found these third party libs and

But as it does not provide any example it didn’t help me much.

So what’s the best way to "mix" native android code and libgdx? I want to be able to achieve things like storing data on db, implementing in-app-purchases, authenticating users. If I’m looking the wrong way please let me know too.

How can I design a magical weapon that grants an advantage against fire-base creatures without using water and choking effects?

The party I am DM’ing is going for an adventure to the Elemental Plane of Fire. I want to design a magical weapon that can grant an advantage against fire-based creatures. I see that Fire Elementals have Water Susceptibility (Cold Damage) but I have already house-ruled that elemental planes can not include magical effects of elements from other elemental planes, but just the spells that have elements of the current plane can be cast (as the plane purely consists of element of itself). For example, in the Elemental Plane of Air, not only Earth-based spells but all the spells are impeded, except air-based ones.

After I realized that I can’t use a magical weapon that has cold damage due to my house-rule, I wanted to give the weapon a "heavy smoke" effect to choke the fire, as I thought that fire can not live without oxygen. But this option conflicts with my house-rule, also I saw that the fire-based creatures any other fire source in the Elemental Plane of Fire don’t need air to live.

Now I have no idea how can I design a magical weapon that gives an advantage against fire-based creatures without cold damage and choking the fire via leaving without oxygen is not an option. I can not cancel my house-ruling because of the sake of my setting. I am open to any house ruling ideas beside the official ruling.

TLDR: as in title, how can I design a magical weapon that grants an advantage against fire-base creatures without using water and choking effects?

If the question shows up to be opinion-based, please accept my apologies.

is it possible for a user to get the firebase auth token from a released app?

Under the constraints that the user only has access to a release (signed) build of the android app and doesn’t know the signing key. No rooted phone either. The token isn’t sent through insecure channels (like http). User only uses default https certificates. The token is not exposed in any way through the user interface.

I am almost sure it is impossible (or at least very very hard), but I want to be sure asking you guys

Reuse Firebase Token for other authentication purporses

I’m building an app where the users should have restricted access to certain api-services. I use gRPC as API. Right now I’m asking the user’s mobile number, send him an SMS with a code which he has to verify. If it’s the same, the backend generates an UUID which will be sent to the user and safed in a local database on the mobile phone. The user is then able to authenticate itself on the backend by just sending the UUID.

While I’m in that process I noticed that the Firebase Token also never changes so I have two unique id’s which are saved in the database.

Is it safe to skip the generation of an extra UUID and verify the user by it’s Firebase Token/UID, only? The client could send the verification code with the Firebase Token and if the Firebase Token is correct, the backend will save this token to the database. The client can then authorize itself with that token. Or do I miss a point here?

Freelancer has access to Firebase Database. What should I do?

Back in November, I put up a $ 100 bounty on a freelancer website for anybody who could debug a bug I had found in my app I was developing and couldn’t squash. It turns out the freelancer was in no position to work for me. He had lied about being Danish (he was actually from northeastern China and had such a poor internet connection, he could barely run my app). Furthermore, his English was far worse than any freelancer I had worked with previously, you cannot even hold a conversation with him.

Anyways, I want to redact my $ 100 that I staged up for him, but I’m afraid of him vandalizing my database as an act of retaliation. He has cloned my project from Github, including the GoogleService-Info.plist file that would allow him to make changes to my backend.

My project is still in Beta, but is slated to go public next month. Should I just generate a new GoogleService-Info.plist file and force all current beta users to update their version (the previous version will be unusable) or should I just go with it and hope the freelancer doesn’t destroy everything I have?

PS: Sorry, this may not be the correct StackExchange site for this question. I am a seasoned Stack Overflow user and know it wouldn’t be appropriate there. If somebody points me to a better site, I will gladly move the question.

Hay alguna diferencia entre guardar data en firebase desde un componente hijo y hacerla desde un componente padre?

En mi código puedo caragar datos en firebase desde el componente padre, pero hago el mismo procedimiento desde un componente hijo y no funciona. Debo incluir ‘$ emit’ o algo así? No encuentro documentación al respecto y no encuentro el por qué no funciona.

tengo problema para generar una notificacion de tema con firebase en android studio

tengo problema para generar un mensaje de tema me estoy guiando de el documento den github de google link, ya lo suscribo pero nocuando le doy al boton que genera la notificacion me lanza un mensaje, pero no entiendo que debo hacer, copie y pegue y esta exactamente como esta en el link (las 3 clases exactamente igual), pero no entiendo ese mensaje, creo que debo ingresar la clave del servidor pero no se en donde debo hacerlo, alguna sgerencia para solucionar esto gracias. mensaje de respuesta

y otra duda que tengo es ¿cuales son las variables para cambiar el titulo y el mensaje de la notificacion?

puedo usar una sola realtime database de firebase con varias aplicaciones android?

Voy a empezar un proyecto que consta de 3 apps las mismas están relacionadas entre si , es decir necesitan acceder a los mismos datos, he buscado en la documentación de firebase y no pude encontrar si puedo conectar estas tres app y quiza una pagina web a la misma base de datos en firebase o como hacerlo