Skip to content
LANGOLF DIGITAL
All work10 / 15
CREATIVE2026

Icarus Adrian

A music and artist experience around audio, identity, and content

A digital music and artist site combining audio playback, music visualization, songs and lyrics, artist content, a newsletter, and a small admin experience.

Status
Functional Prototype
Category
CREATIVE
Year
2026
Primary stack
Next.jsTypeScriptTailwind CSS
Icarus Adrian music platform visualization

Project visualization — a designed representation, not a literal screenshot

01Overview

What this is

A digital music and artist site combining audio playback, music visualization, songs and lyrics, artist content, a newsletter, and a small admin experience.

Explores

  • Audio playback
  • Music visualization
  • Songs
  • Lyrics
  • Artist content
  • Newsletter
  • Admin experience
  • Responsive media UX

02Explore the build

The demo and the build insight

The demo

External application

ENTER THE BUILD

The public Icarus Adrian build — audio playback, songs, lyrics, and the artist experience, live on Vercel.

ENTER THE BUILD

Build insight

01 / 04
Current build
Functional Prototype
Architecture and features below are the real build.
Demo
External
Launch control above opens the verified public build.

Build insight — real project data, not a live application.

Media is modeled as structured content — songs, lyrics, and artist pages — which is what makes the admin surface possible. Playback and visualization are the presentation layer over that library.

03Problem · opportunity

What it sets out to solve

An independent artist needs a place that feels like them — somewhere audio, visuals, and biography live together, where fans can listen, read lyrics, sign up for updates, and the artist can manage content without a web team.

04Concept

The core idea

One intentional media surface: playback and music visualization as the centerpiece, songs with lyrics alongside artist content, a simple newsletter path, and an admin surface the artist actually uses.

05What I built

What's actually in the code

A functional prototype of the artist experience: audio playback, music visualization, songs with lyrics, artist content, newsletter capture, and an admin experience that manages the media library.

Approach

Building the public media experience around an audio engine and music visualization, with songs, lyrics, and artist content modeled as data the admin can edit. Newsletter capture and the admin experience are scoped as part of the same product rather than afterthoughts.

06Key features

What's implemented today

  • Audio playback experience with visualization
  • Songs and lyrics presentation
  • Artist content and identity surfaces
  • Newsletter capture flow
  • Admin experience for managing the media library
  • Responsive media-first layout

07Architecture

How it's structured

architecture.md

Media is modeled as structured content — songs, lyrics, and artist pages — which is what makes the admin surface possible. Playback and visualization are the presentation layer over that library.

Design notes

No streaming or audience metrics are claimed; the site is in functional-prototype stage. Audio-visual interplay is prototyped to be intentionally modest.

08Technology

The stack

  • Next.js
  • TypeScript
  • Tailwind CSS
  • Web Audio (planned)

09Challenges · lessons

Where it got hard, and what it taught me

Challenges

  • Building an audio experience that feels designed rather than technical
  • Separating the media library (data) from the playback (presentation) cleanly
  • Keeping an admin surface simple enough that an artist wants to use it

Learnings

  • Structuring songs and lyrics as data pays off the moment an admin exists
  • Visualizers earn their place when they reinforce the music, not distract from it
  • A tight scope — listen, read, subscribe — is the right scope for a first artist site

10Current status

Where this project sits today

Functional Prototype2026

Core features are engineered and demonstrable. Not yet production-hardened or deployed to real users.

Demonstrated

  • Functional prototype: playback, songs/lyrics, content, newsletter, and admin flows run

11What comes next

Where this goes from here

  1. 01Add real audio content once cleared for use
  2. 02Harden the admin experience for a non-technical user
  3. 03Connect newsletter capture to a mailing provider