Menu
GitHub LinkedIn
Back to projects

SYNCD

Keeping the interface in sync.

An early-stage startup for local events, built outside our classes and jobs. I built its interface in Next.js and TypeScript, with API updates in Ruby on Rails.

At a glance

  • Software engineerThe Next.js interface and Rails API updates for a local-events startup
  • BeforeA team API that kept changingAfterAn interface kept in step
    • Next.js
    • TypeScript
    • Rails
  • Feed, event card, create form, profile tabs.
  • Event dates normalized and grouped.
  • Built with a PM at Google and a developer at Spring Health.
SYNCD · Keeping components in step with the API
  1. Rails API — PostgreSQL
  2. Create event — form + date picker
  3. Data shaping — starts_at → ISO → grouped by date
  4. Profile tabs — Followers · Following · Syncs
  5. Discover feed — event cards
  6. Event card — details and actions

The story

The team

SYNCD was an early-stage startup for local events. I joined as a founding member and software engineer, building it outside our classes and jobs with a product manager at Google and a developer at Spring Health.

The problem

The team's API kept changing as the product took shape, and the interface had to keep up.

What I built

I built the interface in Next.js and TypeScript (the discover feed, event card, create-event form and profile tabs) and made API updates in Ruby on Rails.

Keeping in step

As the API changed, I kept the interface in step: event dates normalized and grouped, and each screen updated to match.

The code is private. I'm happy to walk through it.