You use one app for notes and another for tasks. A new workspace offers both, with one bill and no copying between them. But its task view is weaker than the tool you already know.
Keeping specialist tools means extra logins and connections to maintain. Moving everything into one place means accepting whatever that app does less well.
You open a document on a train and the connection drops. Being able to read it is useful. Being able to finish editing it and save the changes is a different promise.
For an app maker, keeping work on the device can mean more to maintain. For the person using it, the tradeoff might be fewer AI features or waiting to share changes with a teammate.
I recently built a small PDF editor for myself. I wanted something free that I could open in the browser whenever I needed it.
With AI, I ll just build my own seems like a reasonable option for more of these small problems. Especially when you only need a few features and the tool only has to fit the way you work.
I suspect a lot of useful AI-built software will end up as something someone keeps in their bookmarks and uses every week, without ever trying to turn it into a business.
I m hosting the editor on Inquir Compute, the platform I m building for apps, databases and background jobs. We re getting close to launch, and I d like to hear about the things people are building for themselves.
A friend sends you an app that might solve one small problem. You open it and the first screen asks you to create an account before you can see what it does. Some apps need an account to save work or sync; for a quick evaluation, that s a real ask.
As someone building Inquir Compute, I m curious about that first step. The difference may be whether you reach a useful moment before sharing an email, or whether signing up is itself part of getting value.
