Skip to content

Instantly share code, notes, and snippets.

@fedecarg

fedecarg/commerce_prototype.md

Last active May 13, 2019 14:27
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save fedecarg/a46accab89a9378f2cbc778254061fc7 to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save fedecarg/a46accab89a9378f2cbc778254061fc7 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
commerce_prototype.md

Commerce Prototype - Project Overview

  • The goal of the project is to build an optimised version of the Commerce Journey to improve the user experience and maximise conversion. Why? Because in the last 4 months, less than 6% of all visits to the pass pages resulted in a sale.

  • We will create a fully working interactive prototype of the desired Commerce Journey using mocked data on a production environment with production ready code.

  • We will use extensive usability research, purchase funnel and commercial requirements to build the prototype.

  • The prototype will consist of a single responsive web application alongside multiple variants.

  • The web application will be used to test the usability of the UI and identify SDK requirements.

  • Multiple configuration files will be used to create multiple variations of the application. Each config file will define a user journey, and each user journey will consists of a set of use cases (see 2018-04-17 Use Cases v1.0).

  • Each user journey will be initialised by clicking on "Sign In" and entering a pre-defined email address. The experience for existing customers is out of scope for this prototype development.

  • The prototype development will not include architectural assessment of BAM or any other platforms.

  • The development of the prototype will consist of 2 phases:

    • Phase 1: delivery of a fully working web application with dummy data and limited number of territories and languauges. It will support multiple user journeys and cover all the use cases. Content management and translation systems are out of scope for this phase.

    • Phase 2: it will include architectural assessment of other platforms, including BAM and Sonic. Considerations to be reviewed throughout phase 2 are: Payment provider capabilities, content management system, SDK capabilities, best practice for Commerce environments.

Next steps

Below are some of the steps we need to follow in order to proceed with Phase 1, arranged into different tasks (although the order may vary):

  1. Review product requirements.
  2. Review UX designs.
  3. Define UI elements, components and screens.
  4. Write user stories and acceptance criteria.
  5. Create GitHub repo.
  6. Create Express/React app with no build configuration.
  7. Create test plan.
  8. Install testing tools and libraries.
  9. Setup test environment.
  10. Create build job in CircleCI.
  11. Setup a file based REST API mock server.
  12. Define a data structure for each API.
  13. Create a config setting for each use case.
  14. Create a config file for each user journey.
  15. Add base styles.
  16. Create static assets.
  17. Build UI.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment