Development

This slideshow requires JavaScript.

After I completed the sketches and working out the interactions I then went to Adobe XD to mark out the layout I wanted for the interface uses minimal images and designs so I could re-organise or make adjustments when needed.

This slideshow requires JavaScript.

After I had settled on the format I started inserting images that I would use and fleshing out some the information text and descriptions.

Web 1920 – 3Reference

 

I then went to develop the look testing how I wanted the “message boxes” to look like and the surrounding layout and design moving it away from being a wire-frame into a designed and stylised interface.

 

This slideshow requires JavaScript.

After finalising the aesthetic I could then apply the style to the other slides in the wire-frame and inserting more context and make it seem like a real tangible interface for someone to go through. Furthermore, I could then work on the smaller aesthetic details or interactions such as I trailed with different areas for a “further details” button and how I wanted that to look like. Ultimately I shifted it to a “glossary” button to serve as a quick look-up for those uses the interface.

Web 1920 – DETAILS HOMEWeb 1920 – OPEN GLOSSARY

Shown below is one of the process variants of how the user maneuvers to the screen shown above.

This slideshow requires JavaScript.

Full Adobe XD “layout” of all the slides.

DEVELOPMENT2.JPG

Start of XD Prototype.

If I could develop this further I would want to move this out of XD onto its own website with it further developed with animations and sound.

Project Crit

Project Critique, like in previous presentations, I talk through my inspiration for the concept and how it formed and developed.

I discussed my initial processes and prototypes and the feedback I received, and how I used that to improve upon and further develop my currency.

I discussed how I used system diagrams to help me present how my currency would work and identify what areas I needed to work on to make it possible to be a fully functional currency. I then went onto to present my designs.

What I wanted to produce was an introductory page walking through how the currency would work and some of the systems it would have in place, like the management of resources, tracking of inventory and the main central exchange system.

Some feedback that I got was that the system was well thought out, seemed like a real and tangible system that could work backed by many considerations behind it. It was felt that the interface didn’t reach up to the same level and needed some changes and improvements. Additionally, it was suggested that I change the Logo and ensure it is in keeping with the use case and help form the overall design aesthetic.

My final task to do really is work on the branding and appearance with improvements to the interface.

Other Interfaces

Some other interfaces I considered, were the interface for a scanner. I looked at some examples of the interfaces used in RFID scanners and I noticed that the actual interfaces used, were frequently a mobile phone with a scanner application, that was then connected to a physical scanning device.

The Features it would need is verification so some kind of signal that it’s been scanned and a check to see if it’s correct. Moreover, other features included would be to check whats been scanned.

 

Scanner.PNG
RFID Scanner Interface, By Author

 

Project Development Presentation

I presented my initial concept to the group walking through my currency idea and how it works. I gave my idea in the context of Hospitals exchanging and/or sharing resources. However, one point that was brought up that hospitals already have a system in place for using their own resources. Transferring of patients between hospitals when specialists or special equipment is needed to keep resources in use.

 

FirstPrototype
Coloured Prototype, By Author

 

Additional feedback was that the colour scheme looked clinical and very plain. However, in the context of hospitals, I felt this was probably appropriate – clean, easy to understand and use and only displaying information that is needed, highlighting important features and information when required.

 

Styleguide Design

We researched different style guides and how other companies produce their own. Some examples where Channel 4’s and IBM’s style guides.

https://www.ibm.com/design/language/experience

http://www.channel4.com/about_c4/styleguide/downloads/C4StyleGuide1.1.pdf

IBM discusses the language and approach to design, as well as some design methods and then proceeds to their look and style. Whereas Channel 4 solely discusses its design language and how to present work when designing for them like e.g. Logo positioning and sizing what fonts to use with fallback options etc.

My first style guide was just to see how I could do the layout and give examples that I could then use into my own work. Colour scheme and specific details I would change it later when I apply it to my designs, which I could use to reference and put directly into.

 

StyleGuide1
Version 1 of Styleguide, By Author

 

Technical System Diagram

Following the previous diagram, this is the more in-depth version of the system diagram which follows how requests work and then the sending of the resources. Further, how the role of the currency works.

The Diagrams, walk through all the processes and each step required to perform an action in more detail rather than my simple explanation in the previous post.

This slideshow requires JavaScript.

 

System Diagram

First Diagram of how the system would work this was incorporating the currency as a subscription-based service. Through showing proof of usage of resources, you would be given time to use the service. The model would work like before where you exchange giving use of resources to other companies for currency.

Service Model 1
System Diagram incorporating a subscription method, By Author

 

I revised it to make a simple version of how the system works with a more technical diagram to follow of how the transition works in depth.

Simplified System Diagram
Simplified system diagram showing the exchange and how it works, By Author

 

Like the first, it shows how loosely how the diagram works between two companies and where the system fits into a corporation. Acting as a secondary currency for purely resource management and distribution.

Prototyping

Initial Prototype

IMG_0360
Sketch Prototype by Author

My first initial prototype was just testing how I’d create an interface and what sections and parts would be required.

Some interfaces I thought might require designing;

  • Company Registration + Account Management
  • Company ‘Wallet’ / Management
  • Exchange Interface
  • Online Market Place
  • Asset Inventory System (tracking the quantity and location of physical and/or moveable assets (like ambulances, mobile medical equipment, wheelchairs)
  • Stock Control (tracking the number of consumable products like bandages and medicines)
  • Booking System (tracking the availability of fixed resources such as Xray Machines, operating theatres, specialist staff etc.)
  • Marketplace/Pricelist – agreed “Service Coin” value for specific assets (e.g. buy some bandages costs you 1 Service Coin. Lending out your x-ray machine and operator for 1 hour earns you 100 Service Coins)

The main interface needed to tackle is the ‘Exchange Interface’

Overall Initial Interface

Some major criticism was that people didn’t understand what was going on and that it was confusing. I think I sectioned each area to what was needed, but accept that it was executed poorly.

Listings of Companies, what goods they have on offer and what they require the use of this would then branch into two sections giving separate listings of goods and other company needs. The ‘Goods’ branch would be a list of items a company has, and enable you to see the description of the item then write a form requesting use of their resources. For ‘Service Needs’ you’d see the reverse what items a company wants to use from your company followed be description and time and date of use. Furthermore, I made two different views on requests, list of request your company has made to other companies and requests companies have made to you.

Initial Super Awful Prototype
First Prototype by Author