Skip to content
View lets-go-app-pub's full-sized avatar

Block or report lets-go-app-pub

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Please don't include any personal information such as legal names or email addresses. Maximum 250 characters, markdown supported. This note will be visible to only you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
lets-go-app-pub/README.md

Lets Go — Portfolio Overview

I co-founded and built the product for a two-person startup for ~3 years. I owned the software side end-to-end while my partner ran the business (operations, sales, customer development). This page highlights the architecture and links to the key repositories.

What the app is

A mobile app for meeting people to do activities together. Think swipeable match cards, but focused on shared activities, timeframes, and lightweight privacy (built-in chat so you can coordinate without sharing personal info). The system also supports Events—sponsored or community activities that appear as their own cards and drop you into a related chat room if you opt in.

How it works (user view)

  1. Pick activities & a timeframe (e.g., Pick-up Basketball this weekend, Sushi tonight, Hiking next week).
  2. Set preferences (distance, categories, availability).
  3. Get match cards generated by a server-side matching engine (activity/category overlap, time windows, recency/inactivity rules).
  4. Swipe Yes/No on each card; on a Yes, a chat room is available so you can coordinate without exchanging personal details.
  5. Discover Events presented as cards; a Yes opens the event chat and shows the relevant info.

Activities & categories (samples)

  • Pick-Up Sports: Basketball, Soccer, Volleyball
  • Food: Brunch, Sushi, Mexican
  • Adventures: Hiking, Boating, Skiing
  • Social Drinking & Tastings (21+): Beer, Wine
  • DIY & Personal Development: Home Care, Investing & Finances
  • Video Games: FPS, Racing, MMORPG
See the complete activity list.
  • Pick-Up Sports: Baseball, Basketball, Football, Golf, Hockey, Pickleball, Soccer, Ultimate Frisbee, Volleyball
  • Working Out: Crossfit, Cycling, Dance, MMA, Pilates, Running, Swimming, Weight Training, Yoga
  • Food: American, Brunch, Chinese, Indian, Italian, Mexican, Pho, Sushi, Thai
  • Adventures: Band Jam Session, Bar Hopping (21+), Boating, Clubbing (21+), Dancing, Hiking, Shopping, Skiing, Snowboarding, Water Activities
  • Social Drinking & Tastings (21+): Beer, Spirits, Wine
  • Beauty: Hair, Makeup, Mani Pedi, Skin Care
  • Board Games: Catan, Checkers, Chess, Dominoes, Dungeons & Dragons, Monopoly, Pictionary, Scrabble
  • Collectable Card Games: Magic The Gathering, Pokemon, Yu-Gi-Oh!
  • Concerts: Country, EDM, Hip-Hop, Indie, Jazz, Oldies, Pop, Rap, Rock
  • DIY: Cars, Home_Care, Refurbish Items, Restore Antiques
  • Movies & TV: Action_Adventure, Comedy, Drama, Reality TV, Thriller_Suspense
  • Personal Development: Emotional, Intellectual, Investing & Finances, Relational
  • Play Dates (18+): Board Games, Crafts, Fun-In-The-Kitchen, Movies, Outings, Park-Day
  • Poker: 5 Card Draw, 7 Card Stud, Blind Man's Bluff, Omaha Hold'em, Texas Hold 'em
  • Sporting Entertainment: Baseball, Basketball, Boxing, Football, Golf, Hockey, MMA, Soccer, Tennis
  • Video Games: Battle Royale, Digital Card Games, FPS, MMORPG, MOBA, Racing, Sports

Lets Go Architecture

Highlights (skim me)

  • My role: system design, backend (C++), Android (Kotlin), matching engine, integrations, server administration, deployment docs.
  • Architecture: stateless C++ Application Server (gRPC/Protobuf) with MongoDB.
  • Matching: Mongo aggregation pipeline + C++ converter for embedded execution and speed.
  • Clients: Android app for end users and a Desktop Admin Interface (Qt) for moderation/ops and event tools.
  • Integrations: SMS + Email providers for notifications and verification as well as account flows.

Highlighted Repositories

  • Server (C++) — stateless hub, gRPC/Protobuf, MongoDB
    👉 Lets_Go_Server

  • Android Client (Kotlin) — auth, profiles, activities, chat (SDK versions may be dated)
    👉 Lets_Go_Android_Client

  • Desktop Admin (Qt) — admin/ops console for moderation, events, stats, and controls
    👉 Lets_Go_Interface

  • Matching (Algo & Converter) — Mongo aggregation (JS) + C++ converter to embed pipelines
    👉 Lets_Go_Algorithm_And_Conversion

  • Protobuf Files — protobuf files used to communicate between server and clients
    👉 Lets_Go_Protobuf

  • Docs & Deployment Notes — release checklists, SSL testing, Mongo RS commands
    👉 Lets_Go_Docs

What I did

  • Architecture & backend: designed the system, authored most server code, defined gRPC/Proto contracts.
  • Data & matching: wrote aggregation pipelines and the C++ converter to run them efficiently server-side.
  • Android: implemented core UI/flows (auth, profiles, activities, chat).
  • Admin interface: contributed features and workflows used for moderation and operations.
  • Server administration: provisioned Linux hosts, configured system services, SSL/TLS, backups, and monitoring; operated a MongoDB replica set across separate nodes.
  • Integrations: wired SMS and Email providers for notifications and account flows.

Status & scope

  • Active development ~3 years.
  • The company is sunset, and this code is provided for anyone that it may have value to as well as for portfolio purposes.
  • Tooling notes: Android project targets older SDKs; the Desktop Admin uses Qt (modern builds may require current Qt tooling/licensing).

Tech at a glance

C++ · gRPC · Protobuf · MongoDB (Replica Set) · Android (Kotlin) · Qt · Aggregation Pipelines · SSL/TLS · Gradle/CMake · Linux Server Ops · Wordpress

Pinned Loading

  1. Lets_Go_Server Lets_Go_Server Public

    App service/server that works as central hub for other major components.

    C++

  2. Lets_Go_Android_Client Lets_Go_Android_Client Public

    App Android client.

    Kotlin

  3. Lets_Go_Interface Lets_Go_Interface Public

    Interface for administration of app.

    C++

  4. Lets_Go_Protobuf Lets_Go_Protobuf Public

    Protobuf files to communicate between server/service and other nodes.

    CMake

  5. Lets_Go_Docs Lets_Go_Docs Public

    Documentation for various parts of the app.

    HTML