Flutter Developer for Codebase Migration
Budget / Salary$750–1,500
TypeFreelance project
LocationRemote
Posted1 hour ago
# Full-Time Flutter Developer
**Existing Codebase Migration + New Architecture Ownership**
**Remote | 2–3 Years of Experience | $1,300–$1,500 Per Month**
Most Flutter developers can assemble screens, connect an API, and produce something that technically launches.
That is not the assignment.
Production Connections is hiring a **full-time Flutter Developer** who can enter an existing application, understand code they did not write, identify what actually matters, transfer the required functionality into a new architecture, and then take ownership of the new codebase.
This is a long-term position.
Not a temporary migration contract. Not a small feature project. Not something you squeeze between five other clients while pretending to be full-time.
The old application already contains business logic and functionality we need.
The new codebase is where the product is going.
Your responsibility is to connect those two realities without dragging unnecessary technical debt into the future.
## Position Details
**Company:** Production Connections
**Employment Type:** Full-Time
**Experience Required:** 2–3 Years
**Compensation:** $1,300–$1,500 per month, based on technical ability and experience
**Working Hours:** 8:00 AM–5:00 PM U.S. Eastern Time
**Location:** Remote
**Platform:** Freelancer.com
## Your Primary Assignment
You will take responsibility for a controlled transition from an existing Flutter application into a new codebase and architecture.
That means you must be able to:
**Understand the old codebase.**
**Extract the functionality that matters.**
**Rebuild or refactor what should not be copied.**
**Protect existing application behavior.**
**Become highly productive inside the new architecture.**
Copying files from one project into another is not migration.
A successful transition requires technical judgment.
## Existing Codebase Responsibilities
* Analyze the existing Flutter application, architecture, dependencies, business logic, data flows, and functionality
* Understand unfamiliar code without requiring the original developer to explain every decision
* Identify which features, services, models, integrations, and workflows must be transferred
* Separate required functionality from obsolete code, duplication, workarounds, and technical debt
* Transfer viable functionality into the new codebase correctly
* Rebuild or refactor functionality when direct migration would weaken the new architecture
* Preserve existing business rules and expected application behavior
* Test transferred functionality and correct migration-related defects
* Prevent regressions across connected features and user workflows
* Document important migration decisions and implementation changes
* Take responsibility for the technical quality of the transition
The goal is not to preserve the old code.
The goal is to preserve the correct functionality while improving the foundation underneath it.
## New Codebase Responsibilities
* Work primarily inside the new Flutter codebase and architecture
* Learn the project structure, conventions, standards, and development patterns quickly
* Develop, rebuild, maintain, and improve Flutter applications
* Convert Figma designs into accurate, responsive Flutter interfaces
* Write clean, scalable, maintainable Dart and Flutter code
* Implement appropriate application architecture and state management
* Integrate REST APIs, authentication systems, payments, notifications, analytics, and third-party services
* Handle local storage, secure storage, session management, error states, and data synchronization
* Diagnose crashes, failed builds, dependency conflicts, rendering problems, and performance issues
* Optimize application stability, responsiveness, usability, and loading performance
* Ensure reliable behavior across Android and iOS devices
* Manage Flutter SDK, Dart packages, Gradle, CocoaPods, Xcode, and Android Studio requirements
* Collaborate with backend developers, designers, QA, and other developers
* Use Git and GitHub correctly for branches, commits, pull requests, and version control
* Prepare builds for Google Play and Apple App Store submission
* Support release testing, deployment, updates, and post-release corrections
* Build new features without weakening the architecture every time the application expands
## Required Experience
* **2–3 years of professional Flutter and Dart development experience**
* Experience developing production applications for both Android and iOS
* Strong knowledge of Flutter widgets, navigation, lifecycle management, asynchronous programming, and responsive layouts
* Experience entering and understanding existing or legacy Flutter codebases
* Experience migrating, transferring, rebuilding, or refactoring functionality between codebases
* Ability to understand unfamiliar architecture and business logic independently
* Ability to work effectively inside a new architecture rather than forcing old patterns into it
* Experience protecting existing functionality during migrations and refactors
* Experience with Bloc, Cubit, Riverpod, Provider, GetX, or comparable state-management systems
* Strong REST API and third-party integration experience
* Firebase experience
* Experience with authentication, push notifications, analytics, and application data handling
* Working knowledge of Gradle, CocoaPods, Xcode, and Android Studio
* Git and GitHub experience
* Strong debugging and root-cause analysis skills
* Clear written communication
* Reliable internet access and dependable availability
* Ability to work full-time during U.S. Eastern Time business hours
Experience with payments, real-time communications, media uploads, CRM systems, project-management platforms, or complex role-based applications is an advantage.
## The Transition Standard
The right developer should be able to manage the complete sequence.
### Old Codebase
**Understand → Analyze → Identify → Transfer → Refactor → Test**
### New Codebase
**Learn → Implement → Improve → Maintain → Expand**
You do not need to become emotionally attached to the legacy implementation.
You need to understand it well enough to preserve what works, reject what does not, and move the product forward correctly.
Your long-term value will be measured by how effectively you operate inside the **new codebase and architecture**.
## What We Are Not Looking For
Do not apply if you simply copy existing code without understanding what it does.
Do not apply if you can only work with applications you personally built from the beginning.
Do not apply if your migration strategy is to move the entire old project into a new folder and hope the problems disappear.
Do not apply if you cannot determine when functionality should be transferred, rebuilt, refactored, or abandoned.
Do not apply if you depend on someone else to diagnose every difficult issue.
Do not apply if you disappear when builds fail, dependencies conflict, or application behavior becomes complicated.
Do not apply if you are already working several full-time jobs and plan to treat this position as another background commitment.
A functioning screen is not the standard.
The application must communicate correctly with APIs, handle failures, preserve business logic, perform reliably, survive dependency updates, and work across real devices.
The old codebase must be understood.
The required functionality must be transferred correctly.
The new codebase must become the foundation for everything built afterward.
## Schedule Requirement
This position requires full-time availability from **8:00 AM to 5:00 PM U.S. Eastern Time**.
Your availability during these hours is not optional.
Apply only if you can consistently work the required schedule, communicate during working hours, and commit to a serious long-term position.
## How to Apply
Begin your proposal with the word:
**FLUTTER**
Then include the following:
1. Your total years of professional Flutter and Dart experience
2. Links to 3–5 Flutter applications you personally developed
3. A clear explanation of what you personally built on each application
4. Your experience working with existing or legacy Flutter codebases
5. One example of a codebase or functionality migration you personally handled
6. How you analyze an unfamiliar codebase before changing or transferring anything
7. How you protect existing functionality during migrations and refactors
8. How you decide whether code should be transferred, rebuilt, refactored, or discarded
9. Your experience learning and working inside a new application architecture
10. The state-management systems you have used
11. One difficult Flutter problem you personally diagnosed and corrected
12. Your experience with APIs, Firebase, payments, notifications, analytics, or third-party integrations
13. Your Android, iOS, Google Play, and Apple App Store deployment experience
14. Your current location, time zone, and availability
15. Your expected monthly compensation
16. Confirmation that you can work full-time from 8:00 AM to 5:00 PM U.S. Eastern Time
Generic applications will be ignored.
Production Connections is not hiring someone who simply knows how to build a Flutter screen.
We are hiring a developer who can understand the old system, control the migration, protect the application, and make the new architecture strong enough to carry everything that comes next.
**Existing Codebase Migration + New Architecture Ownership**
**Remote | 2–3 Years of Experience | $1,300–$1,500 Per Month**
Most Flutter developers can assemble screens, connect an API, and produce something that technically launches.
That is not the assignment.
Production Connections is hiring a **full-time Flutter Developer** who can enter an existing application, understand code they did not write, identify what actually matters, transfer the required functionality into a new architecture, and then take ownership of the new codebase.
This is a long-term position.
Not a temporary migration contract. Not a small feature project. Not something you squeeze between five other clients while pretending to be full-time.
The old application already contains business logic and functionality we need.
The new codebase is where the product is going.
Your responsibility is to connect those two realities without dragging unnecessary technical debt into the future.
## Position Details
**Company:** Production Connections
**Employment Type:** Full-Time
**Experience Required:** 2–3 Years
**Compensation:** $1,300–$1,500 per month, based on technical ability and experience
**Working Hours:** 8:00 AM–5:00 PM U.S. Eastern Time
**Location:** Remote
**Platform:** Freelancer.com
## Your Primary Assignment
You will take responsibility for a controlled transition from an existing Flutter application into a new codebase and architecture.
That means you must be able to:
**Understand the old codebase.**
**Extract the functionality that matters.**
**Rebuild or refactor what should not be copied.**
**Protect existing application behavior.**
**Become highly productive inside the new architecture.**
Copying files from one project into another is not migration.
A successful transition requires technical judgment.
## Existing Codebase Responsibilities
* Analyze the existing Flutter application, architecture, dependencies, business logic, data flows, and functionality
* Understand unfamiliar code without requiring the original developer to explain every decision
* Identify which features, services, models, integrations, and workflows must be transferred
* Separate required functionality from obsolete code, duplication, workarounds, and technical debt
* Transfer viable functionality into the new codebase correctly
* Rebuild or refactor functionality when direct migration would weaken the new architecture
* Preserve existing business rules and expected application behavior
* Test transferred functionality and correct migration-related defects
* Prevent regressions across connected features and user workflows
* Document important migration decisions and implementation changes
* Take responsibility for the technical quality of the transition
The goal is not to preserve the old code.
The goal is to preserve the correct functionality while improving the foundation underneath it.
## New Codebase Responsibilities
* Work primarily inside the new Flutter codebase and architecture
* Learn the project structure, conventions, standards, and development patterns quickly
* Develop, rebuild, maintain, and improve Flutter applications
* Convert Figma designs into accurate, responsive Flutter interfaces
* Write clean, scalable, maintainable Dart and Flutter code
* Implement appropriate application architecture and state management
* Integrate REST APIs, authentication systems, payments, notifications, analytics, and third-party services
* Handle local storage, secure storage, session management, error states, and data synchronization
* Diagnose crashes, failed builds, dependency conflicts, rendering problems, and performance issues
* Optimize application stability, responsiveness, usability, and loading performance
* Ensure reliable behavior across Android and iOS devices
* Manage Flutter SDK, Dart packages, Gradle, CocoaPods, Xcode, and Android Studio requirements
* Collaborate with backend developers, designers, QA, and other developers
* Use Git and GitHub correctly for branches, commits, pull requests, and version control
* Prepare builds for Google Play and Apple App Store submission
* Support release testing, deployment, updates, and post-release corrections
* Build new features without weakening the architecture every time the application expands
## Required Experience
* **2–3 years of professional Flutter and Dart development experience**
* Experience developing production applications for both Android and iOS
* Strong knowledge of Flutter widgets, navigation, lifecycle management, asynchronous programming, and responsive layouts
* Experience entering and understanding existing or legacy Flutter codebases
* Experience migrating, transferring, rebuilding, or refactoring functionality between codebases
* Ability to understand unfamiliar architecture and business logic independently
* Ability to work effectively inside a new architecture rather than forcing old patterns into it
* Experience protecting existing functionality during migrations and refactors
* Experience with Bloc, Cubit, Riverpod, Provider, GetX, or comparable state-management systems
* Strong REST API and third-party integration experience
* Firebase experience
* Experience with authentication, push notifications, analytics, and application data handling
* Working knowledge of Gradle, CocoaPods, Xcode, and Android Studio
* Git and GitHub experience
* Strong debugging and root-cause analysis skills
* Clear written communication
* Reliable internet access and dependable availability
* Ability to work full-time during U.S. Eastern Time business hours
Experience with payments, real-time communications, media uploads, CRM systems, project-management platforms, or complex role-based applications is an advantage.
## The Transition Standard
The right developer should be able to manage the complete sequence.
### Old Codebase
**Understand → Analyze → Identify → Transfer → Refactor → Test**
### New Codebase
**Learn → Implement → Improve → Maintain → Expand**
You do not need to become emotionally attached to the legacy implementation.
You need to understand it well enough to preserve what works, reject what does not, and move the product forward correctly.
Your long-term value will be measured by how effectively you operate inside the **new codebase and architecture**.
## What We Are Not Looking For
Do not apply if you simply copy existing code without understanding what it does.
Do not apply if you can only work with applications you personally built from the beginning.
Do not apply if your migration strategy is to move the entire old project into a new folder and hope the problems disappear.
Do not apply if you cannot determine when functionality should be transferred, rebuilt, refactored, or abandoned.
Do not apply if you depend on someone else to diagnose every difficult issue.
Do not apply if you disappear when builds fail, dependencies conflict, or application behavior becomes complicated.
Do not apply if you are already working several full-time jobs and plan to treat this position as another background commitment.
A functioning screen is not the standard.
The application must communicate correctly with APIs, handle failures, preserve business logic, perform reliably, survive dependency updates, and work across real devices.
The old codebase must be understood.
The required functionality must be transferred correctly.
The new codebase must become the foundation for everything built afterward.
## Schedule Requirement
This position requires full-time availability from **8:00 AM to 5:00 PM U.S. Eastern Time**.
Your availability during these hours is not optional.
Apply only if you can consistently work the required schedule, communicate during working hours, and commit to a serious long-term position.
## How to Apply
Begin your proposal with the word:
**FLUTTER**
Then include the following:
1. Your total years of professional Flutter and Dart experience
2. Links to 3–5 Flutter applications you personally developed
3. A clear explanation of what you personally built on each application
4. Your experience working with existing or legacy Flutter codebases
5. One example of a codebase or functionality migration you personally handled
6. How you analyze an unfamiliar codebase before changing or transferring anything
7. How you protect existing functionality during migrations and refactors
8. How you decide whether code should be transferred, rebuilt, refactored, or discarded
9. Your experience learning and working inside a new application architecture
10. The state-management systems you have used
11. One difficult Flutter problem you personally diagnosed and corrected
12. Your experience with APIs, Firebase, payments, notifications, analytics, or third-party integrations
13. Your Android, iOS, Google Play, and Apple App Store deployment experience
14. Your current location, time zone, and availability
15. Your expected monthly compensation
16. Confirmation that you can work full-time from 8:00 AM to 5:00 PM U.S. Eastern Time
Generic applications will be ignored.
Production Connections is not hiring someone who simply knows how to build a Flutter screen.
We are hiring a developer who can understand the old system, control the migration, protect the application, and make the new architecture strong enough to carry everything that comes next.
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.