Complete Android App Development

I'm seeking an experienced Android developer to finish up my app. The project involves enhancing the user interface, completing backend functionality, and thorough testing and debugging.

Key Tasks:
- User Interface: Improve and finalize the app's UI for a better user experience.
- Backend Functionality:
- API Development: Create and integrate necessary APIs.
- User Authentication: Set up secure user authentication methods.
- Testing and Debugging: Identify and fix bugs, ensure app stability and performance.
1. App purpose

Build a TikTok Operations OS that:

- Standardizes ideation, approvals, production, post-mortems, and analytics.
- Implements the existing “TikTok Music Virality Playbook” as a living system.
- Supports roles: Creator, Editor, Social Manager, Brand Manager, Director.

Core modules:

- Post creation & workflow (draft → review → approved → posted).
- Post-mortem engine (4-question template + deep-dive).
- Library of Wins (case study archive).
- Performance dashboard (metrics by audio category, visual style, creator).
- Training & onboarding (drills, levels, certification).

---

2. Tech stack

Front-end:

- Next.js (App Router) + React
- Basic component library (custom or Tailwind/Chakra)

Back-end / data:

- Supabase (Postgres + Auth + Storage)
- Supabase JS client in lib/supabaseClient.ts

Auth & roles:

- Supabase Auth
- profiles table with role field:
- creator, editor, socialmanager, brandmanager, director.

---

3. Database schema (Postgres / Supabase)

profiles

- id (uuid, PK)
- email (text, unique)
- name (text)
- role (text)
- created_at (timestamp)

posts

- id (uuid, PK)
- title (text)
- creator_id (uuid → profiles.id)
- audio_category (text: trending / emerging / evergreen)
- visualstyle (text: highvelocity / controlled / cinematic)
- goal (text: reach / discovery / branding / conversion)
- status (text: draft / inreview / changesrequested / approved / posted)
- tiktok_url (text, nullable)
- created_at (timestamp)
- posted_at (timestamp, nullable)

approvals

- id (uuid, PK)
- post_id (uuid → posts.id)
- approver_id (uuid → profiles.id)
- approver_role (text)
- decision (text: approved / rejected / changes_requested)
- notes (text)
- created_at (timestamp)

metrics

- id (uuid, PK)
- post_id (uuid → posts.id)
- threesecretention (numeric)
- avgwatchtime (numeric)
- completion_rate (numeric)
- shares (integer)
- saves (integer)
- comments (integer)
- ctr (numeric)
- follower_delta (integer)
- collected_at (timestamp)

post_mortems

- id (uuid, PK)
- post_id (uuid → posts.id)
- hookstoppedscroll (boolean)
- visualmatchedbeat (boolean)
- audiocategoryappropriate (boolean)
- one_adjustment (text)
- deepdivenotes (text, nullable)
- created_by (uuid → profiles.id)
- created_at (timestamp)

wins

- id (uuid, PK)
- post_id (uuid → posts.id)
- retentionscreenshoturl (text)
- hookframescreenshot_url (text)
- summary (text: “why it worked”)
- created_by (uuid → profiles.id)
- created_at (timestamp)

drills

- id (uuid, PK)
- name (text)
- description (text)
- level (integer: 1–4)

drill_completions

- id (uuid, PK)
- drill_id (uuid → drills.id)
- user_id (uuid → profiles.id)
- completed_at (timestamp)

creator_levels

- id (uuid, PK)
- user_id (uuid → profiles.id)
- level (integer: 1–4)
- certified_at (timestamp, nullable)

---

4. File structure (Next.js + Supabase)

`text
tiktok-ops-os/
app/
layout.tsx
page.tsx // Home: list posts
posts/
page.tsx // All posts
new/
page.tsx // New post form
[id]/
page.tsx // Post detail + approve + metrics
PostMortemForm.tsx // Post-mortem component
approvals/
page.tsx // List posts in review
[id]/
page.tsx // Approve/request changes
wins/
page.tsx // Library of Wins
[id]/
page.tsx // Win detail
training/
page.tsx // Creator training overview
drills/
page.tsx
levels/
page.tsx
dashboard/
page.tsx // Performance dashboard
settings/
page.tsx // Roles, thresholds

components/
Navbar.tsx
Sidebar.tsx
Button.tsx
Card.tsx
Input.tsx
Select.tsx
Modal.tsx

lib/
supabaseClient.ts
auth.ts
roles.ts
validators.ts
utils.ts

pages/api/
posts/
create.ts
submitForReview.ts
approvals/
approve.ts
requestChanges.ts
postmortems/
create.ts
wins/
create.ts
training/
completeDrill.ts
updateLevel.ts

styles/
globals.css

package.json
README.md
`

---

5. Core MVP screens & flows

Creator:

- Home: list of own posts (draft, changes_requested, approved, posted).
- New Post: form with title, audio category, visual style, goal → status = draft.
- Submit for Review: button to set status = in_review.

Manager/Brand/Director:

- Approvals: list of posts with status = in_review.
- Approval Detail: approve / reject / request changes → writes to approvals, updates posts.status.

Post-Mortem:

- Available when status = posted.
- Form with 4 fields:
- hookstoppedscroll (boolean)
- visualmatchedbeat (boolean)
- audiocategoryappropriate (boolean)
- one_adjustment (text)
- Saves to post_mortems.

Library of Wins:

- List of wins entries (linked to posts).
- Each entry: video link, retention screenshot, hook frame screenshot, summary.

Dashboard:

- Aggregates metrics by:
- audio_category
- visual_style
- creator
- Shows weekly/monthly summaries.

Training:

- Shows drills, completion status, creator level.

---

6. Example code references

You already have:

- supabaseClient.ts
- NewPostPage component
- PostPage with approve action
- PostMortemForm component

Developer should:

- Wire Supabase env vars.
- Create tables per schema above.
- Implement role-based routing (e.g., via profiles.role).
- Expand UI and API routes from this spec.

---

You can send this file as:

- TikTokOpsOSAppSpec.md