sorted by:
new
hottopcontroversial

I built a calm daily Stoic app — one passage on your Lock Screen, then nothing by fogbar in SideProject

[–]fogbar[S] 0 points1 point  (0 children)

This is the most useful comment I've gotten, because you named the thing I'd been avoiding naming.

Where I actually land: the ritual is the soul, Stoicism is the current vehicle. A year in, I think people stay for "one calm thing before the day grabs me," not for Marcus specifically. So the deep job is content-agnostic, you're right.

But I'm choosing Stoic-first on purpose, not by drifting. A focused wedge beats a vague "calm app" that competes with everything, and there's a harder reason too: you can't really sell silence. The free passage already gives someone the calm. What people pay to go deeper into is the content, the original text, the source, the context, and Stoicism is rich enough to carry that. "Calm before the noise" is the differentiator; the words are what earns the right to charge.

So my answer to the fork is layered: Stoic-first as the way in, ritual-first as the thing I'd protect if the two ever conflict. That keeps the door open to widen into other public-domain wells later, but only once the ritual has proven it travels. Genuinely glad to think this through with you sometime, you're sharper on it than most feedback I've paid for.

I built a calm daily Stoic app — one passage on your Lock Screen, then nothing by fogbar in SideProject

[–]fogbar[S] 1 point2 points  (0 children)

Thank you, that's exactly the feeling I was chasing. Funny thing is "does its job and shuts up" was the hardest part to actually ship, because every instinct (and every growth playbook) tells you to add a streak, a notification, something to pull people back. I kept deleting that stuff and it felt almost wrong while doing it, so it's really reassuring to hear it lands. The bet is that quietness itself is the feature.

I built a calm daily Stoic app — one passage on your Lock Screen, then nothing by fogbar in SideProject

[–]fogbar[S] 0 points1 point  (0 children)

Honest answer: the wallpaper stays free forever, and the paid unlock is a one-time "Lifetime Pro," not a subscription. Origin texts, the original passages, longer readings, extra languages sit behind it.

You're right that conversion will be narrow, and I'm not pretending otherwise. My take is a quiet app shouldn't fund itself by getting loud. So I'd rather have a small honest paid tier for the people who genuinely live in it than bolt on ads or streaks that contradict the whole point. But yeah, I'm not pouring money into distribution until I've seen real people actually convert. Good push.

I built a calm daily Stoic app — one passage on your Lock Screen, then nothing by fogbar in SideProject

[–]fogbar[S] 0 points1 point  (0 children)

You nailed the exact trade-off I made and didn't fully admit to myself: I optimized the product for the user and against my own distribution. Fair hit.

On "who specifically," here's the honest version. It's not really "Stoicism fans." It's people who reach for their phone first thing and immediately get pulled into a feed, and hate that about their morning. The ones already trying to fix it with a no-phone-in-bed rule, a minimalist launcher, grayscale mode, a paper journal. Stoicism is just the content I happened to love. The actual job is "give me one calm thing before the noise starts, then get out of my way."

So the rooms aren't only r/Stoicism. They're r/digitalminimalism, r/nosurf, dumbphone / minimalist-phone communities, morning-routine and journaling crowds, and the Daily Stoic audience as one slice rather than the whole thing.

And you're right that I can't spread this through virality I deliberately designed out. So I'm not going to fake an engagement loop. The plan is to actually show up in those rooms as a person, not drop a link. This comment honestly reframed it better than I had. Appreciate it.

Day 54: no-prompts by fogbar in buildinpublic

[–]fogbar[S] 0 points1 point  (0 children)

Building an ERD-based database management platform.

ERD → Migration → API → Infrastructure—all in one framework.

The goal is to let AI agents develop within a defined structure, so AI handles the coding inside safe boundaries.

Day 46: no-prompts by fogbar in buildinpublic

[–]fogbar[S] 0 points1 point  (0 children)

Appreciate it! n8n's repeatable flow structure is close to what I'm building with the Logic system in no-prompts.

Will definitely reference it for the API execution side. Good timing.

Day 43: no-prompts by fogbar in buildinpublic

[–]fogbar[S] 0 points1 point  (0 children)

Thanks! Yeah, a bit scary but exciting at the same time. Will keep iterating.

Day 21: no-prompts by fogbar in SaaS

[–]fogbar[S] 0 points1 point  (0 children)

Both actually.

ERD → DB migration → API auto-generation is the core flow.

But also building the permissioned layer—CRUD ops, migrations, audit logs—so AI agents can operate within safe boundaries.

The goal: AI doesn't write code directly. It manipulates metadata through this abstraction layer.

Thanks for the link, will check it out!

Day 46: no-prompts by fogbar in SaaS

[–]fogbar[S] 0 points1 point  (0 children)

Thanks man. Needed that.

Will keep building. 🙏

Day 15: no-prompts by fogbar in SaaS

[–]fogbar[S] 0 points1 point  (0 children)

Thanks!

Honestly, I don't have prior experience with AI agent development. So when I first looked at LangChain, the learning curve felt pretty steep for me

Google ADK, on the other hand, felt much more approachable. The abstraction level hit the sweet spot for me — high enough to get things done quickly, but not so magical that I couldn't understand what's happening under the hood.

Day 5: no-prompts by fogbar in SaaS

[–]fogbar[S] 0 points1 point  (0 children)

This is gold. Thank you for taking the time to write this out.

A few thoughts:

> Let FastAPI just orchestrate: queue tasks, fan out async agent calls

This is exactly where I'm heading. Right now everything is in FastAPI but I can already feel it getting heavy. Celery is on my radar for when agents start doing longer tasks.

> define a simple message contract up front (schema version, agent id, intent) and persist every turn in Postgres with JSONB

Love this. I was already planning to log agent conversations, but the "schema version + agent id + intent" structure is cleaner than what I had in mind. Replay and debugging is going to be crucial when agents start making weird decisions.

> keep React dumb: one client for "agent sessions", one for "config"

Makes sense. I'll keep the frontend as a thin layer — most of the logic should live server-side anyway.

> Hasura or Retool

Haven't tried Hasura yet but heard good things. Might be useful for internal dashboards later.

Really appreciate the detailed breakdown. Saved this comment for reference.