Full-Stack Developer for Dating Platform

$25-50 USD / hour

Posted 1 minute ago

•

Ends in 6 days

$25-50 USD / hour

Aphrodite is a dating platform only for students of the our pilot university. It deliberately does the opposite of Tinder, Bumble and Hinge: 1) no swiping and no endless catalogue. Students get a few curated matches ("drops") twice a week. 2) Skip-to-offline: When two students are both interested, the app offers 3 date slots at partner venues on or near campus. One shared choice books the date. 3) Desired Metric: time-to-offline, not screen time. What you will build (MVP scope) 1. Sign-up restricted to campus identity provider: only university addresses, with email verification. 2. Profile card (signals over photos): name, age (16–99), study program (fixed catalogue of ~29 Bachelor, Master and PhD programs), gender, interested in, "Looking for", 3–5 values and 3–10 interests from fixed lists, career aspirations (max 500 characters). Guided onboarding wizard plus an edit screen. 3. Matching drop: an algorithm scores pairs on study program and on the overlap of values and interests, with configurable weights. Drops run on a manual trigger for the MVP. Students aged 16–17 are only matched with each other, never with adults. 4. Date booking: on mutual interest, both students see 3 slots (date, time, partner venue). The first shared choice books the date into an in-app calendar. 5. Presence check: a bilateral QR scan during the booked slot confirms that both showed up. No location tracking. 6. No-show and cancellation policy: a no-show triggers a 1–2 week lockout. Cancelling more than 6 h ahead is free twice per semester; the third cancellation triggers a lockout. Cancelling less than 6 h ahead counts as a no-show. 7. Semester-end deletion of personal data. 8. Mobile-first web app (PWA-ready), accessible (WCAG AA), light and dark mode. Expected tech stack We have a preferred stack. Well-argued alternatives are welcome in your proposal. - Backend: Java 25, Spring Boot 4, Spring Modulith (modular monolith with modules such as identity, profile, matching, booking, venue, presence, policy), Gradle (Kotlin DSL) - API: API-first with OpenAPI 3.1; server interfaces and the TypeScript client generated from the spec - Database: PostgreSQL only (one schema per module, Flyway migrations). No Redis, no message broker. - Identity: Keycloak (custom login theme, email verification, domain restriction, IDP Integration) - Frontend: React + TypeScript (Vite), React Router, TanStack Query, `oidc-client-ts`, CSS Modules with design tokens - Testing: JUnit + Testcontainers + module boundary tests; Vitest, Testing Library, MSW, Playwright and axe; at least 80 % line coverage - Delivery: Docker Compose for local runs (app, Postgres, Keycloak, local mail catcher); CI on GitHub Actions; images in GHCR Profile: Must have - 2+ years of professional full-stack experience, with production Spring Boot and React work - Solid OAuth2 / OIDC experience, ideally with Keycloak (themes, realm configuration) - Comfortable designing relational data models and writing scheduled or batch logic (matching drops, lockouts) - Privacy by design: you know what data minimisation means in practice. Familiarity with Swiss revDSG or GDPR is a strong plus. - Writes tests as part of the work, not after it - Fluent written English Profile: Nice to have - Experience with Spring Modulith or other modular-monolith setups - Matching, recommendation or scheduling algorithms - Accessibility (WCAG) and mobile-first UI - Experience building consumer apps for students or young adults How we work with you - Work is organised as user stories in Jira with acceptance criteria. Each story is delivered as one pull request on GitHub. - Every PR maps each acceptance criterion to evidence (test, screenshot or manual check) and is reviewed by our team. - Technical decisions are recorded briefly in Confluence (ADRs for decisions, short technical design notes for new data or APIs). - Only synthetic test data. No real student data at any stage (besides production). - New dependencies, external services or costs are agreed with us before you add them. - Weekly 30-minute check-in with the product owner; async the rest of the time. Deliverables - Source code in our GitHub repository, with a green CI build and CD Integration - Short documentation: architecture overview, how to run, Feature Descriptions, ADRs, TDRs (all in Jira / Confluence)

Project ID: 40823071

About the project

48 proposals

Open for bidding

Remote project

Active 3 secs ago

Place your bid

Bid amount Email address

Benefits of bidding on Freelancer

Set your budget and timeframe

It's free to sign up and bid on jobs

48 freelancers are bidding on average $31 USD/hour for this job

User Avatar
Flag of UNITED STATES

Hi, I am Elias from the sunny state of Florida. I understand that your goal is to create a dating platform exclusively for students at your university, emphasizing a safe and engaging environment. This unique user base requires a tailored solution that balances functionality with usability. To achieve this, I would use JavaScript and TypeScript for the front-end, ensuring a responsive design suitable for both web and mobile applications. The backend can be structured for scalability, possibly leveraging Node.js, which allows for efficient handling of user interactions and real-time features. Implementing robust authentication will be crucial to ensure user privacy and security. A few questions to clarify the scope: Q1 – What specific features do you envision for user profiles and messaging systems? Q2 – Are you considering any third-party integrations, such as social media logins or payment systems? Q3 – What is your timeline for launching the platform? I’m excited about the opportunity to work on a project that fosters community among students. Looking forward to hearing from you.

User Avatar
Flag of INDONESIA

Hi there, I’m excited by your vision for Aphrodite—a thoughtfully curated, campus-exclusive dating platform that values meaningful offline connections over screen time. Your emphasis on privacy, data minimization, and accessibility resonates strongly with my approach to building modern web applications. With over three years of hands-on experience delivering full-stack solutions using Spring Boot (including modular architectures), React, and TypeScript, I am comfortable designing robust, secure, and user-friendly systems. I have implemented OAuth2 and OIDC flows with Keycloak, including custom login themes, domain-restricted sign-ups, and email verification, ensuring only eligible students can access the platform. My expertise covers designing normalized relational data models in PostgreSQL, implementing scheduled and batch logic for matchmaking, and enforcing nuanced business rules such as age-based pairing and attendance policies. I am meticulous in integrating privacy by design—complying with GDPR and similar standards—and always prioritize test coverage and accessibility (WCAG AA) in both backend and frontend code. For your MVP, I’d propose an API-first approach, collaborative documentation, and evidence-driven pull requests, aligning fully with your workflow. I’d leverage your preferred stack throughout, delivering a PWA-ready, mobile-first experience with light and dark themes. Each feature would be developed iteratively, with traceable decisions and clear documentation in Confluence and Jira. I look forward to collaborating closely with your team to deliver a secure, delightful, and impactful platform for students. Best Regards

User Avatar
Flag of UNITED KINGDOM

Hi there, Building a high-security, privacy-first dating platform like Aphrodite requires deep architectural discipline, especially when enforcing strict domain boundaries like minor segregation, campus-only identity checks, and automated date-booking logic without relying on unnecessary message brokers or external complexity. The common risk in building modular monoliths with complex state transitions, such as bilateral QR presence checks and strict penalty lockouts, is tightly coupling database schemas and business logic across domains, leading to fragile migrations and failing module boundary tests. My solution is to leverage Java 25, Spring Boot 4, and Spring Modulith to strictly enforce database schema separation per module with Flyway, paired with a bulletproof React and TypeScript PWA frontend that guarantees WCAG AA compliance and seamless OIDC session handling. Here are my questions regarding your setup: 1. Are the Keycloak realm configurations and custom login themes already designed, or will I be setting up the IDP integration and custom themes from scratch? 2. Do you have a preferred scoring weight matrix in mind for the initial matching drop algorithm, or should I implement a configurable baseline using values and study programs? Drop me a message so we can get started right away!

User Avatar
Flag of PAKISTAN

Hello, Live Experts combines over a decade of technical delivery experience with React, Node.js, PostgreSQL, Docker, cloud APIs and system integrations, strong foundations for building Aphrodite’s mobile-first platform and its privacy-conscious data flows. Our team has completed hundreds of projects for startups, businesses and enterprises, delivering production-ready software and operational platforms rather than isolated prototypes. JavaScript and React support the PWA-ready frontend, while PostgreSQL and Docker align with your preferred architecture and local development needs. Our experience with dashboards, business platforms, automation and integrations is relevant to configurable matching logic, scheduling, booking workflows, QR-based presence confirmation and policy handling. We also prioritise clean UI/UX, reliable integrations, maintainability and clear communication, which fits your Jira, GitHub PR and documented technical-decision process. Live Experts can deliver a robust MVP focused on moving students from curated matches to real offline dates, and I invite you to choose us to develop Aphrodite. Thanks!

User Avatar
Flag of NETHERLANDS

Hey, Building a dating platform focused on minimizing screen time rather than maximizing engagement is a refreshing product direction, and implementing this with a clean modular monolith architecture using Spring Modulith and React ensures maintainability from day one. I have extensive production experience building full-stack applications with Spring Boot and React, along with hands-on expertise configuring Keycloak for OIDC authentication and designing strict relational data models in PostgreSQL with Flyway. I also prioritize test-driven development, writing unit and integration tests alongside business logic to maintain high code coverage. For this MVP, I would approach development by strictly separating the modules such as identity, profile, matching, and booking to ensure clear boundaries and straightforward Flyway migrations per schema. I will implement the matching drops using scheduled batch logic with configurable weights, enforce the strict age segregation for minors, and set up the bilateral QR scan presence check alongside the cancellation policy rules. I can start as soon as I have access to the GitHub repository and the OpenAPI specification. Which matching weight criteria should take initial priority for the first pilot student cohort? How would you prefer to handle the initial seed data for the campus partner venues and available date slots?

User Avatar
Flag of PAKISTAN

Hello, Aphrodite’s focus on curated matching and time-to-offline creates a thoughtful alternative to engagement-driven dating products. I can approach the MVP around clear module boundaries, privacy-by-design data handling, strong acceptance-criterion evidence, and an accessible mobile-first experience. A useful improvement would be to formalize matching, eligibility, cancellation, and lockout rules as versioned domain policies so they remain auditable and easy to adjust between semesters. The delivery process should also keep synthetic-data environments and automated accessibility checks central from the first story. Regards,

User Avatar
Flag of MEXICO

Fernando from Mexico here. What I find particularly interesting about Aphrodite is the focus on getting students offline rather than keeping them endlessly engaged with an app. That product philosophy should shape the matching, booking, and presence flows from the beginning. I'd approach the MVP as a modular application, keeping identity, profiles, matching, booking, and attendance clearly separated. The matching logic needs particular care: configurable scoring, controlled drop generation, and strict age-group isolation. Booking also needs reliable handling of simultaneous choices, cancellations, and no-show policies. I'd prioritize privacy, accessibility, and automated testing alongside development, not as final cleanup. Your API-first approach, generated TypeScript client, synthetic test data, and PR-based delivery process make sense for maintaining a reliable codebase. Before estimating the implementation properly, I'd like to understand the current repository and which modules are already started. I'd also clarify the university identity provider integration, as this affects authentication architecture. Fernando

User Avatar
Flag of PHILIPPINES

Hello, The key challenge is to build a secure dating platform that only allows university students to connect, ensuring privacy and user engagement through curated matches and offline meetings. I recommend using Java with Spring Boot for backend development, along with PostgreSQL for the database. My experience includes building scalable applications with these technologies, focusing on secure user authentication and data management. I will implement features iteratively, starting with user authentication and profile creation, followed by the matching algorithm and booking system. My testing will ensure a minimum of 80% coverage and compliance with privacy standards. I’m available to discuss the project timeline and confirm specific requirements for the matching algorithm. Please feel free to reach out to me. I look forward to working with you. Best regards, Billy Bryan

User Avatar
Flag of SERBIA

HELLO, "Matching drops" that lead to real dates - Aphrodite needs carefully controlled matching, mutual-interest booking, and reliable offline attendance rather than another swipe-based dating app. I'll build the MVP as a modular, testable platform, covering university email authentication with Keycloak, guided profiles, weighted matching, age-restricted pairing, date-slot booking, QR presence checks, cancellation rules, and semester-end data deletion. I'll follow your preferred Java/Spring Boot and React/TypeScript architecture, with PostgreSQL, OpenAPI-generated clients, Flyway migrations, and automated tests. One important detail is enforcing the 16–17 age boundary consistently across matching and booking, not just hiding incompatible profiles in the interface. I'll handle implementation, documentation, and CI delivery through individual reviewable pull requests. How will the university identity provider expose student identity and verify university email addresses? I appreciate your consideration and look forward to discussing Aphrodite's MVP. THANKS

User Avatar
Flag of GERMANY

Hello, "Email and Calendar Management" - missed messages and overlapping appointments need to be caught before they disrupt your day. I'll use a structured prioritisation process to separate urgent emails from routine requests, track pending replies and check appointment availability before confirming bookings. I'll handle the workflow from incoming information through follow-ups and scheduling checks, keeping one consistent process so conflicting requests are flagged rather than silently accepted. I should be transparent that I cannot provide a personal past-project anecdote, but I can explain the exact conflict-prevention process I would apply. Would you consider a collaborator based outside the Philippines and India if the availability and working arrangement meet your requirements? Looking forward to working with you. Beate

User Avatar
Flag of AUSTRALIA

Hello, I’d love to help build Aphrodite. The product idea is refreshingly different, and I really like the focus on moving students offline instead of keeping them scrolling. I’ve worked on full-stack products where the main challenge was not just “matching”, but building trust, privacy, and clear user flows around sensitive data. Recently, I built a Spring Boot + React platform with Keycloak login, role-based access, and a guided onboarding flow. I also delivered matching-style logic with relational scoring, scheduled jobs, and strong test coverage using JUnit, Testcontainers, Playwright, and Vitest. On the frontend, I’ve handled mobile-first UI, accessibility improvements, and clean state/data handling with React Query. For Aphrodite, I’d approach the modular monolith carefully, keeping identity, profile, matching, booking, presence, and policy well separated from the start. I’d also make sure the age restrictions, deletion policy, and no-show rules are enforced both in the UI and backend. A couple of questions: 1) Should the matching weights be configurable by admins in the MVP? 2) Do you already have the university identity provider details for Keycloak integration? If helpful, I’d be happy to jump on a call and talk through the architecture. Best regards, Mehreen

User Avatar
Flag of BAHRAIN

Hello, Aphrodite has a clear and interesting goal: helping students move from meaningful matches to real-life meetings instead of encouraging endless app usage. I’d be interested in contributing to an MVP that makes this experience simple, reliable, and privacy-conscious. My background is in web, mobile, and AI engineering, with experience in backend APIs, database-driven applications, and modern application development. I agree with your modular-monolith direction and the importance of keeping identity, matching, booking, and presence logically separated. I would approach delivery through small, testable Jira stories, starting with architecture and identity, followed by profiles, matching, booking, QR presence, and cancellation policies. I would prioritize age-based matching restrictions, data minimisation, automated tests, accessibility, and clear API documentation from the beginning. I’d welcome a discussion about the technical requirements and where my experience would best support your team. Could you share your priorities for the first development milestone? Looking forward to hearing from you!

User Avatar
Flag of MOLDOVA, REPUBLIC OF

Hello. I understand that building a unique dating platform for students presents challenges in creating an engaging and efficient experience. The approach of offering curated matches and a focus on offline interactions stands out, as it prioritizes meaningful connections over endless browsing. I have experience developing a mobile-first application with a similar focus on user engagement and privacy, resulting in a successful product that encouraged real-life interactions among users. I’m particularly attentive to designing a robust matching algorithm that aligns with your specific requirements while ensuring compliance with data privacy regulations. To better understand your needs, could you elaborate on how you envision the user onboarding process and if there are specific features you believe are essential for initial user engagement? Thanks, Artiom.

User Avatar
Flag of UNITED STATES

Hi , How are you? I have a masters' degree and I have a lot of experience in designing and implementing big projects. In addition to that, I have a great deal of knowledge in Typescript, JavaScript, Mobile App Development and Web Application. "Looking for" Please contact me to discuss more regarding this project. Appreciate your prompt response

User Avatar
Flag of CANADA

Hello. I understand that Aphrodite is designed to help university students build meaningful connections through curated matches and real-world meetings, with privacy, safety and reliable scheduling being essential to the MVP. I would follow your preferred Java 25, Spring Boot 4, Spring Modulith, React/TypeScript and PostgreSQL architecture. My approach would start with Keycloak authentication and profile validation, followed by configurable matching, transactional date booking, QR-based attendance and cancellation policies. I would pay particular attention to strict separation of minors and adults, semester-end data deletion, WCAG accessibility and automated regression testing. Each Jira story would include test evidence, documentation and a reviewed pull request. Q1: Is the university identity provider already available for integration testing? Q2: Should the matching algorithm enforce additional eligibility rules beyond age and stated preferences? I'd be glad to review your acceptance criteria and agree on a practical implementation sequence.

User Avatar
Flag of COLOMBIA

HI! IMPORTANT: PRIVACY, USER EXPERIENCE, SCALABILITY. Ensuring a seamless and secure user experience while adhering to privacy regulations is crucial for this project. I have extensive experience implementing OAuth2/OIDC with Keycloak and designing data models that prioritize data minimization, aligning with GDPR standards. To solve this project, I will leverage a modular monolith architecture using Spring Boot, focusing on a clean API design and rigorous testing practices to ensure quality and maintainability. The client will benefit from my proficiency in the preferred tech stack, delivering a robust and user-friendly platform tailored for students. I MISS YOUR RESPONSE! GOOD LUCK!

User Avatar
Flag of UNITED STATES

You want a dating platform that feels smooth, keeps users engaged, and makes it easy for people to connect. The biggest challenge isn't just building profiles and matching features. It's making sure messaging works reliably, personal information stays protected, and the platform can grow without slowing down. About two months ago, I worked on a full-stack project involving React, Node.js, user authentication, database management, and real-time features. One thing I focused on was keeping the frontend responsive while making backend operations reliable. For your project, I'd build a clean, mobile-friendly interface with user profiles, matching preferences, real-time chat, and account management. I'd use React, Node.js, PostgreSQL, and WebSockets where appropriate. I'd also add profile verification options, privacy controls, reporting tools, and an admin dashboard to help manage the platform. Are you starting from scratch, or do you already have a dating website that needs further development?

User Avatar
Flag of GEORGIA

Hello. I like the direction Aphrodite is taking. Getting students offline rather than keeping them scrolling makes sense, and the tricky part is getting matching, booking and privacy rules right without overcomplicating the MVP. I'd stick with your Spring Boot/Modulith and React stack, keeping module boundaries clear and OpenAPI as the contract. Matching drops can run as controlled batch jobs, while PostgreSQL transactions handle booking conflicts and policy enforcement. I'd cover the age restrictions, QR presence checks and semester-end deletion with automated tests, then validate the full journey in Playwright. Q1: Does the university already provide an OIDC/SAML identity provider, or will Keycloak handle verification independently? Q2: Are venue slots managed by Aphrodite or supplied through partner integrations? Happy to work within your Jira/PR process and discuss the first set of user stories.

User Avatar
Flag of SPAIN

Hi there, I see that you are looking to build a dating platform focused on students with specific functionalities like profile cards and a unique matching algorithm. Our team is experienced in developing full-stack applications using Java and React, and we understand the importance of features like OAuth2 integration with Keycloak, as well as ensuring privacy standards like GDPR compliance are adhered to. We're a small team of developers from Germany and the Netherlands, based in Spain, and we take pride in delivering quality work our clients can rely on with complete peace of mind. Our expertise includes working with modular systems such as Spring Boot and we're comfortable implementing relational data models and testing processes. We're ready to discuss your tech stack and suggest optimizations if needed, and we look forward to delivering a solid MVP that meets your needs. Regards, Ali Parandeh IT Director

User Avatar
Flag of BRAZIL

Hello, Aphrodite’s strongest product decision is optimizing time to offline rather than endless engagement, and the MVP needs that principle reflected in dependable matching, booking, presence, and policy flows. The main challenge is coordinating age safe matching, university restricted onboarding, shared slot selection, QR attendance, lockouts, semester deletion, and accessibility without creating inconsistent states or privacy risks. I can contribute Java backend implementation with PostgreSQL schemas and migrations, while JavaScript and CSS support a responsive React experience across onboarding, curated drops, booking, and calendar views. I would structure the work around clear API contracts, transactional booking rules, configurable matching weights, scheduled drop and lockout processing, strict separation of minor and adult matching, and test coverage for cancellation edge cases. The interface would remain mobile first, keyboard accessible, and consistent in light and dark mode. Each user story can be delivered as a focused pull request with acceptance criteria mapped to automated tests or documented checks, using synthetic data throughout. This approach keeps the modular boundaries clear and makes privacy deletion behavior verifiable before production. I would be glad to help turn the pilot into a reliable, focused MVP. Gabriel

内容来自 Freelancer News,版权归原作者所有。

阅读原文 ↗

把喜欢的内容,留在你的新标签页。

打开我的订阅