Firebase Blog

On-device models seems like a good approach to this. Especially if it's silly projects they probably don't need the latest and greatest expensive models. Firebase recently launch some experimental on-device APIs. https://firebase.blog/posts/2025/06/hybrid-inference-firebase-ai-logic

Firebase was such a terrible loss. I had been following it quite closely on its mailing list until the Google takeover, then it seemed like progress slowed to a halt. Also having big brother watching a common bootstrap framework's data like that, used by countless MVP apps, doesn't exactly inspire confidence, but that's of course why they bought it. At the time, the most requested feature was a push notification mechanism, because implementing that on iOS had a steep learning curve and was not cross-platform. Then probably some more advanced rules to be able to do more functional-style permissions, possibly with variables, although they had just rolled out an upgraded rules syntax. And also having a symlink metaphor for nodes might have been nice, so that subtrees could reflect changes to others like a spreadsheet, for auto-normalization without duplicate logic. And they hadn't yet implemented an incremental/diff mechanism to only download what's needed at app startup, so larger databases could be slow to load. I don't remember if writes were durable enough to survive driving through a tunnel and relaunching the app while disconnected from the internet either. I'm going from memory and am surely forgetting something. Does anyone know if any/all of the issues have been implemented/fixed yet? I'd bet money that the more obvious ones from a first-principles approach have not, because ensh!ttification. Nobody's at the wheel to implement these things, and of course there's no…

How does the element copying work? > Copy the designs of your favorite websites, frameworks, or themes. Extract the HTML and CSS code of an element and all its children in seconds. > Not the right element you're looking for? Precisely re-target any DOM element using your keyboard's arrow keys (▲ ▼). The documentation talks about it a little bit but not much. I am wondering if this feature is another cheapskate implementation that doesn't actually do what it says it does. How for example would this tool handle the Firebase[0] featured header? The other features look OK, but I don't think I could justify the price though. If you want to charge for it so much, maybe change your pricing to a yearly license and then do updates, and simply restrict new updates to people who stop subscribing. Seems like a lot more reasonable approach and it also gives you a chance to really work on extending this product beyond what it currently does. [0]: https://firebase.blog/posts/2023/05/whats-new-at-google-io

But, why do they launch Firebase Studio (https://firebase.blog/posts/2025/04/introducing-firebase-studio/) on the same day? I wonder if this is a timed.

The first time I heard about ordered string IDs was Firebase’s push IDs. They had an interesting solution to also address time skew to get better ordering for drivers: https://firebase.blog/posts/2015/02/the-2120-ways-to-ensure-unique_68/