SShortSingh.
Back to feed

Firebase Studio Adds Figma Import, Image Swaps, and Automated Backend Setup

0
·13 views

Google announced new Firebase updates at I/O 2025, focused on helping developers build full-stack AI applications from one place. Firebase Studio, the cloud-based AI workspace previewed at Cloud Next, now lets users import Figma designs via a Builder.io plugin and use Gemini to add screens or connect user flows through chat. The App Prototyping agent can also replace placeholder images with visuals from Unsplash and detect and provision backend services such as databases and authentication. Google says the workspace has already seen over 1.5 million creations in just over a month and is now powered by Gemini 2.5. The article is a developer-focused implementation guide, and it notes that Vertex AI in Firebase has since been renamed Firebase AI Logic.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Seven Self-Hosted Jira Alternatives Compared on Migration, Deployment and Workflow Fit

Replacing Jira can affect more than ticket tracking, since projects often rely on long-standing history, workflows, and reporting routines. This guide evaluates seven self-hosted options using four criteria: deployment fit, project and agile coverage, workflow and reporting flexibility, and migration effort. A comparison table lists each tool's best use case, deployment options, AI agent readiness, pricing, and free plan availability. ONES.com is highlighted for teams that need a structured Jira data migration path, with documented mapping of issue types, fields, and users. Other options named include Jira Data Center, GitLab, Redmine, Taiga, Tuleap, and Trac, each suited to different team needs.

0
ProgrammingDEV Community ·

cAdvisor Monitor Found on 13,948 Internet-Facing Hosts on Port 8080

A search-index analysis of cAdvisor, a container resource monitor usually installed alongside Kubernetes, counted 134,520 pages with a loose title match and 13,948 that also answered on port 8080. The researchers found that strict title and application queries returned no results, because the tool has no standard product fingerprint for classification. cAdvisor exposes container names, image names, volume paths, labels, and process details, along with a debug profiling endpoint enabled by default unless disabled. The findings indicate how common the deployment is but do not establish whether these listeners are reachable beyond the scanner's vantage point. The analysis recommends reviewing bind addresses, authentication, and profiling settings for such deployments.

0
ProgrammingDEV Community ·

Radar directory aims to help users discover websites through category browsing

The author, who runs the web directory Radar, argues that search engines work well only when users already know what they are looking for. When people want to explore unfamiliar tools, communities, or services, they often cannot form a useful query at all. To address this, Radar separates Search for finding known sites from Discovery for uncovering new options. The platform organizes websites by category, letting visitors pick a field, compare alternatives, and then visit the site they need. The author stresses that browsing complements rather than competes with search, and that it helps users see choices beyond the same few sites that keep appearing in results.

0
ProgrammingDEV Community ·

Owe: Gemma 4 drafts replies to avoided messages, with a local check on sending

Owe is an open-source tool that takes a message the user has been avoiding and uses Gemma 4 through the Gemini API to draft a reply of at most 60 words. The model also names the one fact it must not invent and indicates whether the reply can be sent. A local script then checks the draft for word count and for any numbers, emails, or names absent from the original message or user note, and can block sending. Without a user decision, the tool produced a short holding reply, and with a note it produced a reply matching that decision. The message text goes to the Gemini API, so the tool does not work offline, though the final send decision stays on the user's machine.