Flutter Developer

Have you shipped one Flutter codebase to both stores and dealt with whatever App Store review sent back? Can you look at an overflow error and know which constraint caused it before you add an Expanded? Do you check what a widget rebuilds before you add setState?

Then, our Flutter Developer role here at CUBE84 may interest you.

1. One codebase, two platforms You’ll build and ship Flutter apps for Android and iOS. You’ll turn Figma designs into layouts that hold up on a small Android phone, a large iPhone, and a user who has set text to 200%.

2. Plan the build first Before you build a feature, you’ll write a low-level design for it. You’ll keep network code out of the UI, use a clean repository layer, and pick a state management approach you can explain.

3. Plan for failures, not just success You’ll integrate REST APIs and handle authentication and token refresh. You’ll design the error, empty, and loading states, not just the happy path. Some projects connect to Salesforce through REST APIs and OAuth 2.0, and you’ll handle those too.

4. It still works on a weak signal You’ll handle local storage, caching, and offline behavior, so the app stays usable on patchy 3G in a basement clinic.

5. You own the release You’ll set up and maintain builds, signing, flavors, and releases to the Play Console and App Store Connect. When a rejection comes in, you’ll read it, fix it, and resubmit.

6. Keep it at 60fps You’ll use Flutter DevTools to find and fix jank, extra rebuilds, and memory leaks. You’ll write unit, widget, and integration tests so the next change doesn’t quietly break the last one.

7. The team gets better around you You’ll review pull requests and mentor junior developers. You’ll estimate your own work and raise risks early. You’ll work with QA, project managers, and clients through UAT and release.

• Have 3 to 5 years of professional mobile development, with at least 2 years hands-on in Flutter and Dart

• Know Dart 3 well: sound null safety, futures and streams, async and await, error handling, and when to move work to an isolate

• Understand the widget tree: stateless versus stateful, the widget lifecycle, keys, const constructors, and what actually triggers a rebuild

• Can work through tricky layouts with Row, Column, Flex, Stack, slivers, and constraints, and debug an overflow or an unbounded height error

• Have used one state management approach (Bloc or Cubit, Riverpod, or Provider) in production, and can explain why you chose it

• Handle navigation with go_router or Navigator 2.0, including nested routes, guards, and deep links

• Build API layers with dio or http, handle JSON with json_serializable or freezed, and use a repository pattern

• Use Hive, Isar, sqflite, or shared_preferences for local data, and secure storage for tokens

• Have used Firebase in production: Auth, Cloud Messaging, Crashlytics, and Analytics

• Write platform channels, and know enough Kotlin or Swift to read native code and wire up a plugin

• Have taken at least one app through review on both the Play Store and the App Store, including signing, provisioning profiles, versioning, and fixing a rejection (this one’s non-negotiable)

• Test with flutter_test and mocktail, and have widget tests running in CI

• Work with Git feature branches, pull requests, and code reviews as part of your daily routine

• Write and speak clear English with clients and teammates

• Salesforce REST APIs, OAuth 2.0 flows, or Experience Cloud

• Built offline-first apps with sync and conflict handling

• Mobile CI/CD with Codemagic, GitHub Actions, Bitrise, or Fastlane

• Custom animations with AnimationController, Tween, Hero, and custom painters

• Accessibility, localization, and right-to-left support

• Flutter web or desktop

• Built LLM features (OpenAI, Claude, Gemini) into a product

• Some React or Node.js (our team includes web developers)

• A published app or a public repo you can walk us through