Servers and databases and UIs, oh my
November 9, 2010 1:04 PM Subscribe
How do tech limitations affect design choices on large scale Web sites?
posted by rmm to computers & internet (11 answers total) 5 users marked this as a favorite
Hi HiveMinders - and specifically Web techie MeFis,
I have a concrete example - Meetup and LinkedIn and their user account management or lack thereof. Not to attack these 2 sites specifically, because I do love using both of them - but they're a site that has some of these design issues. Both sites have a huge number of users and user groups, and lots of functionality within those groups. If you go under your account settings, you'd think the ability to control how much email you get from the site would be there. The designer part of me says, 'have a global email communications setting via a checkbox that allows the user to turn off ALL emails from Meetup'; instead, with Meetup, you have to go to each individual group's setting page and change it there. Is there a reason on the tech end of things why global settings aren't an option? I'm seeing the front end solution (i.e. add checkboxes), but is there a back end requirement with the databases and server loading that prevents these kind of simple solutions from being implemented? I know enough about the reasoning that goes into design choices from the non-tech requirements angle - the usual suspects, like usability isn't always important when developing the site, that some sites choose to have weird account settings on purpose (Facebook as one obvious example), etc. What are the *technical* requirements that prevent the most humane design choices in UI?