Backend Developer Needed for Consumer Caregiver App We’re building a caregiver app that helps families keep track of a loved one’s care information, including diagnoses, medications, surgeries, notes, and tasks. This is a direct-to-consumer app, not a hospital or clinic product, so we need someone who can build a secure, privacy-first backend for sensitive health data. What you’ll build: - User authentication and account management. - Care recipient profiles. - Structured health records for diagnoses, medications, surgeries, allergies, appointments, notes, and care tasks. - Role-based sharing for multiple caregivers. - Secure file storage for documents or images. - Audit/activity logging. - Export and deletion features. - Admin tools for support and account recovery. What we need: We’re looking for a backend developer who can build a clean, secure, production-ready system with strong privacy controls. Required experience: - Strong backend development experience. - Experience with Postgres and secure API design. - Understanding of authentication, authorization, and role-based access control. - Experience with encryption, secure file storage, and logging. - Comfortable working with consumer health or sensitive data. - Ability to document architecture and hand off code cleanly. Nice to have: - Experience with healthcare, healthtech, or privacy-sensitive apps. - Experience with Supabase or AWS. - Familiarity with FTC health privacy expectations for consumer apps. - Experience designing systems that can scale into stricter compliance later. Preferred stack For this project, we’re leaning toward a cost-friendly, modern stack such as: - Front end: Lovable. - Backend: Supabase or a similar managed Postgres backend. - Auth: built-in auth with strong password/session handling. - Storage: private file storage. - Permissions: row-level security or equivalent. - Optional server logic: edge functions or a small Node service. If you think a different stack is better, explain why. Security and privacy expectations: This app will store sensitive family health information, so security matters a lot. We need the backend to include: - Encryption in transit and at rest. - Strong access controls. - Minimal data collection. - No unnecessary third-party tracking or ad-tech. - Audit logs for important actions. - Secure password handling. - Private storage and restricted file access. - Clear privacy-aware architecture. Important note: This is not a hospital backend. We do not need a complex enterprise healthcare platform on day one. We do need someone who understands how to build a secure consumer health app properly, with the option to evolve later if the product grows. Deliverables: 1. A short architecture proposal. 2. Recommended stack and rationale. 3. Basic database schema. 4. Security and permissions plan. 5. Estimated timeline and budget. 6. Build the MVP backend after approval. Please send: - A short intro. - Relevant backend projects. - Any healthcare, privacy, or sensitive-data experience. - Your preferred stack. - Your estimated cost and timeline. - One example of a backend system you’ve built that required careful permissions or security.

Description We are building a startup almost entirely in v0 by Vercel, and I'd like to hire an experienced v0 user for a one-hour Zoom consultation. This is not a coding project. I'm looking for someone who understands how professional teams organize and manage v0 projects and can teach me best practices. We'll share screens and walk through my current setup. Topics I'd like to cover Overall v0 architecture Projects vs Chats Repositories GitHub integration Team permissions Workspaces Sharing projects with outside contractors Security best practices Version control Organizing multiple companies inside v0 Naming conventions Branching and deployment workflow How designers and developers should collaborate Recommended workflow from idea → design → production Common mistakes to avoid At the end of the session I'd like to leave with: A recommended structure for my workspace A clean folder/project organization Security recommendations Permission recommendations for team members Best practices document (bullet points are fine) Requirements You should: Have extensive experience using v0 Have built multiple production projects Understand GitHub integration Understand team permissions and collaboration Be comfortable teaching and answering questions Speak fluent English Bonus if you've used: Vercel GitHub Supabase AI coding tools (Claude, Cursor, Lovable, Bolt) Engagement One-hour Zoom call Screen sharing Fixed budget: $150 If things go well, this may lead to additional consulting work as we continue building our platform.

About the Business I own Meet U @ The Net, an established beach volleyball league in Southern California. Website: https://meetuatthe.net The league currently runs multiple seasons per year, has strong player retention, and regularly reaches registration capacity. I am looking for a developer or small team to help modernize the business systems while providing documentation and knowledge transfer so I can eventually manage and improve the platform myself. This is not a one-time project. I intend to build the platform in phases over multiple seasons. Phase 1 Goals CRM Foundation Current data exists across: Excel Airtable Google Sheets The goal is to consolidate historical league data into a single CRM/database. Examples: Players Teams Seasons Registrations Waitlists Payments Participation history Website Rebuild Build a modern website focused on: Registrations League information Schedules Standings FAQ Mobile responsiveness SEO foundation AEO foundation Registration System Support: Individual registrations Team registrations Waitlists Coupon codes Discount codes Payment tracking Waiver System Requirements: Team captains can register teams Individual players must create their own profile Individual players must sign their own waiver Waiver tracking and status management Knowledge Transfer (Required) I do not want a black-box system. I want: Written documentation Loom walkthrough videos Live walkthrough sessions Ability to ask questions after launch The goal is to learn how the system works while it is being built. Future Phases (Not Part of Phase 1) Future projects may include: Scheduling tools Referee score entry portal Automatic standings Sponsorship CRM AI features Mobile applications The initial focus is building a strong foundation. Preferred Technologies Open to recommendations. Currently interested in: Next.js Supabase OpenAI GitHub Budget Approximately: $5,000 – $7,000 for Phase 1 Future phases expected if Phase 1 is successful. Looking For Full-stack developer or small team CRM/database experience SaaS experience Strong communication Documentation-focused Comfortable working with non-technical founders Please send: Relevant projects Technologies used Availability Pricing model Examples of documentation or client training