Absolutely agree.
On Apr 24, 2009, at 8:42 PM, Adrian Howard wrote:
I guess what I'm trying to say is that it's the "pushing" that's
needed. Whether you're pushing against the constraints of the medium
from the outside or the inside - you need to push.
Cheers!
Todd Zaki Warfel
Principal
On 24 Apr 2009, at 22:34, Todd Zaki Warfel wrote:
[snip]
We start all of our designs sketching w/pencil or pen and paper.
This allows us to be uninhibited and explore new models, allows us
to push past what the environment might allow for. Then, because the
stuff we typically come up with i
Some of us seem to be assuming that the footer contains a site map,
straight up. And others are assuming it could be that OR a context
sensitive area for calling out interesting or related material /
resources.
I'm not thinking about lost users at all - if a user is lost and
needs a site map, then
On Apr 24, 2009, at 5:03 PM, Adrian Howard wrote:
The flip side argument to that is if you start outside the box and
compromise you end up with something that's... well... a compromise.
We start all of our designs sketching w/pencil or pen and paper. This
allows us to be uninhibited and ex
I love this post! It's very pertinent to what the design team I'm on
is dealing with, particularly communicating requirements to
developers.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Posted from the new ixda.org
http://www.ixda.org/discuss?post=41485
_
Yes, thanks Ambrose. I was keeping that message to reply to later when
I had time. You've saved me the effort. :)
Best,
Jack
On Apr 24, 2009, at 4:51 PM, Jared Spool wrote:
Ambrose,
Right on the mark.
The "us" vs. "them" attitude never works. We're all in this together.
Jared
Jack L
On 24 Apr 2009, at 21:24, Jack Moffett wrote:
Personally, I consider this to be a poor approach, as it will tend
to limit your thinking about a solution to what you know is
implementable. I prefer to keep implementation in the back of my
mind while designing the solution. I will quite ofte
The few I know of this mindset are also of the Deep Java sort. They create some
fantastic applications that do complex functions in a way I couldn't
comprehend without
a Cray and a tank of nitrous oxide. Some folks just love that, and
even if intellectually
understanding the role and purpose of U
Jared - thanks for the reference! I will have to check it out :) Lots
to consider
AJ - Yes, it's a conundrum. Some of my coworkers have suggested that
it's not necessarily that the fields are there on forms, but that
they require us to fill them in. The thought is, "if I want to give
more info, gr
On Apr 24, 2009, at 11:28 AM, J. Ambrose Little wrote:
Overall, I think you have some valuable insights, but the way you
express
them belies what I think is a wrongheaded approach to interacting
with devs.
The subject line as well as numerous things in the text imply a goal
of
manipulating
On Apr 24, 2009, at 4:54 AM, Coryndon Luxmoore wrote:
> So, while people see them as helpful, the real question is if the
experience of the site is diminished when they are absent. If users
don't miss them, then why make the investment?
I would flip this question around a bit and ask does
On 24 Apr 2009, at 17:52, Scott McDaniel wrote:
Almost
all of my friends in SFO, for example, own an entire vertical of
their projects/products -- from back-end to IA to front-end. It
~blows my mind~, and some are miserable about it, but I don't get the
impression it's a Bay Area USA methodol
>>I will say this, I think that the Bay Area has many more do-it-all
developers/designers. My experiences as a dot-commer in SF actually made me
into the generalist I am -- there was a much greater, um, respect (?) for
the well-rounded geek
Being originally from the Bay I 100% agree. Southern Calif
Personally, I consider this to be a poor approach, as it will tend to
limit your thinking about a solution to what you know is
implementable. I prefer to keep implementation in the back of my mind
while designing the solution. I will quite often have to make some
compromises when I get to i
I think that we've probably all seen situations all across the
spectrum - but ideally I think that HTML/CSS creation and prototyping
belong earlier in the process, so that interative design can take
place and as mentioned above, when it's time to implement the system
(theming in Drupal, .aspx in .N
I get to write the html/css code pretty often in the case of web apps.
Some times we use frameworks like Eclipse or custom Java apps, and
time constrains make it hard for me to keep up the learning effort.
However, I keep myself involved during the implementation iteration
as a UI "quality assu
Hi Jonathon,
Overall, I think you have some valuable insights, but the way you express
them belies what I think is a wrongheaded approach to interacting with devs.
The subject line as well as numerous things in the text imply a goal of
manipulating and controlling and conflicting (and even condes
@Chris -
Dude that's super cool! Online social collaboration is so awesome
when you see it working in action.
@Pascal -
Yes, I think discoverability is really the big issue (although a good
issue to have :)
You know what else I was thinking about the ratingsthe rating
system should have
I guess I'm just touchy.
I've also followed that career trajectory, though I actually started with
something more akin to über-traditional IA (building taxonomies for search),
then made my way from back-end towards the front, now splitting time between
front-end development and IA/IxD.
I will say
I'm usually the touchy one, so I can't judge harshly.
About the Bay Area, it is interesting, and I think there's a strong
case to at least be conversant in d) all of the above (as Andrei
Herasimchuk would probably Argue Strongly For), and minimally, I've
rarely encountered
anyone with an IA, UX or
I do think there is justification for a site like target.com, where
browsing products is the primary use case and dominates the global
navigation, but there are also clear-cut ancillary use cases that
must be served.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Posted from
I typically do all HTML/CSS/JS and then hand the templates over to
development to integrate with their application platform.
This approach works pretty well for us since we're not doing much in
the way of static wireframes anymore. We'll use Axure if absolutely
necessary but most of the prototypes
On 24 Apr 2009, at 12:49, AJKock wrote:
So do you only ask name, email and telephone number the first time and
loose out to a competitor that already sent a qoute on the first
contact or are you that competitor?
[snip]
Why not get the absolute minimum information first, and then give the
cu
> On 24 Apr 2009, at 15:52, Jonathan S. Knoll wrote:
> [snip]
>>
>> My experience, in both agencies and large corporations, is that the
>> front-end team tends to be semi-autonomous, but organizationally closer
>> (and
>> often beneath) the back-end or systems teams. Ironic, since the good ones
>>
On 23 Apr 2009, at 04:37, Chris Neale wrote:
[snip]
I think name (single field) and contact number should be mandatory.
Nearly everyone has a phone number of some sort and a conversation
over the phone is a more personal way to begin than an email.
[snip]
There are a lot of databases out there
>
> The ellipsis: Open File.. and Save As... imply that a name of the file
> is required, rather than confirmation.
I think in mainstream use it really just implies a very generic concept of
"input is needed from the user before the action will occur". E.g. in Mac OS
X, go to the Finder menu and
Ok, B-ham, USA (something you might want to make clearer on this list,
btw).
I got excited when I saw this, but that weekend, I can't make it.
Bummer, as my sis lives in B-ham, AL and I would have loved the
excuse to go visit.
- dave
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
On 24 Apr 2009, at 15:52, Jonathan S. Knoll wrote:
[snip]
My experience, in both agencies and large corporations, is that the
front-end team tends to be semi-autonomous, but organizationally
closer (and
often beneath) the back-end or systems teams. Ironic, since the good
ones
tend to be mor
This is exactly to the tee what an Interactive Producer does.
On Apr 24, 2009, at 8:02 AM, Jonathon Juvenal wrote:
Following are my 13 lessons
that have helped me get better results from the developers I've
worked with.
1. Be a developer
I can't stress this one enough. Development isn't somet
http://www.att.com uses this navigation method as well and they call
it a "link farm"
I agree with Jared in his questioning of the investment.
I think these "link farms" are actually a way to appease the
business people who want their links on the front page.
Its a way for designers to clean
On 24 Apr 2009, at 07:39, Richard Dalton wrote:
Who codes your production quality HTML/CSS/Javascript? Where in the
organization do they sit and do they do more than just
HTML/CSS/Javascript (ie, Java, mid-tier, etc)?
I'm trying to gauge how closely connected to the Design resources
they are,
Richard,
My experience, in both agencies and large corporations, is that the
front-end team tends to be semi-autonomous, but organizationally closer (and
often beneath) the back-end or systems teams. Ironic, since the good ones
tend to be more philosophically aligned with Design teams.
The level
Earlier this week at the local Utah IxDA meeting and over the last
while at various places I've heard the topic of how to deal with
developers come up. I was thinking about it and realized I had a lot
to say about it. Sorry for the length :)
I currently work at a very small company, less then 20
I am more in line with Dave. It always depended where I was and what
role I played. Sometimes there was a front-end developers for the
role, sometimes a developer who did fron and back-end, and sometimes
my stuff was used.
But as I moved away from working on web sites to more working on
applicatio
Have you attended any of the AIGA events?
http://www.aigany.org/events/events_upcoming.php
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Posted from the new ixda.org
http://www.ixda.org/discuss?post=41476
We
Jared mentioned that a "sasquatch" footer might be an indication
that your site lacks sensible / complete navigation elements. That
could definitely be true.
But, I think that precludes the case where the footer area serves as
an instant browsing tool. It's true that many users are on the site
for
BarCamp Birmingham 3
Saturday, May 2, 2009
9am - 4pm
http://barcampbirmingham.org/
See the website for more information.
If you are near Birmingham, come over. We'll have some talks on IxD
and would love to have more interaction designers take part.
___
It varies somewhat, but I typically implement the HTML and CSS, while
the developers do the JavaScript. I know HTML and CSS better than the
developers do, and I don't know JS. There are times that I'm too busy
to deliver HTML and CSS (I'm shared across many projects), so there
are times th
I have nothing to add to this thread, except to add momentum to a meme that
I hear from time to time, as a better name to call these things, these "big
footers."
My favorite name for the "Big Footers" is Sasquatch. Please feel free to use
it as you see fit.
Chris
On Wed, Apr 22, 2009 at 1:49 AM,
I do.
An interface implementation team from the design side does the html+css
(data structure + styling) and the development team does js (behavior).This
approach allow us to decreases production time.
Regards,
Ricardo Seiji
On Fri, Apr 24, 2009 at 4:39 AM, Richard Dalton wrote:
> Who codes you
This has been an "it depends" question for me.
1) It depends on where I was in my career. The higher up I went the
less likely I was coding. (the same is also true of graphic
production.
2) It also depended on what I was designing for. The question is
biased towards Web design. Not everything I've
I like IxDA NYC events a lot. But I am also interested ones that are a
bit more visuals- and graphic-design-oriented. Do you go to any
similar NYC events/communities that are more along those lines?
Welcome to the Interaction Design A
Who codes your production quality HTML/CSS/Javascript? Where in the
organization do they sit and do they do more than just
HTML/CSS/Javascript (ie, Java, mid-tier, etc)?
I'm trying to gauge how closely connected to the Design resources
they are, are they more aligned to Design or more to Developm
2009/4/22 Erin Lynn Young :
> - www.target.com uses this type of footer
> - www.solarwinds.com does as well.
More examples: http://www.flickr.com/photos/factoryjoe/sets/72157594487444992/
--
Danny Hope
07595 226 792
@yandle
Welcome
2009/4/22 Jeff Geurts :
> If it were indeed a site map, then I would suggest linking to it from
> a top-level navigation area. There are more users familiar with a
> typical site map link than with scrolling to the bottom of the screen
> to find it there.
Can you point to evidence of this?
--
Da
> So, while people see them as helpful, the real question is if the
experience of the site is diminished when they are absent. If users
don't miss them, then why make the investment?
I would flip this question around a bit and ask does it noticeably
improve the experience for some users sin
I am actually sitting with exactly this problem. Consultant needs vs
User Experience
I work in the travel industry and our consultants would like to give
an appropriate and complete quote for a client after first contact,
but this would require the client to complete lots of fields in the
enquiry/
Hi everyone !
If you don't know them yet, you'll probably may be interested in
these websites :
http://www.bookglutton.com/
http://www.dailylit.com/
http://books.google.com/
You also should take a look a the review feature in MS Word.
I hope it will be usefull.
Etienne
http://www.linkedin.com/i
48 matches
Mail list logo
