phoenix
phoenixPhoenix - Your AI Assistant
Inactive session will be ended in 24 hours
End Session

Mobile App Foundation Build: Flutter or React Native

  • Posted:
  • Proposals: 47
  • Remote
  • #4513050
  • OPPORTUNITY
  • Open for Proposals
Rejoice Hub L.Awais A.Khalid H.Shoaib A.Joshua A. + 42 others have already sent a proposal.
  • 6

Description

Experience Level: Expert
I’m building a mobile platform for a specific industry vertical and need an experienced developer to build the foundational architecture it will run on. This is phase one of a larger, well-documented build, a full specification is available and will be shared with the successful candidate.

The foundation covers:

- User authentication and account creation

- A multi-tenant data layer with strict isolation between accounts, enforced at the data layer, not just the interface

- An offline-first sync skeleton: the app must work fully for data entry while offline, queuing actions locally and syncing once connectivity returns

- An append-only event log as the core data model, every action recorded as an immutable event rather than overwriting existing records

- A finance module (income, expenses, customers, suppliers, debtors, creditors, cash flow) and a staff/HR module (staff records, performance, salary), both built as reusable capabilities available to every part of the app, not tied to one feature

- Two initial screens built on top of the above, to prove the foundation holds real functionality, not just plumbing

This phase does not include: UI/UX design (a separate design pass is planned later), any operation-specific features beyond the two initial screens, or third-party integrations.

Target platform: cross-platform mobile (Flutter or React Native, open to your recommendation with reasoning). Please quote your hourly rate and estimated hours for this scope specifically, rather than a fixed total, given some of this (particularly multi-tenancy and offline sync) needs to be scoped properly once you’ve reviewed the full specification. Prior experience with offline-first mobile apps and multi-tenant SaaS architecture is more important here than industry-specific experience.

New Proposal

Login to your account and send a proposal now to get this project.

Log in

Clarification Board Ask a Question

  • Khmil A.

    Hi Tinashe

    I checked your job requirement and I have some questions now.

    Can you share the complete phase-one specification and acceptance criteria?
    What exactly are the two initial screens and their required workflows?
    Is there an existing backend, database, codebase, or cloud environment?
    Should phase one include production deployment, or only a working development build?
    What deliverables are expected: source code, API documentation, architecture diagrams, tests, and deployment instructions?
    Are there any planned native-device features that may influence the framework choice?
    Which minimum Android and iOS versions must be supported?
    Should tablet layouts be supported in phase one?
    What represents a tenant: company, branch, team, or individual account?
    Can a user belong to multiple tenants?
    What roles and permission levels are required?
    Is tenant isolation expected through separate databases, separate schemas, or row-level security?
    Are there specific security, privacy, auditing, or regulatory requirements?
    Should platform administrators be able to access or manage multiple tenants?

  • CYTNHIA W.

    1: Five years from now, do you envision this remaining a single-product application, or becoming a platform where entirely new business modules can be added for every tenant? That decision will significantly influence how I design the domain boundaries, event model, and reusable service architecture from the outset.

    2: For offline synchronization, what should happen when two devices modify the same entity while disconnected? Do you already have defined conflict-resolution rules, or would you like the synchronization engine to implement event-based reconciliation, version vectors, or another conflict-resolution strategy as part of the core architecture?

  • Khalid H.

    Hi, could you please clarify the following questions?

    1. Could you share the detailed SRS or architecture document, and confirm whether this phase includes only the mobile application foundation or also the backend services (authentication, APIs, event store, and sync engine)?

    2. Do you already have a preferred backend stack (e.g., Supabase, Firebase, .NET, NestJS, Laravel, PostgreSQL) and cloud provider, or would you like the developer to recommend the complete architecture for offline sync, event sourcing, and multi-tenancy?

    3. For the offline-first architecture, are there any specific requirements regarding conflict resolution, data synchronization strategy, encryption of local data, or maximum offline storage limits?

    4. How many user roles and tenant types will be supported in Phase 1, and what authentication methods are required (email/password, OAuth, SSO, MFA, etc.)?