Full reviewBuilt with
Android Studio
The engineering environment behind real Android capture, offline queueing, widgets, sharing, and secure settings.
Essential for native Android systems; unnecessary for lightweight prototypes.Read the profile →Category field guide
Development & infrastructure
The code, backend, source-control, and deployment tools behind real Android, web, and AI product work.
- Tools covered
- 6
- Full reviews
- 1
- Field notes
- 5
My position
How I decide what belongs in this layer
Android Studio, VS Code, Supabase, Firebase, GitHub, and Vercel are where an AI idea becomes accountable to identity, state, releases, and users. They are not supporting logos; they determine whether a workflow can survive offline behavior, configuration drift, a bad deploy, or a handoff to another operator.
I evaluate development tools at the system boundary: what they make easy, what they hide, how they fail, and whether the resulting product can be inspected and recovered without relying on the original builder's memory.
The working set
6 tools, with the evidence level visible.
A field-note label is not a downgrade or a placeholder. It is the honest boundary between useful experience and a completed repeatable review.
Field notesDevelopment workflow
Visual Studio Code
The flexible code and repository workbench in my web, automation, and product implementation workflow.
A dependable center for mixed-language project work; extensions and AI assistance only help when the repository stays understandable without them.Read the profile →Field notesBuilt and evaluated with
Supabase
A Postgres-centered backend option for authentication, structured data, storage, and application services with a relatively direct data model.
Strong when SQL visibility and a conventional relational core matter; row-level security and backend boundaries still require deliberate engineering.Read the profile →Field notesBuilt and evaluated with
Firebase
Google's application backend stack for authentication, data, storage, messaging, analytics, and Android-oriented product development.
A natural fit for many Google and Android products; convenience can hide data-shape, rules, cost, and portability decisions.Read the profile →Field notesProduction operations
GitHub
The source-of-truth and collaboration layer for code, review, issues, branches, automation, and release evidence.
Essential when the repository is treated as an accountable operating record; dangerous when automation is granted broad access without isolation.Read the profile →Field notesProduction operations
Vercel
A web deployment and preview platform used to turn a repository state into a reviewable or production application.
Excellent for fast web delivery and preview workflows when project, repository, domain, and environment boundaries are kept explicit.Read the profile →Selection rules
The rules I use before adding another tool.
A product that can be tested, shipped, observed, and recovered—not just demonstrated.
- 01Model identity and data before choosing a backend.
- 02Persist user intent before remote delivery.
- 03Keep secrets outside distributable clients.
- 04Tie releases to reproducible evidence.