Are there any companies that offer “small” and “large” UIs for large vs small customers? Not specifically “Lite” vs “Enterprise”, but thinking along the lines of “If you have 0-X this is the best UI for you, and if you have more than X, these views work better” I feel like there should be a UX paradigm along these lines, but I can’t find the right words so that I can learn more.

Interesting approach but it sounds more like you'd be building and selling two separate products. It would likely be a challenge to maintain and cross-sell / upsell users to. Generally, you want your "lite" users to be able to naturally grow into the "enterprise" user. They should know what to expect in the expensive tier by the time they are ready, and you should have a UI that makes it easy for them to pull the trigger when that time comes. I imagine with two separate ecosystems for your users, that would be difficult. I'm curious, is there a specific reason for wanting two different UI's per type of user? I would love to know what inspired the thought. 🙂

Hi @Caitlyn Miley, that’s the thing, in this case it isn’t about the tier, it’s about UX around the amount of data. This case may be odd because everyone gets the same features, the pricing increases as you have more data. Here’s the example rattling around in my head: I’m looking at a CRM contact page, which works the same regardless of how many contacts the customer has. When you go to the page, it shows a search bar, the first page of contacts, and finishes with page number links. That’s fine and probably useful UX when you have fewer than 500 contacts. You might use the page number links to find the contact you’re interested in. But customers with 10,000 or 100,000 contacts are not going to be able to find contacts by paging through the results. They would need to search first. Loading the first page of results is a waste of resources and screen space; I’d like to offer up more useful UX elements. For example, instead of loading the first page of results, show the search box plus the user’s last 5 searches.

I see what you're saying. Curious, is there a reason why you're focusing on that specific problem? I might be missing something. It seems like it would be easier to default your UI to your solution of "loading the first page of results, show the search box plus the user’s last 5 searches" for both types of users and then just rate limit the amount of contacts you can have per tier. The whole point of having tiers is to increase sales and solve a pain point for larger users. More times than not, a clever UI is not the pain point people will pay to have solved. I hope that helps but i'll keep any eye out for any products that take that approach. Right now, I can't think of any but would be interested to know if/when that strategy might be appropriate!

I suppose you could have the UX be reactive based on the size of the dataset in the example given, though some users would like to control which experience they got via some toggle switch I would expect. In our UI for data engineering there's a toggle switch to make the UI read-only so that changes to the data project can only be made via integrated version control. This reflects something like what you describe where small or new data projects tend to be hacking around in the UI to get things working how they want, then larger or more mature data projects tend to want to be version controlled with CICD to evolve the schema and SQL involved.

That’s a great way to phrase it! - “~Reactive~ Responsive UI for data size instead of screen size”

@Jeffrey Sherman not exactly the same thing, but Stytch has different UI experience based on the type of business (B2B vs B2C). It may inspire you

Thanks for sharing Stytch! Always cool to see battle-tested & new ways to do things.🙂