Part-Time Flutter Developer for Live IoT App

@pinkeegupta

Impeller I will be able to help you. Please message me so that we will have detail technical discussion. I have 9+ years of combined experience in Mobile Application development, Website development, Desktop application development, 3rd party Artificial Intelligence api, AR/ VR, Chatbot, Blockchain- Cryptocurrency, CRM & ERP, Game Development and any other Software development. Please consider me and initiate a chat for further detailed discussion. Regards, Anju Logical Soft Tech Pvt Ltd, Indore(M.P)

@deependra4113

Impeller I’ve reviewed the developer brief and the long-term nature of this role fits how I prefer to work: understand the existing code first, follow its patterns, and make focused changes rather than rewrite. 1. **Flutter:** I have around 1 year of hands-on Flutter experience, including production work. My stronger background is native iOS/Android, with 9+ years of mobile development overall. I’ve built Flutter functionality integrated into existing native Android/iOS applications. 2. **BLoC:** I’ve worked with BLoC/FormFieldBloc on a production ticketing workflow involving asynchronous operations, form state, API/database updates, and offline-created tickets. I structured events and states so UI state, submission status, errors, and sync results remained predictable. I would follow the existing BLoC architecture in your codebase rather than introduce another pattern. 3. **7 PM–11 PM IST:** Yes, I’m available during this window. I’m comfortable with GitHub PR-based workflows, Jira, written async communication, and working on live apps where reproduction and regression testing matter. The brief’s approach of starting with a small paid ticket also works for me. I understand the app involves long-lived connectivity state, background behaviour, subscriptions, and platform-specific differences, so I’ll be careful about changes around those areas.

@tonybhsl

Hello, We’re interested in a long-term Flutter engagement for your production IoT application. We understand that this is an established BLoC codebase, so our approach would be to read and follow the existing architecture first, make focused changes, and avoid unnecessary rewrites. 1. Flutter experience / production apps: Our team has strong Flutter development experience across Android and iOS applications. We can provide specific shipped-app details during the initial discussion based on the developer assigned to the project. 2. BLoC state-management approach: For complex asynchronous flows, we structure BLoCs around clearly separated events, states, repository/API layers and predictable loading/success/error transitions. This keeps state changes testable and prevents UI/business logic from becoming tightly coupled. 3. 7 PM–11 PM IST: Yes, we can align with the requested 7 PM–11 PM IST working window. We’re comfortable with GitHub, Jira, Basecamp and Teams, async communication, code reviews, debugging production issues, and incremental feature delivery. We’re also happy to begin with the paid trial task and build toward a long-term engagement. Best regards, Bivanshi Ohri

@Sohailzk

Hi, I’m an experienced Flutter Developer with 6 years of expertise in building high-quality, scalable Android & iOS apps. I can handle complete app development, API integration, Firebase, UI/UX, and Play Store deployment. Let’s turn your idea into a powerful, user-friendly app!

@TechizeBuilder

Dear Client, I read "Part-Time Flutter Developer for Live IoT App" carefully and understand you want a single Flutter codebase that runs smoothly on both Android and iOS. My hands-on experience with Mobile App Development, iPhone, Android, Flutter aligns directly with what you need. I've shipped Flutter apps from scratch to store launch — clean architecture, smooth animations, native-feeling UI and solid API integrations — that stay easy to maintain as features grow. A few quick questions to get us started: 1. Do you need Android, iOS, or both from day one? 2. Are UI designs ready, or should I design the screens as well? 3. Is there an existing backend/API, or should I build that too? Thanks & Regards, Deepak

@Mohammaduvez

Impeller Answer to your questions: 1. I have 5 years of Flutter experience and developed and shipped one production app including backend, there are other projects I worked on with existing live apps. 2. Updating state of elements with bloc in a collection bloc 3. Available Please contact me to discuss further and get started Thanks.

@jayantkumar314

Impeller With over 6 years of experience in the software engineering domain, I have developed a deep understanding of persisting code authenticity and integration in large projects just like yours. To be honest, this project looks like the ideal match for my skills and expertise. Flutter app development has been a central part of my work for the past couple of years, successfully delivering several production grade apps and maintaining them with utmost efficiency. As per your requirements, I'm firmly acquainted with BLoC and well-versed in GitHub, Jira, Basecamp and Microsoft Teams for seamless remote collaboration. A persuasive example of my knowledge in BLoC lies in one of my previous projects where I tackled a particularly intricate state problem by structuring it in a modular and pluggable way to ensure maintainability. Regarding availability, I can assure you 10-15 hours per week uninterrupted between 7 PM to 11 PM IST. But it's not just about the time, is it? It's about the value we can bring to your project week after week. I understand the importance of clear communication and consistent quality code delivery – two factors that have defined my professional relationships over time just like the extraordinary chemistry you seek in long-term partnerships. Let's take this opportunity to collaborate on a small paid task first so we both can evaluate how our respective talents align with the project's needs.

@MuhammadAsad108

Impeller I deliver 100% work — 99.9% is not for me. Workflow Diagram Existing BLoC Review ⟶⟶ Reproduce Issue ⟶⟶ State/Stream Trace ⟶⟶ Minimal Fix ⟶⟶ Tests ⟶⟶ Small PR ⟶⟶ CI/Review ⟶⟶ Release Validation 1. I have 6 years hands-on Flutter experience and have shipped [X] production apps across Android/iOS. 2. A difficult BLoC problem I’ve handled involved asynchronous state that had to remain consistent across screens and lifecycle changes. I separated events, transient connection states and persistent domain state, then used explicit state transitions and stream-driven updates rather than UI-owned flags. This prevents stale UI, duplicate events and race conditions while keeping behavior testable. Your brief matches how I prefer to maintain live products: read the existing architecture first, reproduce before changing code, preserve established BLoC patterns, and avoid unnecessary rewrites. For IoT issues I’ll trace device state, reconnection, API/RPC state and lifecycle transitions to isolate whether failure belongs to Flutter or backend/device behavior. 3. Yes, I can work 7 PM–11 PM IST and communicate asynchronously through GitHub, Jira, Basecamp and Teams. I’m comfortable starting with your small paid ticket. Best Regards, Asad

@jagratip3

I have 5+ years of hands-on Flutter experience and have delivered 15+ production apps across Android and iOS, including apps with real-time data, BLE integrations, background services, and subscription flows. A challenging BLoC problem I solved involved synchronizing device state, API updates, and user actions without race conditions. I used separate event streams with repository-driven state management to keep UI updates predictable, scalable, and testable while preventing duplicate state emissions. Yes, I am available between 7 PM and 11 PM IST and can commit 10–15 hours per week long-term. I’m comfortable working within established codebases, following existing patterns, and collaborating asynchronously through GitHub, Jira, Basecamp, and Teams. I’m happy to start with the paid trial task and demonstrate my approach.

@dushyant317

Impeller — We have 8 years of Flutter experience and 50 production apps shipped; our BLoC experience includes managing complex asynchronous device connectivity with separate events and states for predictable UI updates. We can work 10–15 hours weekly, including 7–11 PM IST, follow your existing codebase and collaboration workflow, and start with the paid trial task.

@santoshkumars17

"Years of hands-on Flutter experience? A whopping five years and counting! I've had the opportunity to develop and deliver numerous production apps, supercharging my skills in the process. What this means for your project is that I can bring a wealth of insight and fast, efficient problem-solving to the table, having faced and resolved complexities similar to what you might encounter with your live IoT app.

@RajAbhisek

Impeller Hi, Your three answers first, then a note. 1. Years and shipped apps: several years hands-on Flutter, multiple apps shipped live to both the App Store and Play Store. 2. A difficult BLoC state problem: a live-device screen where BLE connection state, streamed sensor readings, and user commands all raced - taps arriving while the device was reconnecting produced impossible UI states. I split it into two BLoCs: a ConnectionBloc owning only the link lifecycle (disconnected/connecting/ready/error), and a DeviceBloc that consumed the connection state and refused or queued commands unless it was ready. Structured that way because the bug was really two concerns tangled into one state object - separating the connection machine from the command machine made every impossible state unrepresentable, and reconnect-mid-action stopped corrupting the UI. 3. Availability 7-11 PM IST: yes, I can work reliably in that window. On the role itself: reading first and matching existing BLoC patterns rather than rewriting is exactly how I work in someone else's codebase - small reviewable PRs, and I flag a blocker in writing early rather than going quiet. The "no unasked-for rewrites" line tells me you have been burned before; I work the opposite way. Happy to start with the small paid task. I have not opened the attached brief PDF yet - please share it and I will read it before we begin. Ping me. Thanks, Raj

@jafarali14

Impeller Hi Sir Madam I am a Flutter developer with 5 plus years of hands on experience and have shipped multiple production Android and iOS applications. I am comfortable working on established codebases, following existing architecture and patterns, and making focused changes without unnecessary rewrites. 1. I have 5 plus years of Flutter experience and have shipped production apps for real users across Android and iOS. 2. One difficult BLoC state problem I handled involved coordinating API data, loading states, errors, refresh actions and dependent UI updates. I structured it with clear events and states so async operations remained predictable, testable and easy to maintain without tightly coupling UI and business logic. 3. Yes, I am available to work between 7 PM and 11 PM IST and can commit 10 to 15 hours per week for ongoing work. I am also comfortable with GitHub, Jira, Basecamp and Microsoft Teams and can provide clear written progress updates. I can work with BLE, background services and in app purchases when required. Published apps EasyBalance Wynette Logistics MyKidsEdu I am happy to start with the small paid task and continue long term if the collaboration works well. Thanking you All the very best Cheers

@shinuvs

Impeller Hi, I’m Shinu. I have 15 years of mobile development experience, including hands-on Flutter development and production mobile applications for iOS and Android. I’m comfortable joining an established codebase, understanding the existing architecture and patterns first, and making focused changes without unnecessary rewrites. Flutter experience: I have hands-on experience with Flutter and have shipped production mobile applications across iOS and Android. BLoC: For complex state flows, I prefer separating UI events, business logic, and state clearly through BLoC. For example, in a multi-step workflow with asynchronous API operations, loading/error/success states, and dependent UI updates, I structure events and states explicitly so each transition remains predictable and testable rather than mixing state changes directly into the UI. Availability: Yes, I can work between 7 PM and 11 PM IST and can commit 10–15 hours per week for an ongoing engagement. I’m comfortable with GitHub-based workflows and async collaboration, and I’m happy to start with the small paid task to understand the codebase and demonstrate how I work. Best, Shinu

@saiqasheikhwork5

Drawing from a wealth of experience as a Full Stack Developer, I am confident that I am the best fit for your project. Over the years, I have built several production-grade apps with Flutter, including those with BLoC architecture, making me well-versed in matching and enhancing existing codebases. My approach is to read first, understand the patterns, and amplify what's already there without uninvited rewrites. In line with this, my work with digital solutions has honed my ability to collaborate asynchronously using GitHub, Jira, Basecamp, and Microsoft Teams. One key contribution I can make to your project is my skill in app launches and support. I don't just focus on building but also launching and maintaining your application long-term. Skills in BLE, device pairing, background services, and in-app purchases - while not a requirement - are among my forte. Additionally, keeping clear channels of communication via written updates that profoundly matter to me means you can expect transparency regarding workflow and progress. Regarding your part-time work schedule of 10-15 hours per week, I'm happy to inform you that I am available between 7 PM to 11 PM IST – an Impeller as it were for our smooth collaboration. Let's begin with a small paid task so we can both gauge our compatibility better. Looking forward to joining hands on this exciting journey!

@modesorehari6

⭐⭐⭐Hi there, From Your Vision To Successful — I will take responsibility⭐⭐⭐ Impeller I can help maintain and extend your live Flutter IoT application with a careful approach focused on stability and long term success. I have experience building and maintaining production mobile applications with Flutter, Dart, state management and API integrations. I am comfortable joining existing codebases, understanding current patterns and delivering clean features without unnecessary rewrites. My plan is to first understand your current architecture, BLoC structure and development workflow. I will review the existing codebase carefully then implement features and fixes following your standards. I have hands on experience with complex state management including handling multiple async flows, API states and UI synchronization by separating business logic from presentation layers. I have shipped production applications and understand the importance of reliable updates for real users. I can start work immediately as I have free time available now. I can commit 10 to 15 hours weekly and provide clear updates through GitHub, Jira, Basecamp and Teams. I respect your suggestions and prefer building a long term partnership where I can continuously support and improve your product. I am available to discuss the first paid task and can work between 7 PM to 11 PM IST. Thanks

@guptakishan805

Impeller is the code-word Kishan, let's cut straight to the chase. In the past 3 years, I have focused heavily on Flutter development, having shipped numerous production apps for diverse clients. I leveraged my skills in BLoC - which you specifically require - to solve a complex state problem during a project on resource allocation system. My structure ensured clean separation of UI and business logic enabling better reusability and testability. Working with previous teams remotely via platforms like GitHub, Jira, Basecamp and Microsoft Teams harmonized perfectly well with the asynchronous but collaborative workflow you seek. I am a believer in open communication and provide comprehensive written updates as required. In parallel, several projects involved BLE/device pairing and in-app purchases so I do have this useful skillset you wish. Finally, I understand your need for reliability, consistency and someone who will stick around. As a full stack developer for over 5 years now, my aim has always been long-term impact creation rather than short-term sprints. Rest assured, when or wherever you need me, between 7 PM to 11 PM IST or otherwise, I'll be there: committed, proactive and ready to contribute my best for your live IoT app.

@michela542

Impeller Hi, ➤ The hardest part of working inside a live BLoC codebase you didn't write is staying disciplined about the existing patterns. It's tempting to reshape state handling to fit your own habits, but on a production app with real users, matching what's already there matters far more than making it "cleaner" your way. ✅ I ran into a tricky state problem on a similar project involving a device that streamed real-time data while the user could also trigger manual actions that affected the same state. Two sources were updating the same piece of state at different speeds, and naive BLoC events kept racing each other. I solved it by splitting the state into a clear source-of-truth stream with debounced manual events layered on top through a single reducer-style event handler, so both paths went through one predictable place instead of fighting over the state directly. ✅ That approach worked well. The UI stopped flickering between stale and live values, manual actions felt instant without breaking the real-time stream, and the pattern was simple enough that it matched how the rest of the codebase already handled state, so it didn't feel bolted on. I've worked hands-on with Flutter for several years and shipped multiple( about 7-8 ) production apps to both the App Store and Google Play. Answered above, the dual-source state race condition solved with a single reducer-style event handler in BLoC. Yes, I can be available between 7 PM and 11 PM IST. Best regards, Michel.

@Cruz1217

Impeller, I see the app is already live with real users, so I'll set up a real-time sync to handle updates without disrupting the existing user base. I'd approach this by checking the current BLoC implementation and matching the existing patterns. The goal is to maintain a stable and scalable codebase. In my experience, a common mistake is not handling async operations properly, which can lead to app crashes or unexpected behavior. I'll make sure to handle these operations correctly, and the client can expect a stable and reliable app as a result. I'll also provide clear written updates through GitHub, Jira, Basecamp, and Microsoft Teams to ensure everyone is on the same page.