Synceria

Mainstream dating apps are built around a core mechanic that serves engagement metrics more than real connection: the swipe. Photos, short bios, and basic prompts drive first impressions. The result is shallow engagement, swipe fatigue, and high churn in a product category where 79% of Gen Z report burnout, yet the space generates $12.37 billion annually and is projected to exceed $24 billion by 2032.

Music is a fundamentally different compatibility signal. Shared music taste is among the strongest predictors of social bonding, more durable than demographic similarity and more revealing than profile photos. Spotify's catalog provides a standardized, structured way for users to express their musical identity by selecting real artists rather than typing genres into a text field. The Spotify Web API makes this catalog searchable at scale, with Apple Music planned as a future integration.

The opportunity was to build a dating experience where curated musical identity replaces the photo-first swipe as the primary compatibility signal. Competitive analysis of nine apps (Tinder, Bumble, Hinge, Tastebuds, Vinylly, POM, Vipriya, Solmate, and Sitch) confirmed the gap: no major app built matching around structured Spotify catalog data as the primary signal.

The competitive moment sharpened in June 2025 when Tastebuds (the pioneer of music-based dating, with over 1 million all-time registrations and roughly 70,000 weekly active users) permanently shut down. An aging codebase, not a demand problem. A half-million users worldwide suddenly had nowhere to go, while the next competitor, Vinylly, had only ~2,000 members. Capturing even 10% of Tastebuds' weekly active users would yield ~7,000 highly-engaged early adopters, several times Vinylly's entire base.

Research combined two tracks: desk research and primary user research. Desk research built a 10-dimension audience analysis covering demographics, geography, psychographics, behavioral insights, needs and pain points, goals and motivations, channel and media habits, barriers and objections, competitive landscape, and market size and trends, all grounded in cited third-party statistics.

Competitive analysis went beyond surface comparison. For each of the 9 apps studied, the research covered founding stories, team structures, funding paths, and differentiation strategies. The goal was to understand not just what competitors built, but how they got started and where they were vulnerable.

Primary research included a 20-question survey distributed to 50+ users focused specifically on branding, logo design, and color preferences. This validated visual identity decisions before committing to final assets, confirming the color palette and 'Vibe-drop' logo direction with strong positive reception.

The most consequential finding: competitive research into how top dating apps got started (small teams, scrappy launches, and campus or city-density strategies) directly shaped the go-to-market approach. Soft launch 6–8 weeks before hard launch, city-first density strategy, and festival-season timing were all research-driven decisions.

The MVP centered on four pillars: (1) Spotify Web API integration, where users search the catalog and select favorite artists to build their music profile, (2) genre-based vibe rooms that group users by shared musical taste (each selected genre, sub-genre, or artist creates a separate user pool), (3) a swipe and matching system with like tiers and daily caps by subscription level, and (4) real-time chat via Stream Chat for matched users.

What was intentionally deferred: AI-powered matchmaking (scoped but deprioritized in favor of shipping core matching), Apple Music as an alternative data source (planned for post-launch), identity verification via Veriff (evaluated and scoped, deferred to post-launch), ad-supported monetization (AdMob explored but pulled due to dependency conflicts with the existing package ecosystem; Meta Ads under consideration as the app matures), audio/video calling, group matching, advanced concert integration, and couples modes.

The biggest product tradeoff was scope discipline. Early planning included an AI matchmaking advisor, a Spotify account-linking OAuth flow, and ad-supported free tiers. Each was evaluated, and each was cut or simplified when the technical or compliance cost outweighed the V1 value. The decision to ship a focused product faster proved more valuable than shipping a feature-rich product later.

The subscription model was refined from an initial 4-tier plan to 3 tiers (GA free, VIP, AllAccess) during development, benchmarked against 8 competitor pricing models and positioned to undercut Tinder and Bumble's premium tiers while matching features. Choosing Supabase over Firebase was another defining decision: PostgreSQL's relational power was essential for complex match scoring queries, and Edge Functions kept infrastructure serverless.

Five primary flows were designed: (1) Onboarding: account creation, Spotify artist search to build a music profile, genre and subgenre selection, photo upload, and first vibe room assignment. (2) Discovery: browsing genre-based vibe rooms, viewing profiles with music data, swiping with like/super like/pass. (3) Matching: mutual like confirmation and match notification. (4) Chat: real-time messaging via Stream Chat for matched users. (5) Profile management: editing bio, photos, music preferences, and subscription settings.

Onboarding was the highest-stakes flow to get right. The Spotify integration step, where users search the catalog and add favorite artists, is the first moment the app delivers meaningful value. The original plan used Spotify OAuth to link accounts and access listening history directly, but this was simplified to catalog search via the Spotify Web API. The tradeoff: less automated data, but faster development, full Spotify TOS compliance, and the same outcome. Users build a music identity that powers matching.

Friction was reduced wherever convention could be leveraged. The 5-tab bottom navigation (Discovery, Vibes, Match, Chat, Home) mirrors patterns from Tinder, Bumble, and Hinge so muscle memory transfers. Genre selection was designed to feel like identity expression rather than a settings form: choosing genres immediately assigns you to vibe rooms where everyone shares that taste, creating immediate value from the first selection.

Trust and clarity shaped every detail. Music data permission copy was written to explain exactly what is accessed and why. Genre selection was framed as identity expression: choosing genres immediately assigns you to vibe rooms where everyone shares that taste, creating immediate value from the first selection.

The interface was built around three principles: (1) music-first identity, where every screen reinforces that this is a music-powered experience, not a generic dating app with a music skin, (2) dark-mode native, where the charcoal background (#1A1A1A) creates an immersive, nightlife-adjacent atmosphere that makes vibrant accent colors pop, and (3) clarity over cleverness, where standard interaction patterns were favored over novel but confusing mechanics.

The visual identity had to survive two complete rebrands. The app launched internally as Vibin', was renamed to SSYNC mid-development, then renamed again to Synceria before shipping. Each rename required rethinking the visual identity, domain strategy, store listings, and marketing materials from scratch while continuing to build and ship the product.

During the Vibin' phase, the logo went through 30+ initial concepts, narrowed through an icon usability map of 35 concepts, refined to the 'Vibe-drop' direction (a teardrop combined with a waveform forming a V). The color palette went through 4 distinct explorations before landing on the Vibin' phase gradient: Vibin Pink (#FF4D9D), Neon Magenta (#FF2EAA), Electric Purple (#C728FF), and Vivid Violet (#8927FF). The 50+ user branding survey validated this palette and direction with strong positive reception. Through two subsequent rebrands, the production palette evolved to Pink (#A10078), Purple (#6A1FB9), and Teal (#00C896), a shift that preserved the bold, energetic character while maturing the identity.

The SSYNC rebrand produced a complete playbook: a stylized double-S wordmark (two S's mirrored like eighth notes), strict casing rules, new domain strategy, social handle reservations, and rebuilt ASO copy for both stores. When Synceria became the final name, all of this was rebuilt again. The core design language (the color palette, typography, and dark aesthetic) survived all three phases, proving the design foundation was strong enough to transcend any specific name.

Typography was finalized as a dual-typeface system. The original design used Recoleta for headings (warmth and personality with high-contrast letterforms), but this was later switched to Montserrat (geometric, modern, and clean) for a more polished, contemporary feel. Inter remained for body copy (neutral and legible). A complete typographic scale was defined, from H1 at 48px/Montserrat Bold through Caption at 14px/Inter Regular, with documented line-height, paragraph spacing, and tracking values. The design system also formalized a complete error state color system (light and dark variants, all WCAG AA compliant).

The mobile app runs on React Native with Expo, TypeScript, and NativeWind (Tailwind CSS for React Native). State management uses Zustand for global state and Supabase client for data fetching and caching. Expo EAS handles build and deployment pipelines for both iOS and Android from a single codebase. Navigation uses Expo Router with file-based routing and automatic deep-link generation.

The entire backend runs on Supabase: PostgreSQL with row-level security policies for data isolation, Supabase Auth for email/password registration, Supabase Storage for photos and media, Stream Chat for production-grade messaging, and Supabase Edge Functions on Deno runtime for serverless AI logic. The database schema consists of 40+ tables covering profiles, vibes, matching, subscriptions, moderation, and analytics.

External integrations: Spotify Web API for artist catalog search (pivoted from OAuth account linking to a simpler, TOS-compliant model where users search and add artists directly). Stream Chat for production-grade messaging with delivery guarantees, read receipts, and offline handling. RevenueCat for unified subscription management across both platforms. PostHog for product analytics. Sentry for crash reporting. Apple Music integration was scoped as a future alternative data source, and AdMob was explored for free-tier monetization but pulled due to dependency conflicts with the existing package ecosystem.

A 5-phase codebase migration from the original repo to a monorepo (Analyze → Map → Execution Plan → Iterative Execution → Clean-up) was executed mid-development, a significant engineering effort documented in full. Twenty Edge Functions on Deno runtime handle serverless logic including Spotify token exchange, subscription validation, and notification delivery.

Testing combined manual QA across physical devices with a structured red team security audit framework. The audit covered six categories: RLS policy verification (checking database-level data isolation), monetization integrity testing (ensuring RevenueCat subscription enforcement cannot be bypassed), client-side threat modeling (evaluating Expo SecureStore token handling and API exposure), 'vibe coding' pitfall detection (patterns where rapid development may have introduced vulnerabilities), Spotify integration testing (verifying Web API token exchange and search flow), and Edge Function security (validating API key management and input sanitation).

Device testing used physical hardware: Dylan's personal iPhone was registered as a test device, and an older Android phone was used for Android testing, validating on real devices before simulator testing. A notable cross-platform challenge was animation performance: iOS devices use GPU-accelerated animations natively, while Android does not, requiring attention to visual consistency. Once stable on physical devices, the iOS build was released to TestFlight for beta.

Both app stores rejected the first submission. The reason: app privacy data declarations did not accurately reflect how the app handled data under the hood. This was not a simple fix. It required auditing every data collection path, third-party sharing relationship, and tracking mechanism across the codebase.

To resolve this, Dylan built a team of specialized AI compliance agents focused on legal compliance, state and federal regulations, and Apple/Google platform policies. These agents audited the codebase, data handling practices, and privacy declarations systematically, ensuring alignment with all current and upcoming laws. This approach resolved both store rejections and resulted in successful resubmission.

One other significant pre-ship decision: the Spotify integration model was fundamentally rethought. The original plan (linking personal Spotify accounts to access actual listening data) carried compliance risk under Spotify's Terms of Service. The pivot: use the Spotify Web API to let users search for and add favorite artists to their profile manually. Full legal compliance, delivered. Less automated data, but a tradeoff worth making.

Synceria shipped as a fully functional music-based dating app on both the Apple App Store and Google Play Store, built from concept to launch in approximately one year by a two-person founding team where one person handled all execution. The shipped product includes: Spotify Web API integration for music data, genre-based vibe rooms, a swipe-and-match system with like tiers, real-time chat via Stream Chat, and a three-tier subscription model (GA, VIP, AllAccess).

As a just-launched app with no marketing spend yet, early download and engagement numbers are not the story. The meaningful outcome is the artifact itself: a fully functional, cross-platform music-dating app with genre-based matching, real-time chat, and subscription infrastructure. Researched, designed, built, and shipped by one person in one year, surviving two complete rebrands along the way.

What this proves: frontend design and full-stack development have always been Dylan's strongest areas, but Synceria demonstrates something broader. Having personally executed every role in a product lifecycle (researcher, strategist, UX designer, visual designer, frontend engineer, backend engineer, QA tester, compliance auditor, and launch operator) creates genuine empathy and understanding for every team member's challenges. This isn't theoretical knowledge. It is proven by a live, shipped production product.

The strongest lesson from the year: give yourself enough time to do the job correctly. The original target was a 3-month timeline. That estimate was quickly proven unrealistic, not because the work was harder than expected, but because every stage of the lifecycle takes real time, and rushing through any of them means cutting corners that surface as problems later. The decision to extend to a full year was the right call.

The technical architecture decisions made early in the project proved durable. Choosing Supabase with row-level security meant data isolation was enforced at the database layer rather than relying on application code, which simplified the security audit significantly. The decision to use RevenueCat for subscription management instead of building payment infrastructure from scratch saved weeks of development time and eliminated an entire class of compliance concerns. Stream Chat handled the complexity of real-time messaging, letting the focus stay on the matching algorithm and user experience rather than WebSocket infrastructure.

Building as a solo developer also shaped how decisions were made under pressure. Every tradeoff was immediate and personal: choosing to invest time in the compliance agent system rather than patching individual store rejections, pivoting the Spotify integration model when the legal risk became clear, and committing to physical device testing over simulator-only QA. These were not theoretical product management exercises. They were real decisions with real consequences on a live timeline, made by the same person who would then implement the outcome.

The two rebrands mid-development (Vibin' to SSYNC to Synceria) tested more than patience. Each rename required propagating changes across the codebase, rebuilding app store listings, updating domain strategy, regenerating marketing assets, and re-verifying compliance documentation. What could have been a derailing setback instead became a process lesson: decouple brand identity from deep infrastructure early, because names change but architecture should not have to. That resilience now informs how every future project gets structured from day one.

Looking forward, the next chapter for Synceria is growth: marketing strategy, user acquisition, and iterating on the matching algorithm based on real usage data. The infrastructure is built to scale. PostHog analytics and Sentry crash reporting are already integrated, providing the observability layer needed to make data-driven product decisions as the user base grows. The foundation is not just a launched app. It is a platform ready for its next phase.