Mobile Engineer & Flutter Consultant
Chandra Abdul Fattah
I help teams build reliable Flutter applications, connect native Android and iOS capabilities, and improve mobile architecture. My work spans Staff Engineering at Evermos, mobile leadership at TechLab Security, and freelance engineering with Cloud Creatures.
ENGINEERING EXPERIENCE & COLLABORATIONS
Selected work
Selected work covering the problem, my role, the technical decisions, and the evidence available to review.
Architecture · quality · technical direction
Growing with a mobile platform from feature work to technical direction — architecture, engineering effectiveness, and the decisions that outlive any single release.
Android usage monitoring and app restrictions, with an iOS permission bridge — a Flutter plugin case study in making platform boundaries explicit.
Read the case study: Building Screen Time Capabilities in Flutter
$ dart run package_rename_plus
Configure → build → release
Android · iOS · Web · Desktop
Building the tools that shorten a team's feedback loop — release configuration, in-app event inspection, and network debugging — and why each one started as a repeated manual step.
What I do
Practical support for the decisions, integrations, and production issues that slow mobile teams down.
Build a mobile application from architecture and module design through implementation, API integration, testing, and release preparation.
Flutter · Android · iOS · REST · GraphQL
Improve growing codebases through modularization, clearer dependencies, and focused refactoring of the areas that slow delivery.
Architecture · Modularization · Refactoring
The work that starts where Dart ends: platform channels, Android and iOS SDKs, Kotlin and Swift implementations, and the lifecycle details that only surface in production.
Flutter · Kotlin · Swift · Platform Channels
Developer-facing libraries where the API is the product — designing a surface other engineers can use correctly without reading the source, then publishing and maintaining it.
Dart · pub.dev · API Design · Versioning
Crashes that only reproduce on one OS version, performance cliffs, lifecycle and state bugs, networking edge cases. Diagnosis first, then a fix at the root rather than the symptom.
Profiling · Crash Analysis · State Management
Tooling, automation, and CLI workflows that shorten the loop between writing code and knowing whether it works — including where AI agents genuinely help.
CLI Tooling · CI/CD · Automation
Expertise
Shipping and maintaining mobile products that stay maintainable under continuous change.
Application architecture, state management, and performance in production Flutter apps.
The boundary between Dart and the platform, where cross-platform stops being free.
Libraries where other engineers are the users, and the API surface is the product.
Open source
Packages, plugins, and upstream contributions — published, versioned, and used by other engineers.
A Flutter plugin for Android app-usage statistics and foreground-app monitoring, with native permission and accessibility-service integration.
Screen Time is an operating system capability with no Dart surface at all. Android exposes it through UsageStatsManager, AppOpsManager, and an AccessibilityService; iOS through the FamilyControls framework. Nothing about the two designs lines up.
A maintained fork of Package Rename that configures Flutter bundle identifiers, app names, and platform metadata, including fixes for iOS extension targets.
Renaming a Flutter app by hand means editing Gradle, Info.plist, manifests, and web/desktop config by hand, and missing one silently breaks a release build.
A togglable in-app overlay listing background events as they fire — analytics, network calls, or any logged stream — in debug builds.
Verifying analytics normally means tailing a console on a connected device. Putting the event stream on the screen makes tracking bugs visible to QA and product, not just to engineers.
Upstream contributions to the Flutter SDK for GrowthBook, an open-source feature flagging and experimentation platform.
Feature flags and A/B tests need a client SDK that evaluates consistently with the rest of the platform. This brings Flutter into an ecosystem that already had web and backend support.
AI-Augmented Engineering
I use AI coding agents throughout research, implementation, debugging, testing, review, documentation, and automation — while keeping architecture decisions, trade-offs, and quality accountable to engineering judgment.
Understand the product and its constraints. Read the code and documentation, trace the flow, and reproduce the problem.
Agree on scope, compare technical options, and document the trade-offs behind the chosen approach.
Write the smallest change that solves the real problem, in the style of the code around it.
Verify critical behavior and failure cases with tests that catch regressions and support safe releases.
Review correctness, maintainability, and risk. I remain responsible for the work, including changes assisted by AI.
Prepare the release, rollout, monitoring, and recovery steps with the team.
Feed what the production system taught back into the architecture and the tooling.
Recommendations
Summaries of recommendations received on LinkedIn. Each recommendation is linked to its original source.
Recommendation summary
Cevin highlights Chandra’s problem-solving ability and the confidence he brought to tackling challenges together on the mobile team.
Recommendation summary
Dwi credits Chandra’s early Flutter architecture and modularization work at Evermos, and describes how their collaboration helped him grow as an engineer.
Recommendation summary
Syamsu recognizes Chandra’s discipline, ability to learn quickly, time management, prioritization, and leadership potential.
About
I started building software in 2014, moved into native Android in 2017, and adopted Flutter around 2019. My experience spans commerce, healthcare, and consumer applications.
Today my focus is mobile architecture, native integration, SDKs, and developer tooling. I also share that experience through open-source contributions and mentoring.
Today I work as a Staff Engineer on mobile at Evermos, and independently through Solusi Bejo.
Share your product, the technical challenge, and the outcome you need. We can discuss the scope and a practical next step.