Time To Make A Synopsis Of Design

After over three weeks of reading design books, exploring applications and immersing myself in a new technology environment, it is time I construct a usable post to help with the designing of Crohn'sPromise. Summarizing what I have found to be most valuable will create a checklist of standards to maintain as the designing process begins. In essence, this post is giving me an opportunity to see how much I have learned over the past few weeks.

Design in General

I think that a lot of the process of design is going to rely on my imagination. The metaphors I learned in design: a screenshot is just like a billboard and an application is like a store, will prove to be incredibly valuable. Though I have no experience when it comes to creating billboards or organizing stores... this mindset will help me approach each design principle that comes up.

Like a billboard designer, I should always be asking :

1. Is it obvious to the user what is on this page and what purpose the page serves?
2. Does the user know how to proceed to their next step from this page?

For each  page, the answer to these questions needs to be "Yes." If this is not the case, then the page is not complete.

As if the design of an app = the design of a store I will need to keep in mind that a user is just a customer who is searching for a product in the store's many isles.
     1. If they get frustrated by their search they will close the app and use their time differently
     2. Creating a sense of "location" makes a search more concrete (requires intuitive layout)
     2. Tools and conventions exist to help a user with their search
                a. Does the page have a Title?
                b. Is there use of Font Sizes, Colors and additional METHODS to get the point across?
                c. Are links clearly visible and lead to a clear location?
                d. Is everything that is necessary on the page/is everything on the page necessary? (don't overcrowd)
                e. Is anything on the page going against conventions? Can something on the page use everyday conventions?

The Game of Designing APPS

I have broken down app design into 6 sections and will list a few main bullet points for each one.
    The Home Screen

• Is there a way to get to all of the most important functions from the Home Screen?
• so make it complete-all options present and none are ambiguous
  
• but is important to not succumb to overcrowding
  
• Is there easy access back to Home Screen?
  
• Gives the feeling of "location"
  
• Using a tool bar at the bottom is one way to accomplish this (there are others-be creative!)

Layout and Organization

• Is the progression from one screen to the next intuitive?
• Answer: If I click this button, what do I expect to see on the next screen?
  
• Does everything fit into the different category titles?
• Don't compile unrelated features under ambiguous titles to save space on the previous screen shot.
  
• Can the user get an idea of the "big picture" of the app?

• Can they see more than just one input at a time and gain understanding of what the they are accomplishing
• Like the Daily Log and graphs seen on the apps already looked at

• Can the app be made in a more dynamic fashion?
  

• Options appear as they become applicable making original screen simplistic.

Inputting Information

• To be sure the page requires no effort from the user, answer these questions:
  

• Can you use a sliding scale (for #'s or between definitions like myIBD)?
• Can you create a scroll menu for inserting text?
  
• Can you provide a list of available options for typing in a response?
• this only helps if the list is concise (avoid USDA)
  
• How can you use colors here to make inputs more intuitive?
  
• Is there a need for an input option of "other?"

• To include options that serve little purpose to the majority of users
• NOT because your provided list is incomplete!
• Did you include a way for users to add personal notes?
  
• Users will be more willing to share information some if which can be crucial
• Good design: make text box project out to make it obvious

Use of Icons

• Can the instructions be explained by an icon?
  
• nobody will read text instructions.
• Can any text be replaced by a picture?

• Is the icon ambiguous?
  
• Can one or two words be added to enhance the meaning of the icon?

Presenting Data

• Presenting Data
• Can relationships be represented in a line graph?
  
• Can words be replaced by colored scales and numbers?
• Is their data present that is more distracting than helpful and should be removed?

Always be thinking

• Can this be made fun?
• Can this be made social, can there be a network aspect?
  
• Aim to create a more loyal and involved user base that will lead to the success of the app.

The points and questions above will act almost as a checklist. The result of following what is written will be a strong and friendly design for Crohn'sPromise. It was fun creating this list; reading my pasts posts and seeing the lessons and reflections that I have had thus far!

A last lesson of value to remember is that I must always be thinking about the user. As I looked at other apps, the stand out features occurred when the designers thought outside the box, like GI monitor putting a "Questions for Doc" feature on their home screen or GI Buddy including information not directly related to the apps function but still beneficial. Putting myself in a users shoes, I will always try to design with the user experience in mind. I hope the end product will be a success!