0
Loading
Back to Works
Case Study
2023

Quova

Empowering users with a customizable biolink tool. Scalable and user-centric.

Quova

Role

Full Stack Development

Client

Internal Project

Stack

Next.jsPostgreSQLStripeCustom Auth

The Vision

Quova was created to give users control over their digital landing page. In the age of "link in bio," we wanted to offer a tool that went beyond simple lists—a full biolink solution with deep customization options. We noticed that existing solutions were either too simple (Linktree) or too complex (Carrd). Quova aimed to sit perfectly in the middle: easy to use but powerful enough to express individuality.

Engineering the Platform

Similar to Termed, Quova required a robust backend to handle user data and customization settings. We utilized a stack centered around Next.js and PostgreSQL, implementing a custom authentication system to ensure total control over user security.

The Quova landing page

We integrated Stripe for premium features and used an S3 CDN to handle user-uploaded assets. Optimizing image delivery was a significant challenge; we implemented on-the-fly image resizing and compression to ensure that profiles loaded fast regardless of how much high-resolution content a user added.

Custom Authentication

Instead of relying on off-the-shelf auth providers, we built a custom solution using secure HTTP-only cookies and JWTs. This gave us granular control over session management and allowed us to implement features like "impersonation mode" for support purposes securely.

Evolution

The platform evolved significantly during its lifecycle. Early versions focused on core functionality, but as we iterated, we added rich customization tools that allowed users to truly make their profiles their own. This included custom CSS support, animated backgrounds, and integration with third-party widgets like Spotify and SoundCloud.

Legacy

Quova was a success, attracting 500+ users and generating over 90,000 total views. It was a fun, challenging project that pushed our skills in building user-centric applications. The feedback loop with our users was tight; we shipped features weekly based on their requests.

Note: While Quova has ended, the lessons learned here are fueling a potential successor currently in the works. Watch this space.

Next Case Study

Slain

Start Project