Functionality Rationing in large scale webapps

For huge apps with lots of functionality, why not assign each discrete component a cost based on the impact to capacity. Then enfoce dynamic rations on users to preserve at least some functionality durring high volume periods. A user can choose to turn everything off except for the big honkin’ consumer if they have enough ration points. Better overall experience for all? Ripe for misimplementation, that’s for sure.

e.g. I’ve returned the first 25 results of your search for “#quantifiedself”. Showing you the next 25 results will cost you 5 “points”. You currently have 0 points. Would you like to disable your live twitter feed for 5 minutes to free up 5 points?

Does this present a better user experience?

When twitter currently says “Older tweets are temporarily unavailable.” would they rather say something like this?

One Response to “Functionality Rationing in large scale webapps”

  1. JACOB says:


    PillSpot.org. Canadian Health&Care.No prescription online pharmacy.Special Internet Prices.Best quality drugs. No prescription pills. Buy drugs online

    Buy:Valtrex.Arimidex.Retin-A.Lumigan.Synthroid.Mega Hoodia.Human Growth Hormone.Zovirax.Petcam (Metacam) Oral Suspension.Accutane.Actos.Prevacid.100% Pure Okinawan Coral Calcium.Nexium.Prednisolone.Zyban….

Leave a Reply