Timeline-Native Experiences

Games, predictions, challenges, and social mechanics inside the timeline.

ThreadPlay is the lab. Battle Dinghy is the first artifact. The broader category is timeline-native UX: experiences that use the thread itself as interface, state, distribution, and spectator surface.

Timeline-native social game interface with turns, predictions, challenges, and live state panels

Category Thesis

The timeline can be more than a feed.

Social platforms already contain identity, distribution, conversation, rivalry, spectators, status, and asynchronous turn-taking. ThreadPlay treats those as product primitives.

Problem

Most social games ask users to leave the conversation.

That creates friction. The interesting question is what works when the board, move, challenge, prediction, and audience stay inside the thread.

Idea

The thread becomes the interface layer.

Replies can become moves. Posts can become game-state updates. Spectators can react, predict, challenge, and enter the loop without installing another app.

Umbrella

ThreadPlay

A lab for timeline-native experiences: games, predictions, challenges, wagers, and social mechanics designed to run directly inside platforms like X.

Timeline UXSocial mechanicsHigh priority
Flagship

Battle Dinghy

A Battleship-style timeline-native strategy game. The public page should explain the rules, challenge flow, board state, and why the thread is both game surface and distribution channel.

Game statePublic playFirst demo
Mechanics

Predictions, challenges, wagers

ThreadBookie and related concepts should lead with prediction and challenge mechanics before betting language. The point is market-like interaction inside social context.

PredictionsChallengesWagers
Simulator layer

X Simulator / ThreadPlay Simulator

These repos support interaction testing: posts, replies, turn markers, board embeds, spectators, and persistent public state.

UX testingPrototype surfaceConsolidate

Next Build Pass

Create two focused public subpages.

  • ThreadPlayExplain timeline-native UX as the category and lab.
  • Battle DinghyShow rules, board state, challenge flow, and example thread screenshots.
  • Content loopUse small posts: “the thread is the board,” “replies as moves,” “spectators as mechanics.”