Re: [IxDA Discuss] Managing Complexity of Wireframes
And I've been thinking about the following solution: you draw both parent and child on the same wireframe, but in different layers, and then draw their notes, in another two layers. Then you switch the notes layers parent/child. In this way you can show both parent with preview of the child and the child in context of its parent. Do you think it's practicable to do so? Oleg. On Fri, May 30, 2008 at 8:26 AM, Steve Baty <[EMAIL PROTECTED]> wrote: > Oleg, > > Not a plain grey box, but close to it - you should be able to strike a > balance; all of that extra detail is contained in the separate > representation. An actual object library can also be used if your > wireframing supports them. Although I suspect no matter what software you > utilise, synchronising instances of a panel will require some effort. > > Other caveats: the final choice will necessarily depend on how you feel most > comfortable working :) > > Steve > > 2008/5/30 Oleg Krupnov <[EMAIL PROTECTED]>: >> >> Thanks Steve, >> >> Your answer is clear except that I don't quite understand how you >> technically avoid the problem that a child panel wireframe, contained >> in another drawing document, and copied to the parent wireframe in >> scenarios 1, 2, 3, can get out of sync when its source is modified? Do >> you mean (by the "simple representation") that you don't copy but >> instead show a plain gray box with a reference? In this case, doesn't >> it affect the visual presentability of the parent wireframe? >> > Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Usability = Predictability
Hmmm, this reminds of the automatic lights in the bathrooms where I'm working currently. 2008/5/30 Gavin Burke|FAW <[EMAIL PROTECTED]>: > > You walk up to a door way, you put out your hand to push in the door and it > opens automatically. > I had predicted that I would have to push in the door, but was nicely > surprised when it opened by itself > requiring less physical effect. At the other end of the the scale if having > reached for the door to push it in, I had to pull it out instead... Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Usability = Predictability
Have been keeping an eye on this thread and was thinking of a real world example of usability != predictabilty. You walk up to a door way, you put out your hand to push in the door and it opens automatically. I had predicted that I would have to push in the door, but was nicely surprised when it opened by itself requiring less physical effect. At the other end of the the scale if having reached for the door to push it in, I had to pull it out instead... But what if there was no door at all. Think it comes down to having a goal or task in your head and how you get there can be both predictable or unpredictable in good and bad ways. On 29 May 2008, at 14:29, Eugene Chen wrote: While obviously predictability is wanted most of the time, I feel like this formulation would lead one to making more explicit (ie wordier) and more consistent (ie conventional) designs. The designs I admire most have neither of these qualities. The designs I admire most tend to have a certain amount of ambiguity. Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Managing Complexity of Wireframes
Oleg, Not a plain grey box, but close to it - you should be able to strike a balance; all of that extra detail is contained in the separate representation. An actual object library can also be used if your wireframing supports them. Although I suspect no matter what software you utilise, synchronising instances of a panel will require some effort. Other caveats: the final choice will necessarily depend on how you feel most comfortable working :) Steve 2008/5/30 Oleg Krupnov <[EMAIL PROTECTED]>: > Thanks Steve, > > Your answer is clear except that I don't quite understand how you > technically avoid the problem that a child panel wireframe, contained > in another drawing document, and copied to the parent wireframe in > scenarios 1, 2, 3, can get out of sync when its source is modified? Do > you mean (by the "simple representation") that you don't copy but > instead show a plain gray box with a reference? In this case, doesn't > it affect the visual presentability of the parent wireframe? > > Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Managing Complexity of Wireframes
Thanks Steve, Your answer is clear except that I don't quite understand how you technically avoid the problem that a child panel wireframe, contained in another drawing document, and copied to the parent wireframe in scenarios 1, 2, 3, can get out of sync when its source is modified? Do you mean (by the "simple representation") that you don't copy but instead show a plain gray box with a reference? In this case, doesn't it affect the visual presentability of the parent wireframe? Are there other caveats I have overlooked? Oleg. On Fri, May 30, 2008 at 8:00 AM, Steve Baty <[EMAIL PROTECTED]> wrote: > Oleg, > > One thing I try to aim for in my documentation is that each page has the > same density of information. So where I have a screen that includes a lot of > complexity, I would look to break that complexity off into separate pages > with references on the parent. That principle would apply to your scenarios > 1 & 2. And it applies across deliverables for that project. Depending on the > primary audience for the wireframes I'd adjust the 'standard' level of > complexity and then maintain that density consistently. > > For scenario 4 I would use layering within your wireframing tool and place > the more detailed information into layers that are hidden or shown depending > on the audience. > > For scenario 3 I would use the equivalent of a pattern library with the > parent wireframe containing a simple representation with a reference to the > component detailed wireframe. > > Regards > Steve Baty > > 2008/5/30 Oleg Krupnov <[EMAIL PROTECTED]>: >> >> I'm looking for the current best practices of managing complexity of >> wireframes. >> >> What do you do in the following situations? >> >> 1. A page includes multiple panels, each of them is quite complex, with >> many >> details and notes. How to show all child panels and their notes without >> cluttering the parent page's wireframe? >> >> 2. A page includes an interactive panel, i.e. one that has multiple >> states. >> The size of the interactive panel can be small (i.e. a creeping line) or >> large (i.e. a tab page). How to show all panel states best? >> >> 3. A page includes a panel that is reused on different pages (i.e. as >> common >> info block), or multiple times on the same page (e.g. item in a list). How >> to show the reused panels best, avoiding copying/out-of-sync problems? >> >> 4. Different notes and different level of detail should be shown to >> different audiences. How to create different versions of the same >> wireframe >> best? Also what to do if there is not enough room in the sidebar for all >> footnotes? > > > Steve 'Doc' Baty B.Sc (Maths), M.EC, MBA > Principal Consultant > Meld Consulting > M: +61 417 061 292 > E: [EMAIL PROTECTED] > > UX Statistics: http://uxstats.blogspot.com > > Member, UPA - www.upassoc.org > Member, IA Institute - www.iainstitute.org > Member, IxDA - www.ixda.org > Contributor - UXMatters - www.uxmatters.com Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Managing Complexity of Wireframes
Oleg, One thing I try to aim for in my documentation is that each page has the same density of information. So where I have a screen that includes a lot of complexity, I would look to break that complexity off into separate pages with references on the parent. That principle would apply to your scenarios 1 & 2. And it applies across deliverables for that project. Depending on the primary audience for the wireframes I'd adjust the 'standard' level of complexity and then maintain that density consistently. For scenario 4 I would use layering within your wireframing tool and place the more detailed information into layers that are hidden or shown depending on the audience. For scenario 3 I would use the equivalent of a pattern library with the parent wireframe containing a simple representation with a reference to the component detailed wireframe. Regards Steve Baty 2008/5/30 Oleg Krupnov <[EMAIL PROTECTED]>: > > I'm looking for the current best practices of managing complexity of > wireframes. > > What do you do in the following situations? > > 1. A page includes multiple panels, each of them is quite complex, with > many > details and notes. How to show all child panels and their notes without > cluttering the parent page's wireframe? > > 2. A page includes an interactive panel, i.e. one that has multiple states. > The size of the interactive panel can be small (i.e. a creeping line) or > large (i.e. a tab page). How to show all panel states best? > > 3. A page includes a panel that is reused on different pages (i.e. as > common > info block), or multiple times on the same page (e.g. item in a list). How > to show the reused panels best, avoiding copying/out-of-sync problems? > > 4. Different notes and different level of detail should be shown to > different audiences. How to create different versions of the same wireframe > best? Also what to do if there is not enough room in the sidebar for all > footnotes? > Steve 'Doc' Baty B.Sc (Maths), M.EC, MBA Principal Consultant Meld Consulting M: +61 417 061 292 E: [EMAIL PROTECTED] UX Statistics: http://uxstats.blogspot.com Member, UPA - www.upassoc.org Member, IA Institute - www.iainstitute.org Member, IxDA - www.ixda.org Contributor - UXMatters - www.uxmatters.com Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
[IxDA Discuss] Managing Complexity of Wireframes
I'm looking for the current best practices of managing complexity of wireframes. What do you do in the following situations? 1. A page includes multiple panels, each of them is quite complex, with many details and notes. How to show all child panels and their notes without cluttering the parent page's wireframe? 2. A page includes an interactive panel, i.e. one that has multiple states. The size of the interactive panel can be small (i.e. a creeping line) or large (i.e. a tab page). How to show all panel states best? 3. A page includes a panel that is reused on different pages (i.e. as common info block), or multiple times on the same page (e.g. item in a list). How to show the reused panels best, avoiding copying/out-of-sync problems? 4. Different notes and different level of detail should be shown to different audiences. How to create different versions of the same wireframe best? Also what to do if there is not enough room in the sidebar for all footnotes? Thanks! -- View this message in context: http://www.nabble.com/Managing-Complexity-of-Wireframes-tp17532426p17532426.html Sent from the ixda.org - discussion list mailing list archive at Nabble.com. Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Expense and income tracking apps?
You can also use www.mint.com, it is one of the best money management tool around in terms of interface/simplicity and works with iPhone as well. Prince Arora www.usabilitymagazine.com www.duxjobs.com On Thu, May 29, 2008 at 5:05 PM, Robert Hoekman Jr <[EMAIL PROTECTED]> wrote: > Dear fellow consultants ... > > Anyone seen a good web app lately for tracking expenses and income? > Something wickedly simple, preferably with a mobile / iPhone UI as > well? > > Cheers! > > -r- > > Welcome to the Interaction Design Association (IxDA)! > To post to this list ... [EMAIL PROTECTED] > Unsubscribe http://www.ixda.org/unsubscribe > List Guidelines http://www.ixda.org/guidelines > List Help .. http://www.ixda.org/help > -- Prince Arora http://www.UsabilityMagazine.com Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Asking questions to participants in a positive or negative way ?
Think aloud evaluation of survey questions is commonly referred to as Cognitive Interviewing. The technique comes from the area of social psychology (where Dillman, Sudman et all that Chauncey mentions come from) and is one method of pre-testing a questionnaire. Other methods include behaviour coding and dress rehearsals. I was trained in the method of cognitive interviewing over the period of a week, full time, so it's not something you can learn well in a hurry. However, I plan to write an article on testing methods for forms and questionnaires for my website in the near future, so keep an eye out. In the interim, you could: - do a search for "cognitive interviewing" on the web - adapt think aloud methods that are used for testing websites - read one or more of the papers listed below - hire someone like myself (in Australia) or Caroline Jarrett (in the UK) to do it for you! "New strategies for pre-testing survey questions" (Oksenberg, Cannell and Kalton) in the Journal of Official Statistics. "Cognitive Laboratory Methods: A Taxonomy" (Forsyth & Lessler) in Measurement Errors in Surveys. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=29233 Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Expense and income tracking apps?
Robert, You might want to check out the mobile app from https://www.clearcheckbook.com/. It works on the iphone and ipod touch.I haven't used it but I used a demo of the on-line tool. - Michele . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=29586 Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Painful Registration Flow
Luke Wroblewski wrote a great article on problems with sign up forms, which was recently published on A List Apart: http://www.alistapart.com/articles/signupforms There's also this from Jared Spool at UIE: http://www.uie.com/articles/account_design_mistakes/ http://www.uie.com/articles/account_design_mistakes_part2/ and from Adaptive Path: http://www.adaptivepath.com/ideas/reports/signup/ and from Bokardo: http://bokardo.com/archives/designing-for-the-social-web-the-usage-lifecycle/ Good luck! Jessica Enders Director Formulate Information Design http://formulate.com.au . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=29536 Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
[IxDA Discuss] JOB: Community experience designer/leader, New York, NY, USA, LIMEBITS, full time
LimeBits is developing an innovative software platform intended to empower people to share their own creations and to collaborate on group creations. You'll join the LimeBits team and help overturn the ancient traditions of software development. Your community interaction design, leadership, and management skills will guide LimeBits's outsource developers and motivate and excite our open-source volunteers. As a key member of the team, you have a blue-sky opportunity to lead us in * Designing and establishing community/team interaction processes to apply and demonstrate LimeBits's share-and-refine model of code development. * Designing and establishing social experience and structure for productive, effective, distributed, grassroots collaboration via LimeBits. * Designing and promoting collaborative, open-source culture and ensuring healthy community morale. * Organizing and producing community-building activities, such as contests, discussions, games, festivals, and conferences, both online and in person. * Managing the specification, development, implementation, delivery, and acceptance of outsourced LimeBits projects. * Creating specifications, design documents, and planning documents for outsourced projects. * Facilitating tests, quality assurance, and usability feedback from community members, testers, and other stakeholders. * Establishing, evaluating, and improving technical project procedures for outsource projects. * Establishing distributed processes and procedures for collaborative projects, including tests, reviews, and reports. * Managing multiple simultaneous projects with diverse collaborative teams and with individuals. * Recruiting, encouraging, motivating, mentoring, and training LimeBits community volunteers and leaders. * Proposing and facilitating compelling, exciting, innovative open-source community projects. * Researching and representing the user community internally within LimeBits. * Networking with community members to identify and realize partnerships. Managing relationships with external partners. QUALIFICATIONS: * Skills in community experience design and team interaction design. * Strong interest in organizational behavior and building community cohesion. * Demonstrated leadership and communication skills in project leadership and management. * 2+ years leadership as software project manager or product manager. * Experience managing communications and relationships with external vendors and internal personnel. * Experience estimating costs and negotiating and implementing external/outsource deals and contracts. * Strong experience in ensuring compliance with software specifications. * Knowledge of the software development life cycle. * Bachelor's, Master's, or Doctorate degree. * Bonus: Experience contributing to open-source software development projects. COMPANY: LimeBits is a startup project in the Lime Group, home to such companies as Lime Wire, Lime Brokerage, and Tower Research. The Lime Group companies offer a dynamic and intellectually stimulating work environment. While we work hard, we also play hard and believe in supporting our team. We provide free lunches, snacks, and beverages, tickets to NY events, 5 weeks vacation, and great views from our garden roof deck. TERMS: Employee or individual contractor -- no contract firms. COMPENSATION: Very competitive. RECRUITERS: No -- principal only. LOCATION: TriBeCa, Manhattan, New York, NY, USA. ONSITE: Fulltime. URL: http://limebits.com/ APPLY: Send your cover letter, resume, and links to [EMAIL PROTECTED] Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Portal Best Practices
Hi, what kind of portal are you building? Corporate intranet or extranet (partners site)? I have been involved with the interaction and user interface design for both. Here are general rules to follow: 1. Ask about the platform. Is it out of the box (Sharepoint, Websphere Portal)? Or is it custom from the ground up? There are implications with flexibility for functionality, features and design (the later being the most flexible). 2. Be diligent with user research. Ask your users about expectations and skill level. If you design a portal that is hard to update for content administrators (stale content) and doesn't engage user with either meaningful content or productive tools people won't use it. 3. Make sure the portal design also includes support for 508b compliance, a help section and a feedback mechanism. Nice to have: a community like functionality, builds involvement. Cheers I hope this helps, Peter . Peter Chung Senior User Experience Designer Customer Experience Group, CNET.com [EMAIL PROTECTED] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=29565 Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] What do you call this?
I think there's a place for both -- one has high interactive fidelity and the other has high visual fidelity. I'm toying with the name "clickframes" as an alternative, so the business folks I meet with don't end up with the wrong expectations. As for keeping copies along the way, I use enterprise wiki software to build my "clickframes" so all changes are tracked automatically. (Granted, they're page-by-page histories, so you can't easily revert the entire site to a particular point in time...) -Jonathan On Tue, May 27, 2008 at 1:55 PM, Katie Albers <[EMAIL PROTECTED]> wrote: > Well, I don't know if it's useful or not, but what you're showing is what I > was taught a wireframe is...and it's extremely useful because as the specs > become more specific they can be added in to the wireframe and you can very > closely approximate the current status of the application/site/product > (always being sure to keep a pure copy of each stage along the way so you > can back yourselves out if necessary). In fact, I've never really understood > why the "visio/omnigraffle/whatever Visually oriented but not functioning > wireframe is supposed to be better. > > Katie > > At 10:27 AM -0400 5/27/08, Jonathan Abbett wrote: >> >> I do this-- >> >> http://www.grokdotcom.com/wireframing.htm >> >> --and it's been very useful. >> >> The author calls it "wireframing," but everyone else in the world says >> that >> a wireframe is a low-fidelity mockup. >> >> Do other names exist for this sort of clickable, text-only, HTML >> pre-prototype? >> >> Thanks, > > Jonathan > -- > > -- > Katie Albers > User Experience Strategy & Project Management > [EMAIL PROTECTED] > Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Usability = Predictability
> > Delight, by definition, is something that is surprisingly good. > > By being surprised, it has to exceed the bounds of predictability. > Best argument yet. Only if it were true. I for one am delighted constantly by eating the food I like, drinking the wine I enjoy, meeting the people I love, revisiting the places I've been to, etc. In fact, a good part of 'delight' is the familiarity and predictability in (re)connecting with what one knows, rather than being surprised. Delight and predictability are in no way mutually exclusive. As to kittens, we already have way too many of them. :-) -- Kontra http://counternotions.com Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Jobs, Events and Plug
The new digest omits jobs, events and plugs (actually, any thread with fewer than five posts). The upshot is that subscribers get much, much less e-mail, and the messages tend to be actual discussions. Members can switch over to the digest on their profile page: http://www.ixda.org/profile.php It's also possible to subscribe via RSS to selected topics: patterns, methods, tools, research, business, events, eduation, announcements or jobs. These feeds are curated by IxDA volunteers. http://www.ixda.org/rss.php // jeff > the best solution would be to have the digest or subscriptions > settings allow subscribers to choose which postings > they want to track. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=29576 Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Usability = Predictability
While obviously predictability is wanted most of the time, I feel like this formulation would lead one to making more explicit (ie wordier) and more consistent (ie conventional) designs. The designs I admire most have neither of these qualities. The designs I admire most tend to have a certain amount of ambiguity, but because of a certain internal logic/aesthetic/feel - users seem comfortable to explore them, click around, figure out a new space, new possibilities. This kind of ambiguity is a requirement in video games, but also can lend other applications a kind of intriguing quality. It's great when users trust the design to give them a good time. Then the design doesn't have to be so defensive or try so hard to be predictable. Also, more and more interaction design is moving into behind the scenes algorithms which aren't really predictable. For instance, you can't predict the result of a search query or you wouldn't need to do it. Lastly, good art avoids predictability and I think there is room in what we do for these softer qualities. I would prefer "possible" or "probable" over "predictable". - Eugene Eugene Chen Design User Experience | Strategy Research Design http://www.eugenechendesign.com . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=29451 Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Usability = Predictability
... the above should have read: 'But predictability, being partly intuitive (the user's responsibility) and partly experiential (the designer/programmer's responsibility), is a key attribute that moves us toward the "plus" side of the usability continuum.' . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=29451 Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Usability = Predictability
Conceptually, I can agree that usability is a continuum (or a scale, as Jared puts it). To the extent that a definition is possible, for the reasons Chauncey points out, I think we _must_ define it. Otherwise we have all the credibility of the ancient alchemist, shrouding our work in mystery and ultimately having it condemned as hokum. The specific components or attributes of usability do vary from one project to another. But predictability, being partly intuitive (the user's responsibility) and partly experiential (the designer/programmer's responsibility), is a key attribute that moves us toward the side of the usability continuum. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=29451 Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
[IxDA Discuss] Need suggestions for long online reading experiences
Hi All, My team is currently designing a report navigation structure that will allow users to fluidly and meaningfully navigate through a long (think 60-100 pages) report. Each report will have multiple sections and sub-sections. Each sub-section will contain both text and information graphics. We know from our research that some users will simply download the full report as a PDF; however, a high number of users will need to easily find, consume, re-use, and refer to only specific sections of the report. Hence the need to guide them to those sections in a quick, intuitive way. I am looking for good online experiences (or real-world analogues) that help users move through long pieces of content. Examples might include features such as: * Persistent table of contents * Quick access to an index * Elegant search functionality * Expandable / collapsible sub-sections Thanks very much! -adam Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
Re: [IxDA Discuss] Usability = Predictability
> Usability is a scale from extreme frustration to extreme delight. > > Delight, by definition, is something that is surprisingly good. > > By being surprised, it has to exceed the bounds of predictability. > > Therefore, Usability != predictability. Best argument yet. And yes, I'll be sure to look out for the kittens, but I'm really more of a patron saint of stray dogs in my neighborhood. -r- Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
[IxDA Discuss] Expense and income tracking apps?
Dear fellow consultants ... Anyone seen a good web app lately for tracking expenses and income? Something wickedly simple, preferably with a mobile / iPhone UI as well? Cheers! -r- Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
[IxDA Discuss] Bounces from the IxDA Discussion List
Hi Everyone, You may have been getting bounces when sending messages to our list. Our service provider goofed and marked our mailing list as active, which caused the bounces. Why were we marked as inactive? Apparently a script they wrote had a bug that mistakenly marked not only ours, bot other lists on their system as inactive. If you're seeing this message, our host has fixed the problem. Please carry on posting away ... Thanks, Nasir Barday Technology Lead Interaction Design Association Welcome to the Interaction Design Association (IxDA)! To post to this list ... [EMAIL PROTECTED] Unsubscribe http://www.ixda.org/unsubscribe List Guidelines http://www.ixda.org/guidelines List Help .. http://www.ixda.org/help
