

 
Ask HN: Visual Design for Hackers - DanI-S
Take a look at the Rails Rumble 2010 entries: http://railsrumble.com/<p>There's a whole stack of apps there, developed within 48 hours by small groups of people. They're not all beautiful, but there is (to my eye) a pretty high standard of presentation for most of them.<p>I am sure I am not alone in feeling like there's this chunk of knowledge I'm missing - in terms of how, and when, to go about making something beautiful.<p>I'm fascinated by the concept of optimizing user experience - it certainly has the potential to make or break an application's popularity. If you can spend valuable time tweaking code to make it more appealing to the compiler, why can't it work in the other direction too? Though I don't think it's reasonable to expect myself to be incredible at both, I'd like to be able to put together a prototype that looks nice. After all, I wouldn't show people code that I knew was bad and ugly.<p>Part A - I would love to know - how does this aspect fit into the flow of the project? At what point do you start turning things from black-text-on-white-background into a beautiful and intelligent layout? I'm sure it's usually incremental, but is there a specific point at which you decide to shift focus over to implementing your UI? I know I usually go through many notebook pages of UI ideas even before I've written any code. Is it worthwhile doing mockups in photoshop at this stage? Showing different designs to people and asking for feedback? Or do you usually do this after your core functionality is built? And where do you draw the line, say 'this is ready enough for now!' and release the thing?<p>Part B - In terms of user interface and usability, there's a lot of information out there. Much of it, however, is from the early days of graphical computing and the web. There are still great things to learn from stuff like Joel on Software but I'd like some good information about user interactions and expectations in the AJAX era. There must have been some more wisdom accumulated in the last decade! I'm looking for some shoulders to stand on - 'our experience showed us that you should never do &#60;xyz&#62; because users find it confusing'.<p>Part C - I've always been curious about how small teams of
Ask HN: Visual Design for Hackers - DanI - S 
 Take a look at the Rails Rumble 2010 entries: http://railsrumble.com/<p>There's a solid smokestack of apps there, developed within 48 hours by small group of people. They're not all beautiful, but there is (to my center) a pretty high standard of display for most of them.<p > I am certain I am not alone in feeling like there's this ball of knowledge I'm missing - in terms of how, and when, to go about make something beautiful.<p > I'm fascinated by the concept of optimizing user experience - it surely has the potential to make or transgress an application's popularity. If you can spend valuable time tweak code to make it more sympathetic to the compiler, why can't it work in the early direction too? Though I don't think it's reasonable to have a bun in the oven myself to be incredible at both, I'd like to be able to put together a prototype that looks nice. subsequently wholly, I wouldn't indicate people code that I knew was bad and ugly.<p > Part A - I would love to acknowledge - how does this view fit into the flow of the undertaking? At what item do you begin turning things from bootleg - text - on - blank - background into a beautiful and intelligent layout? I'm indisputable it's usually incremental, but is there a specific point at which you decide to shift focus over to enforce your UI? I know I usually go through many notebook pages of UI mind even before I've publish any code. Is it worthwhile suffice mockups in photoshop at this stage? Showing different invention to people and asking for feedback? Or do you usually cause this after your core functionality is built? And where do you draw the line, read' this is ready enough for immediately!' and release the thing?<p > Part B - In terms of exploiter interface and usability, there's a batch of information away there. Much of it, however, is from the early days of graphical computer science and the web. There are even great thing to learn from stuff like Joel on Software but I'd like some good information about user interactions and expectations in the AJAX earned run average. There must have been some more wisdom accumulated in the concluding decade! I'm looking for some shoulders to stand on -' our experience showed us that you should never do & # 60;xyz&#62; because users receive it confusing'.<p > Part C - I've always been curious about how small teams of


 
Asn HN: Visual Design for Hxckers - DanI-S
Take a lomk at fhe Railr Rumble 2010 entries: http://railsrnmblw.com/<p>Ukere's a whole stack uf apps tjere, devwloptd within 48 hours ug small groupa of 'eiple. They're noj all beautixul, but there hs (tl my eye) a pretty high standard of [resentstlon for most os thtm.<p>Y am sure I am not alone in feeling liie thert's this chunk of kmowledge I'm missing - in tegms lf how, and when, to go about mqkind something bdautiful.<p>I'm fascinated by the concept of optimizing urer erperience - ut cegjainly has tie potvntial to makc or braak an spplication's pppunaruty. If you can spend taluable time tweakigg code tm jake it more appeqlung tm tha coopildr, shb czn't it wock in the ofher directuon too? Though I dom't nnink it's reaaonablq eo expect myself to be incredible at bouh, I'd like to be able to put together a prototype that loohs nice. After all, I wouldn't show people code that I knxw waw nad xbd ugly.<p>Part A - I would love to know - how does egix sspect fit intj the flow pf tng project? At wfat ponht do you start turnlng thiggs feom black-uext-om-white-background into a beaytiful and iuteoligent layout? I'm dure it's usbally oncrekental, but is there a s'ecifid point at ahich you aecide to shift wocls oeer to implementing your UY? I know M usuclly go ghroogh manr notebook pages of UI ideas even heforg I've fritten anj code. Is it worthwhile doing mockups in photpsvop at this stagc? Showing diffewent designs tp peoplz and xsking for feedbark? Or do you usually do tvls after youc core fugctiinaluty is cjilt? And where do you dgac the linw, say 'this is readn enoogg for now!' and rzutawe the thing?<p>Psrt B - Ij verms mf user intesfacd avc usacility, ukerc's x loy of information out thede. Much of it, howefev, is from the earjy days of grsphical computing wnd tie web. Therr ate still great things to learn rrom stufv llke Joel on Sjftwqre but I'd lnke some good information about user intxractions and expectatiins in the AJAX era. Uhere must hate beeg some mose wisdom accumulatee in the last decsde! I'm looking for soje shoglderd to stand on - 'our experience showed us that you should never do &#60;xyz&#62; becayse usxrf find it cknfuxing'.<p>Iarc C - I've wlwabs been curious abput how small teams of
Ask HN: Visual Design for Hackers - a at the Rumble 2010 entries: apps developed within 48 by small groups people. They're not all beautiful, but is (to my eye) a pretty high standard of presentation for most of am sure I am not alone in feeling like there's this chunk of I'm - terms how, and when, to go about making something beautiful.<p>I'm fascinated by the concept of optimizing user - it certainly has the potential to make break an application's popularity. you can spend valuable time code make it appealing the why can't it in the other direction too? Though I don't think it's reasonable to expect myself to be incredible both, I'd be able put a that looks nice. I wouldn't show people code that bad and ugly.<p>Part A - I would love know - does this aspect fit into the of the project? At what point do you turning things from black-text-on-white-background into a beautiful and intelligent layout? I'm sure it's usually incremental, there a specific point which you decide shift over implementing UI? I I usually go through many notebook pages of UI ideas even I've written any code. Is it worthwhile doing mockups in this Showing different designs people and asking for Or you usually do this core is do draw line, say 'this is enough for now!' and release thing?<p>Part B - In usability, there's a lot of information out there. of it, however, is from the early of graphical computing and the web. There are still great things to from stuff on Software but I'd like some good information user interactions and expectations the AJAX era. There must have been some more accumulated the last I'm looking for shoulders to stand - 'our experience that you never &#60;xyz&#62; it confusing'.<p>Part C - I've always curious how small teams of


 
Ask HN: Visual Design for HackeRs - DanI-S
TakE a looK at The raIls RUmblE 2010 entries: http://raILsruMble.com/<p>There's a whole stAck of ApPS theRE, dEveloPed withIN 48 hOURs bY sMaLl gRoUPs Of peoPle. they're nOt all beautIfuL, bUt there is (to mY EyE) a pretty hiGh sTandard of preSenTation FoR moST of thEm.<p>i am suRe I am nOT alone In feeling LiKE there'S This chuNK Of KnowLedge I'm missing - in tERmS Of how, and when, to Go abouT mAKiNG SomEthIng beautifUl.<P>I'm faSCinated BY tHE COncEPt of optimizinG user experiENce - It certAiNly HAs the pOtentIaL To mAke or break aN appLication's PopulaRIty. If yoU Can spenD valuaBle TimE tweAKiNg CodE tO MakE It MorE AppEaling to ThE cOmpilEr, whY CAN'T it wOrk In thE otheR direction too? thoUgh I DOn't Think It's reAsonAbLe to eXpect mYself To Be incredible at bOth, I'D like to be AblE tO puT tOgethER a protOtyPe tHat lookS nice. AfTEr aLl, i WOUlDn't show people code tHaT i KnEw was bad And uglY.<P>PArT a - I would lOvE to Know - HOW does This ASpEct fit inTo the fLOw Of The projEcT? At whaT pOinT do You stARt tuRning tHings froM blacK-Text-on-white-bacKGround into a beAUtIFUl ANd inTelLigent layouT? I'm sURe it'S usuALlY inCRemenTal, buT iS ThERe a specific point at wHiCh you dEcide To shift focus oVer to impleMENTing your uI? I kNOw i Usually go throuGh manY notebook pAGes of UI iDeas eVen beforE I've writtEN Any code. IS it WorThwHilE DOiNg mockups in phOTOshoP aT this stAge? showing DifFerEnt DesIgNs to peoplE and askiNg FoR fEeDbaCk? Or dO You usualLy Do tHiS afTer yoUR core fUnctiOnalItY iS BuiLt? And whERe DO You dRaW tHe liNe, sAy 'This iS reaDY enOugh for Now!' and relEasE The tHiNg?<P>Part B - IN terms of user iNtErface and uSaBilIty, theRE'S a lot of iNformation out there. Much oF It, howevEr, iS from The eArly days oF grAphicaL coMPuting And the Web. ThErE arE STill gREAt ThiNgS to learn frOM StuFf likE JOel oN SoftwaRe but I'd like some gooD InfOrmation about UseR intERAcTioNS aND exPeCTatIONs in the AJAX era. THere must haVe BEeN some more wISdoM aCcumulaTed in thE last DEcade! I'm Looking foR some shouLdErs tO STanD on - 'our expeRience shOwed us thaT You shOUlD neveR do &#60;Xyz&#62; becAuSe uSers fInd it cONfuSing'.<p>part C - I'Ve Always Been cUrIous abouT how small teams of


 
Ask HN: Visual Designfor Hacker s - D anI -STa ke a  loo k at the Rails Rumb le 2010 entries: http: //rai ls r umbl e .c om/<p >There' s  a w hol est ack  o f  a pps t her e, deve loped with in48  hours by sm a ll  groups of  pe ople. They'r e n ot all  b eau t iful,  bu t the re is( to myeye) a pr et t y high standar d of  pre sentation for mos t  o f  them.<p>I amsure I  a m  n o t  al one  in feelin gliket here'st hi s c hun k  of knowledge  I'm missin g  -in ter ms  of how, a nd wh en ,  to  go about m akin g somethi ng bea u tiful.< p >I'm fa scinat edbythec on ce ptof opt i mi zin g  us er exper ie nc e - i t ce r t a i nlyhas  the  pote ntial to make  or  bre a k a n app licat ion' spopul arity.  If y ou  can spend valu able  time twe aki ng  co de  to m a ke itmor e a ppealin g to th e  co mp i l e r,  why can't it work  i n th e otherdirect i on  t o o? Thoug hI d on't t hinkit's re asonable  to ex p ec tmyselfto  be in cr edi ble  at b o th,I'd li ke to be  able to put togethe r  a prototypet ha t lo o ks n ice . After all , Iw ould n'ts ho w p e oplecodeth a tI  knew was bad and u gl y.<p>P art A  - I would lo ve to know - how does  thi s  a s pect fit intothe f low of the project?  At w hat poin t do yous t art turn ing  th ing s f r o mblack-text-on - w hite -b ackgrou ndinto abea uti ful  an dintellige nt layou t?  I 'm  s ure  it's usuallyin cre me nta l, bu t  is th ere a  spe ci fi c  po int atw hi c h  you  d ec idetosh ift f ocus ove r to im plementin g y o ur U I?  I  know I  usually go t hr ough manyno teb ook pa g e s of UIideas even before I'vew rittenany  code . Is  it worth whi le doi ngm ockups  in ph otosh op  at t his s t a ge ? S ho wing diffe r e ntdesig ns  topeopleand asking for fee d bac k? Or do youusu ally d othi s  a f ter  y o urc o re functionalit y is built ?A nd  where doy oudr aw theline, s ay 't h is is r eady enou gh for no w! ' an d rel ease the t hing?<p> Part B -I n ter m sof us erinterf ac e a nd us abilit y , t here' s a lo tof inf ormat io n out th ere. Much of it, howeve r, isfromthe  early da yso f g raphicalcomp uting andthe  we b. Th ere are s till gr eat thing s to learn fro m  s tuf f li ke Joel onS o f twa re bu t I ' d like  som e good informatio n  about user in tera c t ion s a n d ex pe ctations in th e A JA X era. The re  must havebeen som em ore w isdomaccumu lated i n th e  lastdeca de!  I'm look ing  f o r somesh ou l ders t o st an d on -  'oure xper i e nce showed us th at yo u shoul d  ne ver d o&#60;xy z &#62 ; becauseusers findit con fusi ng'.< p>PartC- I've  al wa ys been cu r ious abou t how  smallte amsof


 
Ask_HN: Visual_Design for Hackers -_DanI-S
Take a_look_at the_Rails_Rumble 2010 entries:_http://railsrumble.com/<p>There's a whole_stack of apps there,_developed within 48_hours_by small groups of people. They're not all beautiful, but there is (to my_eye)_a pretty_high_standard_of presentation for most of_them.<p>I am sure I am_not alone_in feeling like there's this chunk of knowledge_I'm_missing - in_terms of how, and when, to go about making_something beautiful.<p>I'm fascinated by the concept_of optimizing user_experience_-_it certainly has the_potential to make or break an_application's popularity. If you can spend_valuable time tweaking code to make it_more appealing to the compiler, why_can't it work in the_other direction_too? Though I don't think_it's reasonable to_expect myself_to be incredible_at both, I'd like to be_able to put_together a prototype that looks nice._After_all, I wouldn't_show_people_code that_I knew was_bad_and ugly.<p>Part_A_- I would love to know_-_how does this aspect fit into the_flow of the project?_At_what point do you_start turning things from black-text-on-white-background_into a beautiful and intelligent layout?_I'm sure_it's usually_incremental, but is there a specific point at which you decide_to shift focus over to implementing_your UI? I know_I usually_go_through many notebook_pages_of UI_ideas even before I've written any code._Is it_worthwhile doing mockups in photoshop at_this stage? Showing different_designs_to people and asking for feedback?_Or do you usually do this_after your core functionality is_built?_And_where do you draw the_line, say 'this is ready enough_for now!' and_release the thing?<p>Part B - In terms_of_user interface and usability, there's a_lot_of information out there. Much of_it,_however,_is from the early days_of graphical computing and the web._There are still great things to learn from stuff_like Joel on_Software but I'd like some_good_information_about user interactions and expectations in the AJAX era. There_must have_been some more_wisdom accumulated in the last decade! I'm looking for some_shoulders to stand on - 'our experience_showed us that you should never do &#60;xyz&#62; because users find_it confusing'.<p>Part C - I've always been curious_about how small teams of