Cloud saving is now fully integrated into the application, making it possible to permanently persist data on the phone and now even cross-link progress between different platforms. 

I was motivated to tackle this herculean task because I found that no matter my best efforts, there was no way to guarantee the persistence of saved data on the phone locally. It would still always get wiped away eventually by bad timing or bad luck. So I looked to the skies and spent 30+ hours learning and working from scratch and user-made plugins to integrate the saving to a Firebase cloud. 

Saving was frankly the easy part. It was the loading that was killing me. A variety of roadblocks kept cropping up. Let me paint you a long tale of stumbles.

- At first I was using gmail to authenticate the data retrieval, but the program didn't work on desktops, only web

- Then I fixed it to do both, but it turns out the HTML5 frames in Godot don't allow opening tabs within frame, so no gmail.

- So I had it open a new tab for the authentication, and then return to the page after, but turns out the frames in Godot can't access the URL of the website, only of the iframe itself

- So I started using the iframe's URL for authentication, and found out that uploading new versions also changes the URL, therefore invalidating the authorization since it has to be a static, trusted URL

- So I scrapped 200+ lines of code and all those hours of my life to step back and try again, this time using Firebase's email system directly for authorization

- This required designing a whole new UI to handle syncing, signing up, signing in, handling errors, and logging in.

- It worked! On Desktop! On ich.io!

- Wait, what's this

- Wait on mobile, HTML5 files can't use the phone's keyboard to type stuff in? So you can't even type in your email?

- Why is this a thing

- What

- That's so stupid

- No no no I'm not losing to a phone, I've gone too far to lose now

- Why are there no viable workarounds for this. 

- Why is this the oddly specific issue that kills the mobile usage? Is there seriously no other way?

- Wait, I have an idea

So anyway that's why you see a janky keyboard on screen when loading in on mobile. I'll patch that up, and a few other visual bugs that cropped up with the UI, at a later point. For now, please enjoy this nuclear and option and any feedback is appreciated!