tag:blogger.com,1999:blog-2902949051864384839.post7178027569444547627..comments2023-11-05T03:32:45.996-06:00Comments on donttouchme: Design for Every ScreenSteven Hooberhttp://www.blogger.com/profile/02906610345363264283noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-2902949051864384839.post-30480431357092465352016-05-28T07:26:38.725-05:002016-05-28T07:26:38.725-05:00Both products offer similar basic features: graphi...Both products offer similar basic features: graphical design and code views as ... Expression Web offers little help if you want to make your site mobile friendly. Usability. Dreamweaver is vast and includes tools to do almost anything that can be. See more <a href="http://www.fixmobileusabilityissues.net/how-to-build-a-wordpress-mobile-version-of-website/" rel="nofollow">wordpress mobile version</a>Anonymoushttps://www.blogger.com/profile/04571828795230778384noreply@blogger.comtag:blogger.com,1999:blog-2902949051864384839.post-26455354869044696892014-03-03T04:12:07.001-06:002014-03-03T04:12:07.001-06:00Well! I think he requirements were basically ident...Well! I think he requirements were basically identical for each platform, to the point that the IA diagram included the common widgets that are used for each screen or state. But one guy built the iOS version. A team of three guys built the eReader. Another team built the website......<br /><a href="http://www.chinavasion.com/china/wholesale/Android_Media_Players/" rel="nofollow">Android Box TV</a>Anonymoushttps://www.blogger.com/profile/06078187053840094428noreply@blogger.comtag:blogger.com,1999:blog-2902949051864384839.post-52615620155997923922011-12-21T08:46:46.621-06:002011-12-21T08:46:46.621-06:00I have continued to refine this concept, and gave ...I have continued to refine this concept, and gave a presentation on it at MoDevEast a few weeks ago. You can see that at Slideshare. <br />http://www.slideshare.net/shoobe01/design-for-every-screen<br /><br />And, for even more detail on mobile-specific processes and patterns, be sure to check out my new O'Reilly book Designing Mobile Interfaces.<br />http://4ourth.com/wiki/Steven Hooberhttps://www.blogger.com/profile/02906610345363264283noreply@blogger.comtag:blogger.com,1999:blog-2902949051864384839.post-69536145267615058442011-11-10T12:16:54.143-06:002011-11-10T12:16:54.143-06:00The conversation at IXDA kept going, and is quite ...The conversation at IXDA kept going, and is quite useful. Read it instead of me re-posting everything.<br /><br />http://www.ixda.org/node/31363Steven Hooberhttps://www.blogger.com/profile/02906610345363264283noreply@blogger.comtag:blogger.com,1999:blog-2902949051864384839.post-54364526096181920622011-11-10T12:15:11.591-06:002011-11-10T12:15:11.591-06:00This comment has been removed by the author.Steven Hooberhttps://www.blogger.com/profile/02906610345363264283noreply@blogger.comtag:blogger.com,1999:blog-2902949051864384839.post-69278902337443267392011-11-08T13:27:25.406-06:002011-11-08T13:27:25.406-06:00For posterity, part of my answer to a response tha...For posterity, part of my answer to a response that came from another channel, since it's important. <br /><br />Good points. Let me take on the write-once thing most of all. It wa getting to be a long discussions so I left out some details; plus, it's a post about self-discovery, so I forgot what else I was assuming. Maybe I'll jsut pitch this as my next book. I could easily write a couple hundred pages on it. Anyone want to pay me for this? <br /><br />Instead of more theory, let me use a real example (a bit sanitized in case no one wants me to share it… so also therefore, I won't share the actual diagram, which is sadly pretty cool and explains it real well).<br /><br />I worked a couple years back on an eReader project. Requirements from the corporate masters were more than a bit vague, so we me up a target audience, and requirements, and so on. But a few key things is that it was going to be hardware (and actual eReader) and a platform so it worked on all sorts of other devices, and could be ported to other dedicated hardware, maybe. <br /><br />So, in this case, I made a single IA for everything. Which took a couple iterations to get right, but I am very pleased with where it ended up. It was a platform/technogy/input/output/context-agnostic IA for the product. But when executed it was one the SAME IA for every channel. The web portal had a portal landing page. Which did not even exist on the eReader, which was centered around the reading experience so landed on the last page of the book you were reading. And the eReader had device settings, which were the same place, architecturally, as the preferences for every other channel, but had device-specific hardware settings, and was accessed in a device-like manner (via a conditionally-present control bar), whereas settings on the desktop app were under File > Settings. <br /><br />So the single IA was implemented for each interface individually still, even at the design level. From a write-once POV, there were absolutely common APIs, and a lot of pseudocode that was shared. The requirements were basically identical for each platform, to the point that the IA diagram included the common widgets that are used for each screen or state. But one guy built the iOS version. A team of three guys built the eReader. Another team built the website. Etc. One IxD, one IA, one VizD team for the whole project, but implementation was unique and custom per platform. And in the end each one looks the same, so is clearly the same brand and structure, but also works well, and works like the specific platform. <br /><br />And, this is example is also good because in the end the hardware was never launched. The product exists, but is only the website, app and mobile app. Which is fine, as there was no core device, with branches. The core design was the core /design/, and every branch was a branch. No refactoring to implement it this way. <br /><br /><br />And, I just used Mobile First as one example. I didn't want to get past "contrary" to "naysaying," but it's a good example of why I disapprove of a lot of these pithy phrases. They are overheard, learned from someone who didn't get it, and then get misused. I am seeing Mobile First interpreted as "whatever I want to build, that is mobile, first and only." So, I know teams making an iOS (or Android) app, ONLY. And they are so laser focused because this is their mantra, they don't just ignore fallback mobile web access (or: Usablenet is good enough!), they ignore the other OSs, and do a terrible job making the appstore (or marketplace) look like the same brand, or sell the app particularly well.<br /><br />But again, I see everything misused. If DFES gets any traction, it will keep me up at night how it's being used for evil.Steven Hooberhttps://www.blogger.com/profile/02906610345363264283noreply@blogger.com