[Show IH] Built Evoke: Tools That Appear When You Need Them

one thing i'd stress-test early: 'build your own tool' is a genuinely cool pitch, but it's also a blank canvas, and blank canvases bounce most people. the majority don't open an app already knowing which micro-tool they want AND having the motivation to build it right then. that's a lot to ask on day one.

but look at your own screenshots. WriterRefine, GST QuickCalc, FiveFit, all those pre-made tools are the actual hook, not the builder. they give someone a reason to open the app today. the 'build your own' is a power feature maybe 5% will ever touch, and that's completely normal for this kind of product.

so if it were me i'd flip the framing: lead with 'a pack of tiny useful tools that appear when you need them' (which your title already nails), get people hooked using 3 or 4 of them, and only then reveal 'oh, and you can build or remix your own.' positioning it primarily as a builder makes people hit the blank canvas on step one. positioning it as a gallery you can also extend gives an instant reason to stay.

good news is your title and that grid are already pointing the right way. i'd just make sure the app's very first screen does too, not a create-something prompt.

I like that you're making the unit of creation a small, purpose-built tool instead of expecting people to build full applications.

I'll be interested to see which kinds of tools users create repeatedly without prompting. Those patterns will probably reveal what Evoke is actually becoming, beyond what it was originally designed to be.

Nice, the small-tool angle is the interesting part. Most builders push you toward making something big, and a lot of people just don't want to. As a user my first question is what happens after I make one. Where does it live, and how do I get back to it next week without hunting for it. Making one is the fun part. Whether I come back to it later is the real test. Curious how sharing works right now. If I build a little tool, can I hand it to someone else easily?

The idea of letting people build their own micro-apps and tools without needing to code is a strong hook — that's usually the exact gap between "I have an idea for a tiny tool" and it ever existing. Tools that talk to AI is a smart angle too, since it turns Evoke from just a builder into something that can actually do work, not just display things.

Being Android-first is an interesting call given how much of the no-code/maker crowd skews iOS — was that a deliberate choice (dev speed, review process, personal device) or just how it happened to ship first? Also curious what the actual building experience looks like inside the app itself — is it more drag-and-drop, prompt-based, or something else? That's usually what decides whether non-technical people actually finish building something or bounce halfway through.

Love the "appears when you need it" framing — that's such an underused pattern in tool design, most things just sit in a menu waiting to be remembered. What triggers Evoke to decide the right moment — is it context-based, time-based, or something else?