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

PWA Developer Wanted — Retirement Finance App (UK-Based)

  • Posted:
  • Proposals: 49
  • Remote
  • #4503528
  • OPPORTUNITY
  • Open for Proposals
Yasir Ali M.Huzaifa M.Tosin O.Azhar A.Adeel A. + 44 others have already sent a proposal.
  • 3

Description

Experience Level: Expert
I am looking for an experienced front-end developer to build a Progressive Web App for an established retirement finance organisation business based in Hampshire.

This is a well-specified, clearly scoped project. A full Developer Opportunity document is available on request.

The key requirements:

— Progressive Web App, installable on mobile and desktop
— Local-first storage — all data on the user's device only
— No backend, no server, no cloud storage
— Biometric authentication (Face ID / fingerprint with PIN fallback)
— Clean, simple, trust-building UI
— The architecture is fixed and non-negotiable

This is a Phase 1 prototype engagement with a view to an ongoing relationship as the business grows. White-label versions for professional partners are planned for later phases.

I am looking for someone who:

— Has built PWAs before — please share examples
— Is front-end focused and comfortable without a backend framework
— Communicates clearly in plain English
— Is UK-based (South of England preferred, UK-wide considered)
— Has a small business mindset and interest in a long-term relationship

Note: If your primary experience is with server-side frameworks such as Laravel and you would typically propose a backend solution, this project is unlikely to be the right fit.

To express interest, please send a brief introduction and at least one example of a PWA you have built. A Developer Opportunity document with full details will be shared with shortlisted candidates.

New Proposal

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

Log in

Clarification Board Ask a Question

  • VCONN P.

    Hi Ian,

    Could you please clarify the following:

    1. Will the Developer Opportunity document include wireframes and screen definitions?

    2. Do you require encrypted local storage for sensitive financial data?

    3. Will users need data export/import functionality for backup and device migration?

    4. Are there any regulatory or compliance requirements that should be considered during Phase 1?

    We appreciate the long-term vision for this product and would welcome the opportunity to review the Developer Opportunity document and discuss how we can support both the prototype phase and future white-label releases.

    Best Regards,

    VCONN Private Limited

  • Naresh S.

    Hi Ian, could you please let me know which local-first storage approach is specified in the architecture (IndexedDB, encrypted local database, browser storage, etc.) and whether the biometric authentication requirement must work purely through WebAuthn/device capabilities without relying on any external identity or cloud services?

    Thanks
    Naresh

  • CYTNHIA W.

    1. Since the application is local-first with no backend, what is the expected recovery strategy if a user loses, upgrades, or resets their device? This is often the most important architectural consideration for financial information stored exclusively on-device.

    2. For the future white-label versions, do you envision simple branding variations, or will different partners require different workflows, data structures, and feature sets over time?

    3. Which aspect of the user experience is most critical to get right for Phase 1: security confidence, ease of use for older users, speed of access, or long-term data reliability?

    4. Is the long-term vision for the application to remain entirely offline and device-based, or is there a possibility that future phases introduce optional synchronization, adviser access, or partner integrations?

    5. What is the single biggest concern preventing users from trusting existing retirement-planning applications today? Understanding that often drives the most important design and product decisions.

  • Asad C.

    - Could you provide more details about the types of retirement finance information users will manage within the application?

    - For biometric authentication, should access be required every time the application is opened, or should there be configurable session durations? Additionally, are there any requirements for data encryption at rest, inactivity timeouts, failed login protection, or additional security measures beyond Face ID, fingerprint authentication, and PIN fallback?

    - Will users need the ability to generate reports, download PDFs, print summaries, or share selected information externally?

  • Speqto technologies private limited

    1- Do you already have the complete UI/UX designs and user flow documentation prepared, or would you like the developer to assist with the interface design as well?

    2- Since all data will remain on the user's device, should the application support data backup/export and restore functionality for users who change devices?

    3- For biometric authentication, do you have a preferred approach or technology in mind, or would you like recommendations based on PWA best practices and device compatibility?