Blog
Unity 4.x Pro Mirror Reflection Limitations
I have been working with Unity 4.3 Pro for the past week or so. The first Pro feature I wanted to try was render-to-texture, so I looked up examples. First thing I noticed was mirror effects suck. There are major limitations to the example scripts, and I have no idea how to get past these limitations at the moment.
Touch-based web app design problems
I attended a course on mobile web design and it got me thinking about the compatibility of the web with touch-based devices. Touch-based devices do not have the same design issues, but that difference creates a more complex overall design challenge. How do we target both touch-based and mouse-based devices?
Advantages of mouse-driven design
- Mice can hover over elements. Hover effects are often taken for granted, but on the web, that feature is very useful, because it allows certain screen elements to only take up space when the visitor needs to see them. There are some workarounds for designing without hover effects, and hover effects are often used poorly, anyway, but designing without hover effects makes the amount of interactive possibilities for the web less varied.
- Mice can more easily traverse small screen elements and therefore allow for much more data and visual stimuli to be presented on the screen at once. On the other hand, if designing for touch-based and mouse-based devices, you will have an easier time scrolling through the content using a mouse wheel than you will holding and dragging the screen with your finger. Therefore, not only is mouse-based design easier on screen real-estate but it is also useful for traversing larger pages.
- Mouse-based devices tend to have larger resolutions with larger screens. As screens get cheaper, touch-based screens will always be more expensive and therefore be smaller than traditional screens. The larger screen means tinier elements will be easier to read from a distance and the screen may support a higher resolution, and the higher resolution means more screen real-estate for a web page design.
Advantages of touch-based design
- Mice can click and drag, and so can touch-based devices, so any design that is for touch-based devices will work for a mouse, as well... as long as we are not using gestures or multi-touch.
- Mobile web has always been mostly keyboard-based and only recently started entering the tablet space. Thanks to touch-based phones becoming popular, we no longer have to design web sites to be keyboard accessible. However, I would hardly call this a good idea. It is simply an advantage of the trend. Traditional computer users still use their keyboards to navigate scroll bars and drop-down lists and form elements. However, most of that functionality is already taken care of for you by the web browser.
- Eventually, this trend of touch-based devices getting bigger will end with everyone utilizing computers with phone features being a standard add-on service, and screen size will be even more varied, so supporting touch-based devices now and allowing your sites to be flexible will benefit you in the future, as well.
Methods to handle both types of design
- Utilize a different subdomain or subdirectory for each type of device or interface. Perhaps use m.domain.com to handle your mobile site and www.domain.com or just domain.com for the regular version of the site. You could utilize the same database and basic logic for both interfaces but build the pages in a different way.
- Design an interface that looks different at different resolutions using clever CSS tricks and possibly some JS effects. The key to accomplishing this is to use more than one style sheet. You could have a mobile style sheet and a non-mobile style sheet. The problem with this is there is not a reliable way to check what kind of device the visitor is using.
- Design a generic layout that scales appropriately for any resolution and looks practically the same on all devices. Do not rely on hover effects to signify that something is clickable, because mobile devices and touch-based devices will not support such functionality. You could include hover effects as an extra effect for traditional viewers, though.
Cautionary tales of web design
- Use JavaScript sparingly. A lot of web sites not only utilize JS but rely on it for practically everything, meaning that they may appear to be blank pages to some users, especially those users who like to disable JavaScript or use NoScript. You should design your web interfaces to only rely on JavaScript where it is necessary, if at all.
- Try not to design for fixed widths. Make your designs flexible. Refrain from maximum widths unless you are concerned for readability of paragraphs, in which case I suggest scaling the font size and line height with CSS.Minimum widths are useful for certain types of elements but should be avoided as well, because mobile devices tend to have very small resolutions. I recommend using percentages to control the width of almost all screen elements.
- Remember to make a print-friendly version of your design. Many sites do not do this, but it saves on ink when visitors want to print out your articles or whatever other data you may provide. The trick is to have a separate CSS file for print. Most browsers support print versions of your CSS.
Funny how web traffic turns out.
I get about 59 spam comments per day, and about 80% of the comments are made on my Design Patterns Primer article and my GW2 April Fools post. Traffic-wise, however, about 90% of my traffic comes from getlives.com, which is a locked down game reviews site that I get a lot of bot traffic at for some unknown reason. Spammers pretty much took over my forum there, and I was tired of making game reviews that few people were actually reading, so I shut down registration and locked the forum. I intend to turn that site into a web comic in case anyone is curious.
- « older posts
- newer »