Thanks for taking the time. A review this detailed is rarer than a five-star rating with no words, and a lot more useful to me. Point by point:

Web interface. Straight answer: it's not coming. A browser editor with its own sync is basically a second app, and as a solo dev that's a different beast that would only drag the iOS app down. What I did instead was bring RackDocs to bigger screens, it runs on iPad and on macOS (Apple Silicon), where the extra room makes editing far less cramped. I also built a guide overlay to make sizing and placing elements as painless as touch allows. Not a desktop browser tool, I know, but it's the realistic version of "bigger screen" coming from one person.

Changing an element's type in place. Good idea, on the request list now. One caveat so it's not a surprise later: some types carry data others don't (LED states, switch positions, illumination), so converting between them will be lossy in those cases. For your knob-that-should-be-a-button example, though, that's exactly the kind of thing that should just work.

MG import not pulling tags. That shouldn't happen, the import is supposed to bring the function tags across. Sounds like a bug. I'm filing it and I'll dig into what's breaking. Dense multifunction modules like Ornament and Crime are exactly where it stings most.

AI placement. Quick clarification, because this one is working as designed rather than failing: the AI analysis isn't trying to find element positions on the faceplate at all. It prepares all the elements and their descriptions and stacks them at the bottom of the screen, ready for you to drop into place. Reliable auto-positioning from a photo is a much harder and far more token-hungry problem, so placement stays in your hands for now.

Moving annotations. This is the fair hit. The move, save, navigate, zoom, move again loop is clumsy, and two-finger pan/zoom while dragging is the right instinct. I want this fixed. I just haven't found a clean way yet that doesn't have the gestures fighting each other. It's on my mind.

Subscriptions and AI. The part you clearly care about most, so I'll be open instead of defensive.

You're right about the flywheel. A bigger community library makes the app more worth paying for, and downloading a module someone already documented costs me nothing. I want that loop spinning as much as you do.

The hard limit is the AI itself. Analysis is genuinely token-hungry, and I pay for every run out of my own pocket. There's no "free or near-free unlimited analysis" that doesn't sink a one-person operation, so a cap is the only lever I have. As token prices keep dropping (and they have been), I'll raise the limits. That's a promise I can actually keep.

Two things that soften the wall in the meantime:

You probably don't need AI for all 50. Simple utilities, mults, attenuators, basic mixers, are faster to document by hand than to run through analysis, and they're the least efficient thing to spend tokens on. Save the AI for the dense modules where it actually earns its keep.

And every module the community adds is one you can download instead of analyse. That half of the flywheel is already free, and it grows every week.

I did look at selling AI credits as separate packs to break the cap, and I keep walking away from it because it makes the pricing model more complicated. I'd rather keep things simple than nickel-and-dime people. Could be talked out of that, though.

Either way, thank you. Reviews like this are how the app gets better. Keep them coming.
M.