FlutterFlow + Supabase Developer Needed

# Mobile App Developer Needed — Sporting Social I am looking for an experienced mobile app developer or small development team to help design and build the MVP of **Sporting Social**, a location-based social and community platform built specifically for shooting sports. I have tested existing community platforms such as Circle and Honeycommb, but they require too many workarounds and do not provide the purpose-built experience I am looking for. I believe Sporting Social needs to be its own application. ## The Vision Sporting Social is intended to connect **shooters with the gun clubs, people, events, and instruction around them.** The platform serves two primary audiences: **Shooters** — who want to find clubs, connect with other local shooters, find people to shoot with, discover events and classes, and access educational content. **Gun Clubs / Shooting Ranges** — who want an easy way to communicate with their customers/members, build community, promote events and classes, send notifications, and receive feedback from the people using their facilities. The app should ultimately be organized around four ideas: **FIND → CONNECT → SHOOT → LEARN** The goal is NOT to build "Facebook for shooters." I want Sporting Social to be a useful tool that someone has a reason to open whenever they are thinking about going shooting. ## 1. CLUB DISCOVERY & CLUB COMMUNITIES Users should be able to find shooting clubs based on their location, ZIP code, or proximity. Sporting Social should ideally contain a directory of clubs, including clubs that have not yet joined the platform. A participating club can **claim/verify its profile** and operate its own community within Sporting Social. Users can follow multiple clubs and designate one as their **Home Club**. Each participating club should have its own page containing: * Club information * Announcements * Community posts * Comments and engagement * Polls * Events/calendar * Shoot Sessions * Classes * Facility updates * Push notifications * Club administrators/moderators This should feel like a purpose-built club experience rather than a generic "Group" feature. ### Request a Club This is an important growth feature. If a club has not yet joined Sporting Social, users should still be able to find it and tap: **REQUEST THIS CLUB** Sporting Social should track how many users have requested each club. This gives us the ability to approach a club and say: **"127 shooters in your area have requested your club on Sporting Social. Claim your club."** Unclaimed, claimed, and verified clubs therefore need to be considered in the architecture. ## 2. SHOOT SESSIONS — CORE FEATURE This is one of the most important and differentiating features of Sporting Social. Many people enjoy shooting but do not always have someone to shoot with. A user should be able to quickly announce: **"I'm going shooting — who wants to join me?"** This should NOT feel like creating a traditional calendar event. Creating a Shoot Session should be extremely fast and intuitive. For example: **Sporting Clays at Bald Mountain** Saturday · 10:00 AM 3 shooters going · 1 spot available **JOIN SESSION** A user creating a session should be able to specify: * Club * Date * Time * Shooting discipline/activity * Number of available spots * Skill level/pace if desired * Notes * Public/friends/invite-only visibility Other users can RSVP, see who is attending, and receive appropriate notifications. Eventually, Shoot Sessions could also support temporary group chat and features such as "Looking for a Squad" for tournaments. I want **Shoot Sessions to feel like Sporting Social was specifically built around this feature.** ## 3. SOCIAL / COMMUNITY Users should be able to interact with other shooters within their local club communities. Core functionality should include: * Posts * Comments * Likes/reactions * Photos * Polls * Mentions * Basic shooter profiles * Shooting friends/connections * Notifications Shooter profiles should focus on relevant information such as home club, preferred shooting disciplines, experience level, and typical shooting availability rather than trying to replicate a traditional social media profile. ## 4. CLUB EVENTS & CALENDAR Clubs should be able to create official events such as: * Tournaments * Leagues * Classes * Demo days * Meetings * Social events Official **Club Events** should remain separate from member-created **Shoot Sessions**. Users should be able to view events at individual clubs as well as eventually browse an aggregated: **EVENTS NEAR ME** calendar across multiple participating clubs. ## 5. EQUIPMENT / FACILITY ISSUE REPORTING Users should be able to easily report a problem they encounter at a club. For example: **Report an Issue** Club: Bald Mountain Location: Station 7 Category: Target Machine Issue: Machine isn't throwing targets Photo: Optional The club administrator receives the report and can mark it: **Open → In Progress → Resolved** The reporting user should receive a notification when the issue is resolved. This is intended to create another valuable connection between clubs and the people using their facilities. ## 6. CLUB STATUS & COMMUNICATION Participating clubs should be able to quickly communicate important information. Examples: **🟢 All Facilities Open** **🟡 Limited Operations** North Course closed until approximately 1:00 PM. **🔴 Closed** Clubs should also be able to send push notifications to followers for announcements, closures, events, etc. Users should control which types of notifications they receive. ## 7. LEARN — CLASSES & EDUCATIONAL CONTENT Sporting Social should ultimately include a **Learn** section. This will include both: ### In-Person Classes Clubs and approved instructors should eventually be able to offer paid classes through Sporting Social. Users can: * Discover classes near them * View instructor/class information * Register * Pay * Receive confirmation * Manage upcoming classes ### Online Education Sporting Social should also be architected to support premium educational content, including: * Instructional videos * Online courses * Multi-lesson courses * Free and premium content * One-time course purchases * Subscription-only content Longer term, I envision a **Sporting Social+** subscription providing access to a premium library of shooting instruction and educational content. The complete learning marketplace does not necessarily need to be included in the first MVP, but the architecture should anticipate paid content, subscriptions, instructors, purchases, and access permissions so that we do not have to rebuild the application later. ## 8. USER ROLES The architecture should anticipate multiple roles: **Shooter** **Club Administrator** **Instructor** **Sporting Social Administrator** A user may have more than one role. For example, an instructor may also be a shooter and a club administrator. ## 9. CLUB ADMINISTRATION Clubs will need a simple management interface, preferably accessible via web/desktop, allowing authorized administrators to: * Manage club information * Post announcements * Create posts and polls * Create events * Create classes * Send push notifications * Review equipment reports * Update facility status * Moderate community content * Manage club administrators * View basic engagement/activity information The administrative side should be simple enough that a typical gun club employee can use it without training. ## 10. USER EXPERIENCE The consumer app should be extremely simple. A possible navigation structure is: **HOME | CLUBS | SHOOT | LEARN | PROFILE** ### HOME A personalized overview of what's happening around the user: * Shoot Sessions * Club announcements * Nearby events * Facility updates * Classes * Relevant community activity ### CLUBS * My Clubs * Nearby Clubs * Search * Club profiles * Request a Club ### SHOOT * Shoot Sessions near me * Sessions at my clubs * Create a Shoot Session * Sessions I've joined ### LEARN * Classes near me * Online courses * Instructional content * Sporting Social+ ### PROFILE * Shooter profile * Shooting friends * My sessions * My events/classes * Purchased courses * Notification/settings ## Technology My initial research suggests a stack such as: **FlutterFlow + Supabase** with appropriate services for: * iOS and Android * Authentication * Database * Geolocation * Maps * Push notifications * Image/file storage * Payments/subscriptions * Role-based permissions * Web-based club administration However, I am open to recommendations. I am more concerned with building the product correctly, maintaining ownership of the application/data, and creating a scalable foundation than forcing a specific technology choice. ## What I Need From the Developer I am looking for more than someone who simply takes a list of screens and builds them. I want someone who can help translate this concept into an **intuitive, polished MVP**, identify unnecessary complexity, recommend better workflows, and build a foundation capable of expanding as Sporting Social grows. I would prefer to begin with a **paid discovery/design phase** before committing to the complete build. That phase should produce: 1. Final V1 feature scope 2. User flows 3. Wireframes/UI direction 4. Database/data architecture 5. Technical architecture 6. Development milestones 7. Final MVP cost/timeline If that process goes well, my preference is to continue with the same developer/team through development, testing, and launch. ## When Applying Please provide examples of relevant applications you have personally built, particularly those involving: * FlutterFlow * Supabase * Social/community functionality * Location-based discovery * Events/RSVPs * Push notifications * User-generated content * Role-based permissions * Payments/subscriptions * iOS/Android deployment Please also briefly explain **how you would approach Sporting Social technically and what you would recommend including or excluding from V1.** I am particularly interested in developers who understand **product development and user experience**, not simply coding. Please begin your response with **"Sporting Social"** so I know you have read the complete project description. **The long-term goal is simple: Sporting Social should become the digital connection between shooters and the places, people, events, and instruction that make them want to shoot more often.**