Catherine Hicks
User Experience and Product Design Professional

Hewlett Packard
(HP)

Hewlett Packard Enterprise is an industry leading technology company that enables customers to go further, faster. With the industry's most comprehensive portfolio, spanning the cloud to the data center to workplace applications, their technology and services help customers around the world make IT more efficient, more productive and more secure.

Role & Project Summary

HP Access Catalog: App Payment

As part of the HP app store concept, this explores how we would take payment for the apps

While building the HP Access Catalog platform, we realized we needed a way to manage payment and billing of app deployment to specific teams seamlessly within the app

Platform managers would be able to manage proper billing to the appropriate teams within the platform

Users will not have to ask for purchasing permission to buy

Administrators can streamline the software approval process

Project Constraints

  1. Users should have a seamless process in "purchasing" apps and the apps should automatically be billed to the appropriate place in the background
  2. We needed to figure out how payments were going to be processed. In the traditional app stores (iOS/Android) an individual user paid for their apps via credit card or other means. Was this the way we wanted to go with this enterprise platform?

Wireframes

HP Access Catalog: App Payment

Initial Screen


HP Access Catalog: App Payment

Individual Color Detail


HP Access Catalog: App Payment

Edit Palette

  • Edit Palette

HP Access Catalog: App Payment

Saved Palette


HP Access Catalog: App Payment

Full Palette


HP Access Catalog: App Payment

Email Palette 



HP Access Catalog: App Payment

Emailed Palette Email Layout


HP Access Catalog: App Payment

Wireframes

Example

At the beginning of my design process I created wireframes for testing purposes.

Guiding Questions

  • Why was it useful to do this?
  • What kind of wireframes did you make?
  • Low fidelity or high fidelity?
  • What tool did you use for this?
  • Did you use them for testing?
  • How many iterations did you have?

HP Access Catalog: App Payment

Wireframes

Example

At the beginning of my design process I created wireframes for testing purposes.

Guiding Questions

  • Why was it useful to do this?
  • What kind of wireframes did you make?
  • Low fidelity or high fidelity?
  • What tool did you use for this?
  • Did you use them for testing?
  • How many iterations did you have?

Summary

  • Payment, as I designed it, was not what was finally implemented. Right before I left we went from the "individual payment" to a more "accounting based payment" where payments were assigned to teams instead of having to be paid individually
  • We believe teams need to be able to keep track of applications for budgeting purposes
  • We believe administrators need a way to manage how payments are collected and to set the payments on the platform
  • Payment was originally thought to be handled in a traditional e-commerce style way, which is what the wireframes show. Upon further reflection right before I left, it became more of an accounting tool since this was an enterprise level product and not a consumer facing product. However I did not design that
  • While I built a fully formed payment system based on an already existing payment backend infrastructure used within the company for other things, right before I left the idea that since this was enterprise platform, payment structure should become more of an accounting type system where it was handled internally and assigned to the person's team instead of the true payment flow. I did not work on that.