graystack

Projects / Pulse

03 · UI/UX · Concept study · 2025

pulse

Social media at the speed of attention.

A calmer social app: one post at a time, reactions that take a beat, a feed you can finish, and notifications that arrive in digests instead of a drip. Designed and built end to end, from brand to working app.

Role
Product design, brand, front-end
Platform
Mobile web app, phone first
Built with
HTML, CSS, vanilla JavaScript
Status
Concept study · fully working demo

01 / The problem

Most feeds are built so you never leave.

Social apps compete for time, so they're designed to be hard to put down. Pulse asks the opposite question: what would a social app look like if it were designed to let you leave, and feel good about it?

Infinite feeds

There's no bottom, so there's never a natural moment to stop.

Drip-fed notifications

Every ping arrives on its own and pulls you back in, one at a time.

Likes as scores

Counting reactions turns sharing into performing.

A concept study, honestly framed. Pulse is self-initiated, not a shipped product, and there was no formal user research. The design starts from five principles and ends with the assumptions a real study would need to test.

02 / Principles

Five rules, built into the product.

Each principle is a real feature in the app, not a setting buried three screens deep.

1

One post, full attention

The feed moves a page at a time and snaps to each post. A small bar shows how far through today you are, so the end is always in sight.

The Pulse feed showing one post and a progress bar
2

Reactions take a beat

A like lands after a short pulse, about a third of a second. It's just long enough to make reacting a choice rather than a reflex. Try it:

A post with its comments sheet open
3

You can be caught up

A daily limit of 12 posts (6, 12 or all, your choice) ends in a real stopping point, not a spinner. The inbox caps new conversations at three a day.

The caught-up screen
4

Notifications in digests

Activity arrives bundled, twice a day by default, so nothing interrupts you on its own. Even reactions to your own posts wait for the next digest.

The activity digest
5

Your pace, your rules

Hide like counts, set quiet hours, change the digest, or switch between Day and Night. The defaults are calm; the controls are yours.

Pulse settings

03 / Brand

Warm paper, quiet ink, one ember.

Pulse needed to feel like the opposite of a slot machine: soft surfaces, a bookish serif for its voice, and a single warm accent reserved for the moments that matter, like the beat of a like.

The Pulse app icon: an ember dot with two soft rings on dusk blue

App icon · the ripple

Palette · Day

Paper#F5F1EA
Ink#221E1A
Ember#E2553D
Glow#F8DDD0
Sage#6F8F78
Dusk#2B3047

Palette · Night

Paper#17161A
Ink#F2EEE8
Ember#FF7A5C
Glow#3A2421
Sage#9CBAA3
Card#211F24

Typography

Aa

Fraunces, 600The voice: headings, the wordmark, story text, the caught-up message.

Aa

DM Sans, 400 to 700The reading face: captions, buttons, settings, messages.

Motion

The beat · 380msSqueeze, swell, settle. Then the like lands.
Breathe · 3.2sThe wordmark's dot, slow enough to calm.
Ripple · 3sThe caught-up moment: a pulse that fades out.

Imagery

Generated, not stock.

Every image in Pulse is drawn by code from a seed: dunes, orbits, blooms, tides, type specimens. They load instantly, never need licensing, re-colour for Night, and give a fictional community a consistent, gallery-like look.

Dune: layered sand hills under a low sun
Dune
Bloom: a violet flower of overlapping petals
Bloom
Tide: drifting blue-green wave lines
Tide
Bloom in the ember palette
Bloom · ember

04 / Screens

Sixteen screens, all real.

Every image here is a capture of the working app, not a mockup. Tap any screen to see it larger.

First run

4 screens
WelcomeOne promise, one button. The ripple mark breathes in the background.
Three quiet rulesThe product explains its own limits before you meet them.
InterestsUsed to explain why a post is in your feed, never to rank you.
FeedOne post per page, a reason chip, and today's progress.

Stories and conversation

4 screens
StoriesTap to skip, hold to pause, reply privately.
CommentsA sheet over the post, so you never lose your place.
InboxCapped at three new conversations a day.
MessagesSimple threads, with replies that arrive like a person typing.

Discover and create

4 screens
DiscoverPeople, tags and posts in one search.
ProfilesFollow, message, and browse someone's posts.
ComposeWrite, pick a canvas and palette, preview, share.
Caught upThe end of the feed is a feature, not an error.

Control and Night

4 screens
ActivityBundled into digests at the times you choose.
SettingsDaily limit, like counts, quiet hours, digest, theme.
Text posts at nightWords get the full card, set in the brand serif.
NightA warm dark theme, not an inverted one.

05 / Try it

The real thing, running right here.

This is the complete app, not a video. Everything you do is saved in your own browser, so your posts and likes are still here when you come back. Nothing is sent anywhere.

Things to try

  1. 1

    Finish onboarding. Pick three interests and choose a handle. Try one that's taken, like theo.makes.

  2. 2

    Like a post, then double-tap one. Feel the beat before the like lands.

  3. 3

    Open a story. Tap to skip, hold to pause, and send a reply.

  4. 4

    Read to the end of the feed. Watch the progress bar fill, then get caught up.

  5. 5

    Post something. Choose a canvas and palette, add a #tag, and find it in your feed and on your profile.

  6. 6

    Message someone. They'll write back after a moment.

  7. 7

    Change the rules. Hide like counts, lower the daily limit, or switch to Night in Settings.

Best on a phone: open Pulse full screen and add it to your home screen. To start over, use Settings → Reset.

06 / How it's built

No framework, no backend, no stock photos.

Pulse is deliberately small: one HTML file, one stylesheet, one script. Small enough to read in an afternoon, complete enough to use.

  • ~1,060lines of JavaScript, no dependencies
  • 16screens and states, from onboarding to reset
  • 7artwork generators drawing every image from a seed
  • 0bytes sent to a server: data stays in your browser
  1. A hash routerEvery screen has its own address (#/feed, #/u/ana.draws, #/post/p3), so links, the back button and shared posts all work.
  2. One state objectPosts, follows, messages and settings live in one object saved to localStorage after every change. Reset wipes it cleanly.
  3. Delegated eventsOne listener per event type handles every button through data attributes, so re-rendering a screen never leaks handlers.
  4. Seeded artworkImages are SVG drawn from a seed and a palette: the same post always looks the same, and Night simply swaps the palette.
  5. Accessible by defaultReal buttons and links, labelled icons, visible focus, a live region for confirmations, and reduced motion respected throughout.
app.js · the beatView source
// A like takes a beat: the heart pulses, then the like lands.
function like(id, fromMedia) {
  const post = postById(id);
  if (!post || pendingLikes[id]) return;
  if (fromMedia && post.liked) { burst(id); return; }
  pendingLikes[id] = true;
  likeButtons(id).forEach(function (b) {
    b.classList.remove("is-beat");
    void b.offsetWidth;
    b.classList.add("is-beat");
  });
  if (fromMedia) burst(id);
  window.setTimeout(function () {
    delete pendingLikes[id];
    post.liked = !post.liked;
    post.likes += post.liked ? 1 : -1;
    save();
    updatePostButtons(id);
    likeButtons(id).forEach(function (b) { b.classList.remove("is-beat"); });
  }, reducedMotion.matches ? 0 : 380);
}

07 / What I'd test next

The assumptions a real study would check.

Pulse makes bets about how people want to feel. Before building further, each one deserves a test with real users.

Does a daily limit feel calming or restrictive?

Some people may love a stopping point; others may feel shut out of their friends' posts.

Test: diary study over two weeks
Does the beat feel intentional or laggy?

380ms is a guess. Too short and nobody notices; too long and it feels broken.

Test: A/B the delay at 0, 250, 380 and 600ms
Would a capped inbox frustrate close friends?

The cap protects attention but might need an exception for people you choose.

Test: interviews after a week of use
Do digests reduce checking, or just move it?

Bundling should lower the urge to open the app; it might just create two daily spikes.

Test: compare app opens per day, before and after