Diven

A few days ago, I posted here because I felt stuck on distribution.

Like a lot of technical founders, I’m comfortable building the product.
Getting early users for a consumer app feels much less obvious.

So instead of overthinking “marketing,” I ran a simple experiment:

I created a dedicated Instagram account for Diven and decided to learn the platform before trying to promote it aggressively.

For context, Diven is a consumer app in the learning/discovery space. It helps people explore interesting facts and short explainers on topics they care about, then suggests related directions if they want to dive deeper.

What I did over the last week

• Created a dedicated Instagram account for Diven

• Pinned 2 carousel posts (in French and English) to highlight the app’s multilingual angle

• Started posting 1 feed post per day

• Spent time following, liking, and commenting on curiosity-focused accounts

• Avoided direct promotion in comments (I don’t want to look spammy or hurt the community)

So I’m definitely not claiming I’ve figured out Instagram.

But I am starting to build a habit:

less “how do I market this?” and more “how do I become native to the platform?”

The interesting part: it improved the product too

Because I’m using Diven itself to generate content for Instagram, I found friction in my own workflow almost immediately.

On Android, I was sharing both an image and text through the native share API.

But Instagram only picked up the image in the feed creation flow, not the text.

That made posting slower than it should be.

So I added a simple workaround:

• Diven shares the image to Instagram

• It also copies the generated caption to the clipboard

• The copied text also includes my promo link + hashtags

• Then it shows a small notification so the user (currently… me 😄) can paste everything instantly

That means I no longer have to manually copy text from the app, and the posting flow is much smoother and more consistent.

The unexpected side effect

This is the part I didn’t anticipate.

Because I’m now generating content through Diven every day, I’m also creating and storing more precomputed content in the backend.

That means:

• more topics are generated in advance

• more content is cached before real users arrive

• less cold-start friction

• faster perceived loading when someone dives into a topic

So this small Instagram experiment is doing two jobs at once:

1. Helping me learn a consumer social channel

2. Quietly improving the app experience for future users

What I’m thinking next

I’m now considering automating part of this loop from the backend:

• generate daily content automatically

• streamline the posting workflow

• keep expanding the pre-generated content library

The goal isn’t just to “post more.”

It’s to spend less time on repetitive posting tasks and more time on actual social interaction:

• engaging with curiosity-focused communities

• learning what content resonates

• understanding Instagram behavior

• building visibility more naturally

The hard part, of course, will be making the content genuinely engaging.

But I’m optimistic because Diven already has a strong structure for that:

• curiosity-first topics

• short explainers

• related “rabbit holes” to keep exploring

• good multilingual potential

My takeaway so far

I still haven’t “cracked Instagram.”

But I’ve stopped thinking about distribution as:

“How do I promote my app?”

And started thinking about it more as:

“How do I build a repeatable content system that frees me up to interact like a real person?”

That shift alone already feels valuable.

Anyone else who’s climbed this mountain and automated content early — what would you have done differently?

Hi everyone,

I’ve been working on a mobile app for the past couple of years.

It originally started as a side project so I could experiment with AI and a native mobile stack (Flutter + Firebase), but over time I started wondering: what if I actually try to launch it properly?

As a technical guy, I naturally focused a lot on the product side: scalability, architecture, UX, and building something clean and maintainable.

That part feels familiar to me.

What feels much harder is everything around distribution: figuring out how to reach early users, which channels are actually worth testing, and how to avoid wasting time on the wrong things.

For context, this is a consumer mobile app in the learning/discovery space. It helps people explore interesting facts and short, high-quality explainers on any topic, then suggests related directions if they want to dive deeper.

I’d love to hear from people who’ve been through a similar first launch:

• Which channels worked best for your first 10–100 users?

• How did you identify your first promising user segment?

• Is it worth paying for launch/growth help this early?

Any practical advice or lessons learned would be hugely appreciated.

Thanks!

The problem that drove me crazy

I’d think “what if I knew more about that?” a dozen times a day—then either scroll on or open a chatbot and end up writing prompts, following threads, and feeling like I was doing work. I wanted to learn in spare minutes, not run a prompt-engineering session.

Passive scrolling doesn’t teach you anything. But who has time (or energy) to “properly prompt” an AI every time you’re curious?

What I built

Diven starts from the topic, not the prompt:

• Pick a topic → AI gives you deep dives, quick facts, and articles. No prompts to write, no long chat.

• Read or skim → Clear, structured content in a few minutes. Built for 10–20 minute curiosity breaks, not study marathons.

• Keep or share → Turn what you learn into something you can share. One-tap summaries, surprising facts, “I didn’t know that” moments.

The idea is simple: feed your curiosity without the homework. Tap a topic, get discoveries and shareable facts—no prompt engineering, no endless threads.

Where I'm at

It’s live on Android. I’m looking for people who:

• Have 10–20 minutes they usually spend scrolling

• Like learning in short bursts and sharing interesting stuff

• Want “I didn’t know that” without “now write a prompt”

If that’s you, I’d love your honest feedback: what’s confusing, what would you change, or what would make you use it again?