Android engineering company
Legacy, Play, OEM, hard integrations. We build and rescue native Android systems with written scope, milestones and quality criteria, and one senior engineer accountable for the result. Scope locked before we start.Legacy, Play, OEM, hard integrations. Scope locked before we start.
Credentials
10 Google Android Enterprise credentials, Associate to Expert, since 2020. In practice: OEM behavior, background and battery, Play policy, purpose-built hardware and sensitive permission flows. Few teams reach this layer. That is where a stable product separates from a polished demo.
Services/ 01
Store policy, device behavior, security and architecture. Those are the points where mobile projects fail quietly, months before anyone notices. That is the work we take on.
Kotlin, Compose, app architecture, release hardening and technical direction for products that need more than screens. That includes items that rarely appear in estimates: Play policy and target API migrations, OEM battery and background behavior, and devices that ship without Google Play Services.
Real-time experiences, WebRTC, sensors, vendor SDKs, permission models and secure data flows. These are the parts that tend to break only in the field, on a device outside the test plan.
Modernize a legacy Android codebase, clear a compliance backlog, or bring senior architecture into a team that's already moving. One technical standard for the whole engagement. AI accelerates the work; it never replaces senior review.
Process/ 02
The same four stages on every project, each one ending in something you can read, review or run. Scope changes are written down before the work starts, never after.
We map goals, constraints, risks and what has to be true in production. You get a written summary of what we found, including the problems you didn't ask about.
A written proposal: architecture direction, milestones, acceptance criteria and quality criteria. What's out of scope is stated as clearly as what's in. You approve before anything starts.
Short cycles with senior review on every change, CI running from the first week, and a build you can install at the end of each one. Progress you can run, not a percentage on a slide.
We close with architecture documentation, recorded decisions and a walkthrough with your engineers. Everything organized so the team can take over product evolution.
Why Levandowski/ 03
Every hour of experience compounds on one platform. That applies both when we rescue a system in production and when we set architecture for a product still taking shape. Device behavior, store policy, security and fragmentation are problems we have already solved, not topics to research on your budget.
When the Android product carries real operational weight: revenue running through it, devices in the field, a store deadline, or a codebase the team avoids maintaining. Or a new product that needs architecture and technical direction from day one. For a simple app with no platform complexity, a generalist team will serve you well and cost less. We state that clearly.
Founders, engineering and product leaders on LinkedIn. Google Android Enterprise certifications. We work on platforms with fleets in the millions.
References/ 04
Written by founders, engineering and product leaders who worked with Gustavo Levandowski. Quoted as written.
Gustavo is extremely proactive. He is the kind of professional big companies want: committed to deliveries, with an owner mentality.
At Pulsus I saw solid technical knowledge and ownership. His code reviews raise the bar for the whole codebase.
High-quality developer: organized, clean code, leadership and an entrepreneurial eye.
Some workplaces, some linked through people who recommend the work
Engagement model/ 06
Scope, milestones and acceptance criteria agreed before the first line of code. Intellectual property in the deliverable stays with you under the contract. Third-party licenses listed explicitly. We invoice as a legal entity, ready for procurement and legal review in Brazil or abroad.
We split the project into milestones with criteria set up front. Each stage is reviewed and approved before the next starts. You decide whether to continue based on what was delivered.
We document the transfer while context is still fresh. Repository, CI and accounts stay in your environment whenever possible. When we finish, your team can operate and extend the system on its own.
Gustavo Levandowski founded Levandowski and leads the engineering end to end. Google Android Enterprise Expert, with a track record in native Android, platform work and products at scale. The company for the contract. A named senior for execution.
The company to hire. The founder to deliver.
Ecosystem One codebase, one architecture, wherever Android runs.
FAQ/ 08
Who we are and when to hire.
What we build and how far we go.
How work starts, runs and stays owned.
IP, confidentiality and how we work internationally.
Contact/ 09
A short brief, then a discovery call. You leave with a written proposal: milestones, quality criteria and a named technical owner.
Credentials
