Wednesday, June 6, 2018

Do icons need labels on mobile apps?


There have already been studies that prove labelling icons enhances usability on desktop applications. This is why Microsoft Outlook started labelling its icons.


outlook icon label



Does the same logic apply to mobile apps? There is limited screen space on a mobile phone. Adding labels to every icon would harm the aesthetic design. I'm thinking of designing my application without many labels, like this popular app:


path app


My theory is that even though users don't necessarily know what all the icons do (three lines, two people, smiley face, plus sign), they will try tapping them to learn what they do. My feeling is that mobile applications are more playful and inviting than desktop applications, so users are not afraid to explore unknown icons. The desktop is a cold hard machine for serious business, whereas your phone is always with you and you interact with it every hour.



Answer



Of course it applies. Limited screen real estate does not invalidate the conclusion that labeling icons improves usability of them. It merely makes it inconvenient.


A user intimidated by desktop app icons is likely just as intimidated by mysterious icons on a mobile. The platform isn't the discerning factor here. The user is. I have seen plenty of people intimidated by their phone. What may well be the case is that the mobile audience in general is a lot younger and more used to just experimenting with an app on a phone to see what happens.


All in all, while I think that labeling icons improves usability just as much on a mobile versus a desktop platform, you are more likely to "get away with" not labeling icons on a mobile platform. Because of the audience, not because of the platform.


resize - Techniques to dramatically scale an image


I have been given an impossible task:


Take a picture image (jpg) at 1422 x 1067 px with 100 dpi and scale it to 86400 x 29376 px (that's equivalent to 34ft x 100ft or 30.5 meters x 10.36 meters)



Unfortunately there are times when a boss requests the impossible from their employee. This is one of those times.


More specifically it was requested that "there be no pixelation (at a viewing distance of 2 feet (0.6 meters)."


The easy (and right) answer is: It can't be done.


But that doesn't mean you can't make the best of an awful situation. So what I'm looking for are techniques, or software solutions that specialize in this sort of huge scaling.


I have heard of something in the past that blows up and image using circles. Granted, it doesn't look great from close up but from a greater viewing distance it looks more held together (like pointillism).


I don't think there is a clear answer, which is why I was hesitant asking here. So I was wondering if this could be transformed into a wiki, because I'm sure I'm not the first or last to be looking up information regarding this sort of scaling.



Answer



I would take a different approach to this, because the task is like wishing for the moon. There's no unicorn filter in Photoshop yet. (And I'm surprised nobody has so far pointed out that Photoshop's pixel limit for a PSD is 30,000 in either dimension, so 86,400 would only be achievable by slicing the image into separate files and enlarging those.)


The problem here is human, more than technical. Your boss has a particular display problem in mind. He/she thinks that the solution is an impossibly small initial image scaled to an insanely number of pixels. We know that's going to look awful, and you don't want your company or your boss to look bad because that won't help anybody.


My response, when I get something like this from a client, is to talk over the actual situation, find out what problem they are trying to solve and then come up with a solution that will work. Make no mistake, you can only do this with a live conversation. Memos, texts, emails are not likely to work. This also requires, on your part, complete sincerity, tact, creative thinking and persistence, in about that order of importance. Sometimes you have to work through some huffing and puffing from the other party, who doesn't want to look foolish or ignorant. (That's where tact and your own sincerity of purpose to find the best possible solution will help enormously. When the other party realizes they're not being made wrong, they don't have to insist on being right.)



Do what Marc suggests and run some tests with a portion of the image so you have something to "show and tell." But don't use this as a club to beat the boss into submission. You have to be on his side.


Keep asking questions until you completely understand the challenge your boss is up against, then come up with the right solution. If you make it seem like his/her idea, so much the better.


Tuesday, June 5, 2018

website design - Do you have a "formula" for the webfont vs graphic type threshold?


Disclaimer:
I realize there is not a perfect "formula" for this question. I'm looking for your experiential working practices. If you don't have any, I won't hold it against you.




Over the last couple of years, webfonts have finally gone mainstream! Browser support is good enough and the market has broadened to the extent that designers have an excellent range of possibilities.


For my performance-focused clients using webfonts has some nice benefits beyond visual/branding: Getting type out of images makes greater image compression possible and content and style updates much faster.



The question today is:
At what point do you make the break from live html text to graphics? Especially in the context of a site with high performance requirements (loads of traffic, logic, and third party assets loading). I'm walking the line in a few projects now and having a hard time deciding in some cases. I'm wondering what formula others have come up with. If any.


We need to balance several factors (I know there are more):



  • Typographic integrity

  • Asset requests made to the server

  • SEO and accessibility

  • Responsive design (where applicable)


Complicating matters, rendering still varies widely by browser and OS. Compare IE 8 to 9, for instance or, more dramatically, OS X to Windows. Obviously, your market may negate concern for some of those issues (I unfortunately still support back to IE7 in a big way on some projects). And while webfont OpenType feature support is pretty good in Firefox, it's still lagging in virtually all others.




Answer



Okay, I'll weigh in with where I'm at, since there don't seem to be any fixed approaches popping up.



For starters, the days of sketchy webfont rendering will be completely behind us soon, at least with well-made fonts. The main offenders (IE versions prior to 9) are fast becoming a thing of the past. IE 8 is still a player but I'm convinced that audience is not an aesthetically motivated one anyway ;)



System/HTML text can easily handle changes to
color,
opacity,
scale,
horizontal and vertical positioning,

and text shadows.


When my effects start getting complicated, I consider it an obvious graphic type moment. Beyond simple style controls (anyone care to add to my list?), you'll need to rely on
javascript libraries,
OpenType features with spotty support,
excessively large webfont downloads on the user's end,
and possibly HTML5/CSS3 features with limited support.


If I want to skew my type,
fine-tune the kerning,
apply textures,
precisely position and line break it over an image,

or anything else that requires precise control, I resort to a graphic.
Like I said, there are ways, I just don't think they're worth it at this point.


With that said, I also have to ask myself in those cases if I really need the effects. Could nicely set system type without all the fancy stuff do the job. Maybe. There's always a fuzzy line somewhere.



Where I find myself hesitating to trust webfonts is very large type. Just to throw out a number, let's say 60px and up. Why is that? I'm not entirely sure but I can think of a couple things than concern me.


For one, big type often requires that extra bit of kerning that simple tracking can't solve. The type is dominant on the page and every little flaw becomes painfully evident to me.


Secondly, type that large tends to require very careful fitment within the design. I think it's less critical on content sites where the type can flow and there's some much needed white space but on a commerce site or in a dense content environment a misplaced line break or extending character can wreak havoc.


I think these may just be insecurities left over from the days when browsers did a really bad job with type. Unfortunately, enough of those problems still linger that it makes me cautious. Things like Giantnerd's add to cart button make me want to embrace it :)



Well, maybe not final. Final-ish.



Despite my insecurities, I'm getting past the big type thing. And I find myself using less effects and more clean system text elsewhere. One of the big gains is more responsive layouts: System text is easy to change on the fly!


I am rapidly streamlining my clients sites and moving to less image dependency. Bring on the webfonts! Maybe it'll be another International Style revival period in design ;)



I would be remiss to not mention awesome excercises such as Lost Worlds' Fairs. It's wonderful proof that just about anything is possible given time and the right user base.


Jason Santa Maria's contribution to beautifying the web


adobe illustrator - Pathfinder bug - doesn't cut the exact path


I've been trying to go through a basic tutorial.
When I get to Step 7 (of creating the main two shapes), I need to use pathfinder to intersect between two shapes. But the intersect function's outcome is not exact (and actually other pathfinder functions.) I believe it's a bug.


This is how it looks with maximum zoom before the intersection: This is how it looks with maximum zoom **before** the intersection:
And This is how it looks with maximum zoom after the intersection: And This is how it looks with maximum zoom **after** the intersection:


You can clearly see that the intersection wasn't made where the exact path of the yellow shape was, but a little bit downwards of that.


Here's two .ai files that correspond to both states for you to download: Before and After.



Answer



You can increase the precision of pathfinder from the hamburger menu. This will alleviate the problem a bit.


enter image description here



So if you set a smaller value into the setting you will get a closer match. However, please note that this will keep happening in many cases if you zoom close enough. It is a unfortunate side effect of how the rendering happens. For it not to really even begin to happen you should also add a point to the underlying shape. Which is why shape builder keeps adding those damn points. It is the correct thing to do in your case, but damn i dont always want to do what they think i am doing ;) So one can not always win.


photo editing - What should I do when scanning hand drawn images?


My friend is an illustrator and has lot of sketches that she wants to digitize to put online. She is also working on a children's book.


How should she scan the images and what are some beginner steps that she can take to clean them up once digitized? I'm guessing the clean-up will be necessary just from the scanning process.



Answer



Are they line drawings or shaded drawings? If they're line drawings, the most common method is to scan as Black and White, trace the artwork using the pen tool (or freehand strokes with a brush) on a different layer, and work from there.

If it's shaded drawings, she should consider scanning either as greyscale (for black and white drawings) or full color (for color shaded drawings) and go from there. Depending on her comfort level with Photoshop / Illustrator, she could do her shading in Photoshop or Illustrator (multiple tutorials exist online for this).

Keep in mind that photocopy-invisible blue pencils ("no-repro blue") will often be picked up in a greyscale scan, so if that's a technique she uses prior to inking the blue lines may still show up.


color theory - How do you choose 'light' and 'dark' shades in Google Material Design


From the Material Design docs:



To create contrast between elements, you can use lighter or darker tones of your primary color. The contrast between lighter and darker tones helps show division between surfaces, such as between the status bar and a toolbar.



Looking at all the examples in the Material Design docs, light and dark colors are chosen from the same swatch as the base color. So for example, if your chosen color is 'Blue Grey 700' your light and dark colors may be 'Blue Grey 300' and 'Blue Grey 900'. This is one of the examples they show:


enter image description here


Using Google's Material Design Color Tool, we can select the same color, 'Blue Grey 700'. However, it suggests light and dark colors that are not from the 'Blue Grey' swatch:



enter image description here


For reference, here is the 'Blue Grey' swatch. You can see that the light (#718792) and dark (#1c313a) colors are not present:


enter image description here


The material design docs state:



They’ve [the M.D. colors] been designed to work harmoniously with each other



Should I use light and dark colors from the color swatch, OR can I just trust the Color Tool and use its suggested colors?


If I should trust the color tool, how does it generate the light and dark colors?




Monday, June 4, 2018

creative writing - Am I breaking the "show don't tell" rule in the following passage?



Then, as if sensing my presence, the girl turned around. She looked young. Probably sixteen or seventeen. She had long black hair, crimson red lips, and a skin so pale it made me wonder whether she had blood at all. But what struck me the most were her eyes. Even though there was nothing unusual in them, they made her face look lifeless, completely devoid of expression. It felt strange. Like staring at an empty canvas.



In the last part I'm telling the reader the girl's eyes make her face look lifeless. I didn't actually describe them (e.g. they were black, white, etc.) But, I don't know, I think I'm also showing the reader how her face looks by stating what it's lacking?



Answer



Rules are there to be broken, and here you break this rule masterfully.


Yes, that is "telly", but being surrounded by entirely "showy" parts, assuring the reader that you were diligent with the descriptions, you suddenly discard the looks and throw the impression instead; it's jarring - as it should be. It draws the reader's focus, marks the information as especially important, contrasting it with the generic description surrounding it, making that part stand out by just making it sink through telling that to us directly, overshadowing the importance of normal appearance.



Leave as is. Yes, you broke the rule, and you did right.


technique - How credible is wikipedia?

I understand that this question relates more to wikipedia than it does writing but... If I was going to use wikipedia for a source for a res...