DEV Community

Cover image for Raat Ka RJ: An Interactive Audio Microdrama – You Decide What Dev Does Next
Sumit Tiwari
Sumit Tiwari

Posted on Edited on

Raat Ka RJ: An Interactive Audio Microdrama – You Decide What Dev Does Next

Raat Ka RJ: An Interactive Audio Microdrama – You Decide What Dev Does Next

An interactive microdrama | 3 choices, 4 endings | Estimated reading time: 5–8 minutes

What if someone sent you a voice note every night at exactly 1:47 AM, but never said a single word?

Would you ignore it, investigate it, or listen closely enough to discover what it was trying to tell you?

I normally write about code, open source, and development. This time, I wanted to experiment with something different: a story where the reader doesn't just follow the plot but actually makes decisions that change how it ends.

The idea came from my interest in radio and the people who stay awake at night listening to voices they've never met.

I've also built UP Radio, a radio app featuring live Uttar Pradesh stations. While working on it, I kept thinking about the connection between a radio host and someone listening on the other side.

That thought became Raat Ka RJ.

This is not a story where you simply scroll from beginning to end. You have choices to make, clues to notice, and different endings to discover.

How to read this story: At every choice, click an option to reveal what happens. Some options lead to dead ends. One path reaches the true ending. Read carefully, because every sound is a clue.


Characters

  • Dev (21): A nervous night RJ at a small campus community radio station, 91.2 FM. His voice shakes whenever he thinks someone is listening.
  • The Listener: An unknown person who sends one voice note every night at 1:47 AM.
  • Bilal (14): A young boy who appears near the end of the story.
  • Khan Saheb: A former radio presenter whose voice has been missing for a long time.

Episode 1: 1:47 AM

A tiny radio studio. Foam panels on the walls. One microphone. A red ON AIR light. The clock reads 1:46 AM.

Dev is alone.

Nobody usually listens to a campus radio show at this hour.

The streaming dashboard says:

3 listeners.

Sound: A quiet hum from the old mixer.

DEV (into the microphone, nervously): Aap sun rahe hain Raat Ka RJ, 91.2 FM. Main hoon Dev. Agar aap jaag rahe hain, toh iska matlab hai ki aap bhi kisi baat ka intezaar kar rahe hain.

At exactly 1:47 AM, his phone buzzes.

A message on the request line.

A voice note. Six seconds long.

No words.

Sound: A ceiling fan turning. A pressure cooker whistle in the distance. And underneath it, something rhythmic: someone tapping slowly on a wooden surface.

Dha, ge, na, ti, na, ka, dhi, na.

Then a text message appears:

"Woh purana gaana laga do. – Ek Shrota"

Dev opens the chat.

The same number has sent this message every night for eleven consecutive nights, always at 1:47 AM.

He has never replied.

He doesn't know which old song the listener means.

The voice note is still playing in his headphones.

For some reason, his chest feels tight.

🎧 Choice 1: What does Dev do?

🅰️ Play a regular song and ignore the message

Dev shrugs, queues a regular song, and finishes the show at 2:00 AM.

The next night, 1:47 AM arrives.

His phone stays silent.

No fan. No cooker. No tapping.

Dev stares at the screen for ten minutes.

The night after that, the same silence.

The number is still saved, but it never sends another message.

Ending 0: The Silence

Some messages only come once. Go back and choose B.

🅱️ Replay the voice note and listen carefully

Dev puts on his headphones again.

This time, he turns down the background music and listens to every second.

Continue to Episode 2 below.


Episode 2: The Rhythm

Dev replays the voice note. Again. And again.

Sound: Fan. Pressure cooker whistle. Eight beats of tapping. Then, at the end, something almost impossible to hear: an old man's breath.

Dev leans closer.

DEV (whispering to himself): Yeh koi gaana baja raha hai. Ungli se. Bed ke frame pe.

He recognises the pattern.

An eight-beat rhythm. The kind of rhythm that old film songs often use.

But he cannot identify the song.

His phone is still open.

He has two options.

He can investigate the number, or he can search the radio station's old archive: a dusty steel cabinet full of cassettes that has been locked since before he joined.

🎧 Choice 2: Where does Dev look?

🅰️ Trace the number

Dev checks the number against the station's caller log.

A name appears on the messaging profile:

Bilal.

No photograph. No address. No other information.

He sends a message:

"Aap kaun?"

Two blue ticks.

No reply.

Dev now has a name, but nothing that explains the mysterious voice notes.

He looks at the clock.

1:52 AM.

The trail has gone cold.

Ending 1: Half an Answer

A name isn't a person. Go back and choose B.

🅱️ Open the old archive cabinet

Dev remembers seeing an old cabinet behind the studio door.

He decides to investigate.

Continue to Episode 3 below.


Episode 3: The Cassette

The cabinet key hangs on a nail behind the door, under a layer of dust.

The lock groans.

Inside are forty old cassettes, each with a handwritten label.

One catches Dev's attention:

"Raat Ka Saathi, 1991. Khan."

He slides it into the old cassette player.

A hiss.

Then a voice.

Deep, warm, unhurried. A voice that sounds like it was made for radio.

KHAN (1991 RECORDING):

Yeh Akashvani ka Lucknow kendra hai. Raat ke do bajne wale hain. Agar aap abhi tak jaag rahe hain, toh main aapke saath hoon. Aaj ki raat ka aakhri gaana, sirf aapke liye.

A song begins.

Raat Ka Musafir.

Old. Gentle. Built around the same eight-beat rhythm.

Dev presses pause.

His hands are shaking.

DEV (whispering): Yeh wahi hai. Woh isi gaane ke liye ungli bajate hain.

He looks at the clock.

1:31 AM.

In sixteen minutes, the mysterious voice note will arrive again.

He rewinds the cassette.

At the end of the recording, Khan repeats a familiar sign-off.

The same words.

The same rhythm.

The same voice.

Dev begins to wonder whether someone has been waiting for that sign-off for thirty-five years.

🎧 Choice 3: What does Dev do on air tonight?

🅰️ Play the song and say nothing

At 1:47 AM, Dev plays Raat Ka Musafir.

No words. No introduction.

The song fills the studio.

Somewhere across the city, a phone buzzes.

Another voice note arrives.

The fan. The cooker. The tapping.

This time, the rhythm is a little steadier.

Then nothing.

Dev smiles, relieved, and ends the show.

Ending 2: The Song

It was kind, but the listener wasn't waiting only for the song. Go back and choose B for the true ending.

🅱️ Play the song, then say the old sign-off on air

Dev looks at the microphone.

He takes a breath.

He has never repeated someone else's words on air before.

But tonight feels different.

Continue to Episode 4 below.


Episode 4: Yeh Akashvani Hai

1:46 AM. Dev adjusts the microphone.

His hands are cold.

For the first time, he doesn't look at the streaming dashboard.

He looks at the clock.

DEV (into the microphone, steady for the first time): Raat ke do bajne wale hain. Agar aap jaag rahe hain, toh yeh gaana sirf aapke liye.

He presses play.

Raat Ka Musafir fills the studio.

Sound: The old eight-beat rhythm. Soft. Familiar.

The song ends.

A moment of silence.

DEV (slowly): Yeh Akashvani ka Lucknow kendra hai.

He stops.

He doesn't know whether he is allowed to repeat those words.

Then he continues.

DEV: Raat ke do bajne wale hain. Aap abhi tak jaag rahe hain, toh main aapke saath hoon.

The red ON AIR light stays on.

For ten seconds, nothing happens.

Then his phone buzzes.

A voice note.

Twenty seconds long.

Sound: A boy's voice. Young. Breathless.

BILAL (voice note):

Bhaiya... Dadu ne suna.

Woh bol nahi sakte. Operation ke baad unki awaaz bahut kam ho gayi thi.

Lekin jab bhi 1:47 bajte hain, woh mujhse phone uthake kamre ki awaaz record karne ko kehte hain.

Woh kehte hain, "Dev sun lega."

Sound: A pressure cooker whistle. The fan. And then the tapping begins.

The eight-beat rhythm.

Steady.

Joyful.

A pause.

Then, from very close to the phone, a rasping, broken whisper.

An old man, speaking for the first time in a year.

KHAN SAHEB (hoarse, barely audible):

"...Yeh... Akashvani... hai."

The tapping continues.

Then it stops.

Dev presses his hand over his mouth.

For several seconds, he cannot speak.

Then he leans into the microphone.

DEV (voice cracking, smiling): Khan Saheb... shukriya. Raat abhi baaki hai.

Sound: The song begins again, softly, underneath his voice.

ON SCREEN:

Some voices never fade. They wait for the right ear.

Ending 3: The True Ending


Why I Wrote It This Way

I wanted to experiment with a format where the reader doesn't just read a mystery but actively participates in solving it.

Here are five creative decisions that shaped the story:

  1. Audio-first storytelling: Every important clue is a sound: a fan, a cooker, a tapped rhythm, and a breath. The story is designed to work even with the screen off.
  2. A mystery the reader can solve: Dev hears the same rhythm as the reader. Instead of explaining everything immediately, I wanted readers to notice the clues themselves.
  3. Choices that change the emotion: Playing the song is an act of kindness. Repeating the old sign-off takes courage. The important choice is not just about what happens next, but about whether Dev is willing to connect with someone he has never met.
  4. Dead ends that still tell a story: Every wrong option has its own ending. Readers aren't simply told they made a mistake; they discover what happens when Dev chooses a different path.
  5. One whisper as the payoff: The entire story builds towards a single line from a man who can barely speak. I wanted a small, quiet moment to carry more emotion than a dramatic twist.

For me, the interesting part was making the reader listen carefully, follow the clues, and feel that their decisions matter.


How I Used AI to Write This Story

This story didn't begin with an AI prompt. It started with an idea, a pen, paper, and brainstorming.

  • Tools: Claude, ChatGPT, and Google Search.
  • My process: I first brainstormed the concept on paper and thought about the setting, characters, sounds, and possible endings. Once I had a rough direction, I used Claude and ChatGPT to help organize my ideas into an interactive storyline, structure the branching choices, improve the wording, and explore different dialogue variations. I also used Google Search to explore relevant references and check technical and contextual details.
  • What worked: AI helped me turn scattered ideas into a structured story with multiple paths and endings. It was particularly useful for exploring different possibilities, organizing the choices, improving transitions, and checking whether the reader could follow the story without getting lost.
  • What didn't: The first versions felt too much like ordinary scripted stories. Some dialogue was overly polished, and some explanations revealed too much instead of allowing the mystery to develop naturally. I wanted readers to feel curious, notice the sounds, and discover the truth themselves. So I reworked the scenes, simplified the dialogue, added more pauses and sound-based clues, and made the choices more meaningful.

One of the biggest lessons for me was that an interactive story is not just about giving readers multiple options. Every option should reveal something, change an emotion, or make the reader think differently.

The idea started with me. AI helped me structure and refine it. The final creative decisions were mine.


Your Turn

Which ending did you reach first?

  • The Silence
  • Half an Answer
  • The Song
  • The True Ending

And here's a question:

If you were Dev, would you have repeated Khan Saheb's sign-off without knowing who was listening?

Tell me your choice and why in the comments.

If enough readers are interested, I'll write Part 2:

What happens to Bilal after that night?


About Me

I'm Sumit Tiwari, a frontend developer, open-source contributor, and writer from Pune, India.

I enjoy building web applications, contributing to open source, exploring new technologies, and experimenting with creative storytelling.


This is a work of fiction. All characters, stations, and events are fictional. Any resemblance to real persons or events is coincidental.

Top comments (0)