Mystrokapp's Blog

Campus Compass User Persona

mystrokapp — Thu, 09 Jun 2011 19:55:28 +0000

iphone App Skecthes

mystrokapp — Thu, 02 Jun 2011 20:23:41 +0000

View this document on Scribd

Application Definition Statement

mystrokapp — Thu, 02 Jun 2011 03:17:02 +0000

Campus Compass IPhone App
Application Definition Statement

1. Features

Classroom locator and status by way of number and section
Instructor’s office location and status
Map with locations (bathrooms, security, store cafeterias, financial aid, etc.
Alternate campus locator

2. Users

Primary
College students
Male and female

Secondary
Faculty
Visiting family

Weekly Reading #8

mystrokapp — Thu, 02 Jun 2011 03:11:00 +0000

So, this week is the last week o reading assignments. Have to say, I’m pretty excited about it not having homework of any kind in two weeks. Time for some much needed R & R. Alright. Back to the subject at hand. This weeks reading was all about developing for the iphone family and what that entails. And the name of the game is, simplicity. First of all you have to keep in mind that a smart phone screen, in this case the iphone, is much smaller than a computer monitor, so your design must reflect that. Also, the iphone’s interface is not one that you point and click on. It is a touch screen and one must design accordingly. So, while you have to make everything smaller, you also have to make it big enough to touch. The simpler and recognizable the design, the better.

One must also keep in mind that an app should perform some sort of function. It can’t be there to just sell a product, it has to do something. You can weasel some brand identity into the app but if it doesn’t provide a useful service it will be completely looked over.

Rock and roll, kids. Have a good break.

Links fo yo momma:

http://www.time.com/time/specials/packages/0,28757,2044480,00.html

http://iphoneappcafe.com/

http://www.smashingmagazine.com/2009/08/11/how-to-create-your-first-iphone-application/

eCommerse Final

mystrokapp — Thu, 26 May 2011 19:38:52 +0000

View this document on Scribd

Weekly Reading #7

mystrokapp — Wed, 25 May 2011 06:17:26 +0000

This weeks chapter was one of those “funny because it’s true” type scenarios. The powers that be are usually only concerned with the bottom line. If they feel that a site isn’t grabbing the customers attention, they want to make it MORE flashy, MORE animated, MORE colorful. Mind you, they do this with the best intentions but, as the author pointed, it is rare that a person is visiting a site for a company and wants to be wowed by the glitz and glam (unless, of course you’re selling glitz and glam). Most people are there to perform a specific task, whether it be making a purchase, finding information or seeking a service. If the way to their end goal is blocked by distractions then, more often then not, the user will find a site that provides the simplest, most enjoyable process to get there.

Once again, the book shows its age when discussing slow load times for large images. We all (well, most of us) have some sort of high speed internet connection so some of these problems no longer exist. That isn’t to say that just because you can throw a bunch more content on the screen that you should. Designers should always be aware of keeping their audience away from their end goal with bells and whistles.

Peep the links, son! (aka what not to do)

http://dokimos.org/index.aspx

http://yvettesbridalformal.com/

http://www.hosanna1.com/

Ecommerce First Look

mystrokapp — Thu, 19 May 2011 20:16:35 +0000

View this document on Scribd

Sketches Ecommerce

mystrokapp — Wed, 18 May 2011 23:56:26 +0000

Wireframes Ecommerce

mystrokapp — Wed, 18 May 2011 23:49:52 +0000

Weekly Reading #6

mystrokapp — Wed, 18 May 2011 22:23:03 +0000

Chapter 10 covered usability. I hate to say it, but its getting to be a lot of review at this point. And what isn’t review is out dated. Maybe it’s just getting late in the quarter and I’m getting burned out on the text. So, the stuff in chapter 10 is good information but some things seem a little odd to me. Like “make sure your user can navigate your site without a mouse. Some people can’t use them.” Really? Who can’t use a mouse? Who designs a site that you can navigate with the arrow keys with the exception of scrolling content? Was this common practice ten years ago?

Chapter 11 had some interesting info, if not entirely outdated. Websites are supposed to be accessible to blind people? I had no idea. Not once in the 7 quarters I’ve been attending AIS have I heard anything about this practice. Id this something that is still in effect? Are there apps that take the place of having to include code in the html to accomplish this? It said that I had been living under a rock if I had not heard this but I’m totally clueless. I think that for my links this week I’m going to try and get to the bottom of this…

Links, yo:

http://www.section508.gov/

http://www.jimthatcher.com/webcourse1.htm

http://www.webpagefx.com/508-Compliance-Web-Site-Design-Services.php