Bring your own React components!
This header will be substituted in nwww code
Rapidly iterating on the logged-in app experience without developers
Problem: Rapidly deploy in-app content changes without developers.
1/20
Time to ship new content
In previous workflows, even small content changes would take 1 hour minimum to deploy. With Plasmic-generated content, that number goes down to minutes.
100%
Development cost savings
Plasmic enables non-engineering teams, such as design and marketing, to own surfaces of the web app in production. Giving these teams the autonomy to deploy gives them direct control, while freeing up valuable engineering resources to work on higher-value product features.
XXX
Improved referral conversions
By implementing their new referral page in Plasmic, experimental changes to the referral program can be deployed in minutes. Since implementing this experiment, PlayVS has been breaking referral records every week since.
Problem
PlayVS supports esports leagues around the country at the high school and collegiate level. Each season, they need to publish a lot of new design-rich content to their app. However, the typical engineering workflow of gathering requirements, engineering estimation, development, testing, code review, and release, meant that content updates were few and far between. Users frequently pointed to the stale content still being served by the app.
PlayVS needed a better solution for visual content like banners, referral pages, and featured tiles that would be shared across the application and marketing page.
Prior to Plasmic, PlayVS faced the following challenges:
•
Only a fixed set of CMS layout templates and building blocks are supported. New features often call for very new and different user experiences.
•
All the building blocks are implemented entirely in code by software engineers.
•
All content changes, no matter how small, were bottlenecked by engineering capacity.
Goals
To accelerate experimentation, the team is focusing on the following key areas:
1
Democratize implementation: Enable non-developers, such as designers and marketers, to implement production components for beautiful responsive content layouts.
2
Lower the friction to update content in production: Enable the marketing team to directly deploy updates without going through manual engineering processes.
3
Incremental adoption: Work within the existing tech stack and allow teammates to start with limited surfaces, without requiring a full re-implementation or port of existing work.
4
A scalable approach: Allow many teams to edit in parallel without conflicting with each other, scaling with business needs.
The Plasmic Approach
Jonathan Bowell, the lead engineer manager charged with evaluating many different CMS options, performed a deep dive comparison of Plasmic to other tools. The solution needed to be easy to use for non-developers, flexible enough to implement rich visual content, integrate easily with their existing code base, and perform well under performance stress tests. They also performed a thorough code audit of the libraries that will be added to production dependencies. Plasmic turned out to be the only solution that met all of their requirements.
With Plasmic, they found a solution that helps with:
Flexible WYSIWYG page and component builder: Plasmic Studio was the only product that provided the necessary flexibility and freedom to implement designs as envisioned, while keeping it easy for anyone to visually create new pages and content. Plasmic ships to production with high design fidelity and speed.
Blazingly fast, production-ready: PlayVS performed speed audits and a line-by-line code audit of Plasmic components. Plasmic had to be ready to be used on their most trafficked pages.
Seamless integration: Plasmic flexibly integrates into any codebase, making it easy to leverage existing pipelines and workflows. Hand-written and Plasmic-generated components are indistinguishable to the user.
Team empowerment: Within a 30-minute training demo, non-developers were up and running, implementing their own content in Plasmic and deploying without a developer in the critical path. Today, the marketing team owns surfaces in production that normally would have been owned by engineering.
Use Cases
Plasmic content has been deployed on the application dashboard, the team's most heavily-trafficked property. Plasmic makes it easy for anyone on the team to create and update rich experiences, giving teams outside of engineering the ability to ship high-impact content, like those used for promotions. By designing news content in Plasmic, these highlights can be easily updated as often as needed.
This is just the beginning for Plasmic at PlayVS. The team also redesigned their in-app referral page in Plasmic, allowing the team to rapidly experiment with different incentive programs.
Everyone, from designers to marketers to developers, is empowered to create a new experience. Plasmic also plugs into existing deployment and QA processes, so you can move fast with the guardrails you need. This increased velocity will help make PlayVS even more agile in this dynamic market.
About PlayVS
2018
Founded
Los Angeles, CA
Headquarters
100+
Employees (as of Sept 2021)
PlayVS is building the infrastructure and official platform for high school and collegiate esports, working with game publishers and high school governing bodies to build and operate sanctioned leagues across the country.
This market leader chooses Plasmic to accelerate their go-to-market.
Want to accelerate your team's velocity like PlayVS?
Try Plasmic for free
The Footer component will be substituted in nwww code