Lovable app created

App Developer Brief. Fix, Stabilize, Make Editable, Add Users, Deploy · I have a web app prototype built with a no-code / AI builder (Lovable) and Supabase as the backend. The app structure and UI are mostly in place, but the current build is not reliably usable because core scre ...

Job description

App Developer Brief. Fix, Stabilize, Make Editable, Add Users, Deploy

I have a web app prototype built with a no-code / AI builder (Lovable) and Supabase as the backend.

The app structure and UI are mostly in place, but the current build is not reliably usable because core screens are still read-only or break when we try to make them editable.

I need an experienced full-stack developer to take over and finish it properly. The goal is to turn the prototype into a stable, editable, role-based application and deploy it to production.

Current status

UI and navigation exist, but several pages are not truly editable.

Attempts to add "editable" workflows often result in:
Blank pages

Inserts/updates failing due to Supabase Row Level Security (RLS)

Missing or inconsistent database tables/migrations

Actions that appear to work but do not persist after refresh

We need to stop relying on the builder's automatic behavior and implement a consistent data and permission pattern.

What I need you to deliver
1) Stabilize the app

Ensure no page ever renders blank.

Add proper empty states ("no records yet") and in-app error banners (show real Supabase errors).

Implement a global error boundary and logging so issues are visible and debuggable.

Clean up routes/navigation so everything points to working pages.

2) Make key modules truly editable (database-backed)

"Editable" means:
create a record, edit it, save it, refresh the page, and the data is still there.

Implement a consistent CRUD + workflow pattern:

Status workflow:
Draft → Submitted → Approved → Active/Locked

Only Admin can approve and lock versions.

Draft/submitted records are editable. Approved/active are read-only.

Start with a small set first to prove the pattern, then roll it across the rest:

Module A:
Versioned records (create draft version, edit fields, save, submit, approve)

Module B:
Table-based line items (add/edit/delete rows, computed totals, save)

Attachments:
evidence linking per record (Supabase storage + DB linking)

Audit log:
track who changed what and when

3) Users, roles, and permissions (RBAC)

I need proper user management and strict access control enforced in the backend, not only in UI.


Deliver:
User authentication

Role-based access control (org-level and project-level roles)

Role-based visibility and edit permissions per module


Admin screens to:
invite users

assign roles

grant project access

disable users


Supabase RLS policies that enforce:
tenant isolation (users cannot see other organizations)

project isolation (only allowed projects)

approval permissions restricted to admin roles

4) Database cleanup and migrations

Review and normalize the Supabase schema.

Create proper migrations for all required tables.

Fix inconsistent table naming and missing relationships.

Add helper SQL functions for permission checks (e.g., can_access_project, is_project_editor).

Implement RLS policies in a consistent way across all tables.

5) Deployment and handover

Export the app from the builder to a proper repo (GitHub).


Set up environments:
staging

production

Configure domain, SSL, environment variables, and Supabase keys.


Provide a clean handover:
architecture overview

schema + migrations

RLS policy documentation

deployment steps

known limitations and next improvements


Optional, depending on scope:
Wrap as mobile apps (iOS/Android) only if needed. Otherwise ship as a web app first.

Expectations and working style

I want incremental, testable delivery.

Do not attempt to "make everything editable" at once.

First milestone must prove real edit/save/refresh persistence with correct RLS, then replicate.

Success criteria

App is stable. No blank screens.

Users can create/edit/save records and data persists after refresh.

RBAC works. Users only see and edit what their role allows.

Admin can manage users and access.

Production deployment is live with staging environment and documented handover.

What I will provide

Access to the current Lovable project and Supabase project

The existing UI structure and module list

The current preview link for reference (not for production)

Contract duration of 1 to 3 months. with 30 hours per week.

Mandatory skills:
Web Development, Mobile App Development, Android, iOS, Android App Development, App Development