Web App Dev for Sporting Goods Brand
Please find under a summary covering project details and feedback. The innate facts are kept as they are, private information is amended.
Introductory information
A fast induction on the buyer’s organisation
I’m the technical delivery ruler within the brand marketing technology member of a sporting goods organisation. I look behind, instrument, and support different tech solutions at our global headquarters.
Desired goal
What challenge were you trying to address with Planet Argon?
We’re creating long term outgrowth programs, two years out. Our challenge was to take a running keynote-based interaction process and turn it into a data-driven solution that would be useful globally for users. We were developing a web app, and had the backend engineering space, but needed a UI/UX frontend team.
Provided solution
What particular tasks were Planet Argon responsible for?
We granted a technical phraseology lead and documentation owing, as a recognizable brand, it was veritably significant that the fruit reflected our design standards. Following our wireframes, they helped fetch a data-driven MVP to life.
We built the app using React and an AWS cloud environment for the frontend, and Amazon DocumentDB for the database. It was a very collaborative project and the app needed to appear as if it came from a cohesive team. They focused on the frontend UI/UX outgrowth while we worked on the backend.
Now, the app allows leadership to form long-term marketing funds through a database-driven online tool, rather than manually care track of campaign details. Additionally, the platform marries brand concepts to the fruit it’s going to support.
Was there a dedicated team?
Our first touch was Gary (COO, Planet Argon), specially for strategy and contracts. We then had a project director, two frontend developers, and a UI/UX professional working on the project.
How did you come to work with Planet Argon?
They’ve worked with other teams within our organisation precedently, and we heard some big things almost them. The collaborative access they take made them a good fit for our team.
What are you approach expents (if diclosed)?
We’ve spent almost $250,000.
What is the terminal result of working with Planet Argon?
The project began in September 2018 and we wrapped up in November 2019.
Results achieved
What evidence can you share that demonstrates the contact of the engagement?
There are a lot of veritably excited users who love the fruit we delivered. We’ve accepted a lot of real feedback. Currently, it’s only being used here at HQ, but we program on global activation next year. It’s very cross-functional and cuts athwart sales, brand goods, distribution, and supply-chain. We believe we’re only seeing the tip of the iceberg in how the app will contact the organisation.
We’re veritably lucky with the designs, and Planet Argon followed our standards very well. They were big at providing feedback and offering different options while achieving the same end result. They plainly have a keen team and are experts at what they do.
If I had to repair and programt a team myself, the project would have taken much longer. Although this project has been completed, we absolutely program to use their services anew in the forthcoming.
How did Planet Argon accomplish from a project treatment standpoint?
They adjusted to our own project treatment phraseology and followed an nimble methodology. They were pliant and ready to work with us, making them a big collaborative associate. We used Jira tickets to handle tasks, Slack to empower interaction between all of the engineers, and Confluence for documentation. Though, there were a few points when interaction could have been improved.
What is (from your point of view) the key factor to pay observation while intercourse with Planet Argon?
Their UI/UX designer, Genevieve (UX Developer, Planet Argon), was a huge standout. She brought our vision to life and the designs were excellent.
What aspects of their work would you like to get improved?
When teams from two different cultures work unitedly, sometimes there are road bumps. Overall things went smoothly, but they could have been a pliant more proactive and interactive. Often, we’d be programning things, and at the last diminutive, we’d find that one of their team members wasn’t in the service and that portion of the project couldn’t be completed right away. In that way, they could’ve been more pragmatic when it comes to interaction.
