Jakub Linowski's Comments

Jakub's Thoughts : Interactive Sketching Notation v1.1

Fri, 15 Jul 2011 03:13:19 +0000

Hi Andy, Would love to hear more in terms of what you had in mind. Could it work to use the smaller state screens to show what changed, after someone has done an action? Maybe there needs to be an explicit symbol to denote that a page does not refresh - is that what you had in mind? Jakub

Wireframes : Personal Pattern Books

Mon, 30 May 2011 01:33:28 +0000

Hey Hayley. Still haven't indexed anything. Maybe just because right now I've only recorded 5 of them. Could be a good idea down the road perhaps.

Wireframes : Personal Pattern Books

Fri, 27 May 2011 20:59:10 +0000

So far I just posted one. Did you click on the image in the post?. Maybe I should of shared more? :)

Wireframes : PowerMockup

Thu, 28 Apr 2011 01:59:12 +0000

Sure, for interactive prototyping there might be more advanced tools. I still think however that the linear narrative nature of PowerPoint and its low barrier to entry makes it an attractive communication tool. I mean, a screen by screen presentation mode is still quite awesome for showing off flows (a different intent from interactive prototypes). So I have to disagree with you and I wouldn't cross this off the list so soon.

Wireframes : Exploring UI Scaling

Mon, 18 Apr 2011 19:47:11 +0000

Just worked in a subtle visual "plus icon" cue to hint that there is a bigger screen shot. Hope this helps. Cheers :)

Wireframes : SketchWizard

Mon, 25 Oct 2010 20:47:39 +0000

Funny :) Well, you're right - there is more pressure from using a tool like this on the designer. But without crossing this off the list, perhaps I forgot to mention that the tool allows to predefine states or screens in advance. Thus, all the designer has to do spontaneously is the "flipping" of screens. The "drawing up" of screens could still be done in advance (or on the fly). Just thought to add this. Cheers.

Wireframes : onProximityFade jQuery Plugin

Thu, 5 Aug 2010 23:45:32 +0000

Agreed. This experiment could be a band aid like fix for something that shouldn't happen in the first place, and the accessibility of it is questionable as well. I did want to add that initially I envisioned the list of links actually being composed of the same actions (ex: repeatable and predictable "add" or "edit" links that sometimes appear on each row). This way, the user knows they're there but they don't clutter the space as much. But maybe it's one of those failed experiments :)

Wireframes : Sticky Floating Navigation

Tue, 6 Jul 2010 15:34:05 +0000

Some nice examples you all found! Thanks for sharing the links. I've noticed a few superior examples (faded and narrower than the column width) which tackle the issue of mistakenly making the scroll bar "feel as if it's broken". @Jarrod. I'd say when the need arises for a larger visible screen area, these floating navigation could potentially collapse on mouse out. @John Beckett. The floating footer could be useful when you have long scrolling pages and a multi step process. In my case I wanted to show very visibly a critical element such as the continue / submit button in a consistent location.

Wireframes : Sticky Floating Navigation

Wed, 30 Jun 2010 13:52:29 +0000

Hey Jeff, At least in this case, the footer is already expanded so the user probably doesn't need to scroll down. Although an expandable interaction could work as well if there was more content inside.

Wireframes : Cursor Affordances

Wed, 30 Jun 2010 04:18:51 +0000

Hi Ronny. About your comment: "And I don't agree about advertising those features to the users using banners, default tooltips and such - This is poor usability." Isn't the option for left clickable items already being advertised in all web browsers with a cursor change? I'm simply suggesting subtle use cues or affordances that can be learned and which extend the traditional left click to other advanced interactions which aren't yet visible.

Wireframes : Experimental Challenge

Fri, 4 Jun 2010 17:11:40 +0000

Hey Stefan. It would be awesome if you think of a solution that you'd be willing to share. Do let me know! :) Cheers

Wireframes : Cursor Affordances

Thu, 20 May 2010 17:14:48 +0000

Hi Stefan, All good points. I wonder if taking this to the browser level in the form of a plugin might be another option. More advanced users might then potentially disable this, or it might get automatically disabled on its own for sites that are visited frequently (where the interactions are already learned). Taking it to the OS level would probably be better, but might require more negotiation?

Wireframes : Cursor Affordances

Thu, 20 May 2010 17:10:03 +0000

Agreed that the buttons could be stronger and more intuitive. Not sure if there would be a case though where all the actions are enabled. If they were, then you're right, it might be a bit of an information overload case. Thanks for the feedback!

Wireframes : Cursor Affordances

Thu, 20 May 2010 17:08:04 +0000

That's an interesting take on the whole concept as well!

Wireframes : Cursor Affordances

Thu, 20 May 2010 16:58:20 +0000

Maitika. I like the comment around the potential of this becoming annoying. It makes me wonder if A) a more subtle solution could make this work better, or B) a solution that diminishes in visual strength over time as the user learns certain actions behind the interface. Another idea for implementing this could be C) where this becomes a setting or plugin in the browser (possibly enabled for new pages that you visit and still need hand holding). Anyone from Mozilla reading this, or know how to build Firefox plugins? :) And I am also liking the idea of using a real mouse symbol to convey these actions. Could be more intuitive. Agreed.

Jakub's Thoughts : Cursor Affordances

Thu, 20 May 2010 16:51:00 +0000

I think the metaphor of showing the mouse as the indicators has quite some potential! Thanks for sharing.

Jakub's Thoughts : Cursor Affordances

Thu, 20 May 2010 16:49:24 +0000

Hey Tom. I totally agree about it looking too much like an infinity sign. :) I also think there could be a clearer way to convey these actions. Thanks for the comments.

Wireframes : Grand Narratives & Play Points

Fri, 14 May 2010 05:21:01 +0000

Hi Lisanne, I think you hit the nail on the head here, in that this is work in progress. Hence I just started an "Experimental" category and moved the post in there as well. You're also right about the bottom screen having no real interaction links (thiner lines) and that would be my mistake. Typically it actually would have some kind of interaction to get the user there. So, my bad. As to the bigger question in terms of what this is trying to achieve, I think I'm exploring the idea to visualize intent. The starting point for each thicker line is a Play like symbol that would indicate the intent or larger story that the user is trying to achieve. Perhaps sometimes I find that by documenting these "smaller" interactions (clicks, hover), the larger picture of what the user is trying to do gets lost. That's where these grander narratives could come in. Again, it's all exploratory work :) More feedback or alternative ideas of your own would be great. Best, Jakub

fluidIA : Scenarios (Experience Threads) v.3

Thu, 29 Apr 2010 23:36:48 +0000

Cool! Here are some thoughts: 1) I think what this idea really shows is that there are two ways of recording interaction. One as your showing, is a more abstract way less defined way (where page relationships are shown but they don't really say how one person goes from one page to another). Second, a more refined way would be to record the detailed interaction (click, hover, typing, etc) as well as giving it a specific position on a page. This idea of less defined / more defined goes 100% fully with what I've been trying to push forward with this product as part of the concept of "flexible fidelity". Namely, designers at times will sketch out work in a less or mote detailed way depending on their state of mind. One quick example of this is the text tool where you can draw a few lines of dummy text very rapidly (low fidelity) but then you can come back to it and give it more detail by typing actual words (high fidelity). So thumbs up for doing this! 2) Having said that. I say the detailed way of recording interactions (with position) as they already occur now, is priority for 0.1. I think we could do this perhaps later? 3) Perhaps you already envisioned it this way, but I think the interaction defined in the detailed way should be automatically visible in this sitemap view, in that both views are always in sync. Earlier on I've also started thinking about the concept of automatically generated site map documentation visible here:http://fluidia.org/wp/2009/03/auto-create-design-... Having said this, I still feel we need to work more on ironing out the details of representing and recording the detailed interactions of complex interactions such as drags, movement, transitions, delays, durations and timing in the context of the existing experience thread functionality. That's probably priority for 0.1 If someone wants to take this on, that would be great. We could have a more discussion about this if required. Sounds good? Jakub

Wireframes : Usability Test Snapshots

Thu, 8 Apr 2010 16:22:34 +0000

It's a little idiosyncratic. I agree. Will be working on another more high level deliverable some time in the future. Stay tuned. Would you have a sample you'd be willing to share? :)