I adore my users and am thankful for their business, but <1% of them produce ENORMOUS amounts of data. Tens of thousands of pages of text, millions of words, 1000x or more of the average user. I've chatted with these users and they're 100% legit; they're just prolific writers, or like copy pasting lots of content into their projects.
These projects push my application to the absolute limits. Because of these projects, for every feature I make, I must consider the extreme scenario, because someone comes along and pushes the feature to 1000x what I thought was possible. It certainly makes me think about algorithmic complexity every day.
Engineering-wise: sure, make the app more performant. But as a solo dev with a business to run, every product decision is a tradeoff, and performance improvements for 30 or so users suck away a lot of time from core product dev and marketing. Of course, I'll continue to improve the application, but if I set out to make it perfectly performant, I wouldn't have time for anything else.
From a product experience perspective, how do you handle super users? Should I just put my foot down at some point and say "no, actually here's hard limits X, Y, and Z"? Or just suck it up? Or design the product in a way that subtly discourages power-use? Rewrite the whole app in Rust? (Joking.) Obviously I want to make the app work for everyone that wants to use it, but I have to be realistic about my hours in a day. These users are great at surfacing bugs that would've affected everyone eventually, but some bugs are unique to "extreme power-use", especially with an imperfect host like the Browser.
