Fabian Maume

How do you actually use AI for long-term planning?

I've noticed something while building products.

AI is amazing at answering questions, but the moment a project stretches beyond a few conversations, things start to break down.

Every new chat means I have to explain:

Hi Product Hunt community!

I have a genuine question for builders and product managers here about the necessity of native iOS/Android apps for simple utility tools.

Years ago, if you wanted to build a smooth, high-performance tool like a video compressor, photo editor, or drawing board you had no choice but to build a native mobile app. Web apps were simply too slow and lacked access to heavy device processing.

But with WebAssembly (WASM), WebGPU, and modern browser engines, we can compile heavy native libraries and run them directly in the browser at near-native speeds.

I built a journaling app, and while working on it I noticed that almost every app
in the category follows the same playbook:

Streaks. Counters. Badges. "Don't break your streak."

To be fair, they work. Retention charts don't lie.

But I kept wondering:
At what point does a habit stop helping people and start feeling like homework they owe an app?