Agree with that. One thing I will say is that RC prices are dynamic. If there is more usage from pools then the prices will go up. So you will need to delegate more per user to the pool than you might expect from average usage. The more apps/games do this the more prices will go up. This will also hurt low-HP users who aren't getting a delegation from an app/pool. It's also a negative for the price of HIVE if apps can get away with needing less HP to support their users (within reason; if the cost becomes too high then it becomes non-viable and they fail or leave, but there is a range).

Anyway, the points I just made are true but that wasn't really my intention in mentioning it here. My bigger concern is that the more complex solution becomes an obstacle in terms of completion and reliability (the later includes ongoing maintenance; once people start using it, it will need to be maintained if problems crop up, and this can be a future burden) if it takes resources away from other development. No question, as I said, the pool model is more powerful and useful, but the utility gap between no RC delegations at all and simple ones is much, much bigger than between simple ones and pools IMO.

We'll have to micro-manage thousands of small delegations and keep doing minor adjustment to the delegate amount according to how much each user is using.

Sounds very easily automated to me.