David Robinson, Director of Production, StoryLoom
Pixelberry Studios released a request for proposals seeking a partner to create a proof of concept for the web-based platform. Their engineering manager recommended the company send the RFP to Atomic Object. Managing Partner Brittany Hunter wrote the winning response in the summer of 2020.
The Atomic team received a budget, an approaching deadline and what Pixelberry’s Director of Production for the product called an ambitious vision.
“Our parent company gave us one year and asked us if we could go big,” said David Robinson.
“We asked the Atomic team, ‘We want to go big—can you go on this journey with us?’ and they said, ‘Yeah, we’ll get on that ship with you!’ They didn’t flinch.”
Atomic designed the system architecture and wrote software and firmware for:
Six weeks into developing the proof of concept, the Atomic team impressed the Pixelberry client enough to take over design work on the project as well.
Soon, Atomic's developers, designers, and delivery leads were diving into advanced logic and helping bring Pixelberry's vision into reality.
Divide and Conquer for Team Management Success
As the year progressed, the team grew, gaining more trust and investment from Pixelberry. The proof of concept evolved into its own software brand: StoryLoom. Atomic organized the expansive work into three thrusts across Atomic’s Grand Rapids and Chicago-based teams:
- One team inherited the original concept: Creator Studio, where users write and design original stories users can play.
- Another team took on Character Canvas—a part of the app that let users design the characters that would star in their stories.
- The last team tackled Player Experience—building out the marketplace for content creators and the interactive community where users could discuss the stories created.
These teams complemented Pixelberry's internal developers, who developed the game experience itself. With so much work happening in parallel, project management took on great importance.
Delivery Lead Tammy Pearson helped keep Atomic’s and Pixelberry’s stakeholders aligned, informed, and on task.
“We’re very careful about respecting their time and the communication channels we use,” she said.
“Our choices around communication with the client have proven to Pixelberry that we’re good stewards of their budget and that we understand what we’re here to do.”
Robinson from Pixelberry said this investment in communication paid off.
“Within 6 months, we started recording the meetings Tammy would lead and share them across all divisions,” he said. “That was the benchmark for internal competency and customer service.”
Speedy Development through Micro-Frontends
To balance building different parts of the app at once, Atomic architected the app with parallel work streams in mind.
“We divided what could have been one big app into composable sub-apps that each team could tackle,” said Software Consultant & Developer John Ruble.
“That led us to some cutting edge micro-frontend technology, that looks like a single app made of different modules or sub-apps.”
The micro-frontends allowed for three different teams with their own codebases. This enabled different teams in different cities to work on the same product at once without any toe-stepping. By dividing and conquering the features, the three teams made up of more than 20 makers moved through the work at a faster clip to meet the client’s deadline.
When Pixelberry takes ownership of the entire product development, they will inherit the same architecture, which will allow the company to scale more easily.
In addition to helping them scale, Robinson said the development structure helped build a better culture of development internally at Pixelberry.
“Atomic did as much to teach them how to manage the project as I did, because they could see an example of how a producer worked, how they communicate, and what’s an expectation of performance,” he said.
“No one ever goes to development meetings unless you’re forced to, but when there’s a queue to get in and people are mad they didn’t get invited, that’s how development should be.”
Creative Constraints with a Design Library
The designers on the project needed to ensure that all the development and team management work resulted in a single, seamless experience for StoryLoom users.
In response, four of Atomic’s designers created a Design System for the product. The system unified design components like buttons or modals—elements that would be re-used throughout all the micro-frontends—into a library.
“As designers, we limit ourselves as much as possible to those pieces and then choose to build something else only if it's totally required,” said designer Kyle Harris. “We want everything to feel cohesive and as immersive of an experience as possible.”
“It was delivered on time, on budget, to expectation, live—not three or four milestones late with people leaving and the platform half-baked and full of bugs.”
The team’s careful project management, client communication, cutting-edge architecture, and cohesive design strategy helped the team ship the product on time and on budget.
Reflecting back on the multi-year, high-profile project, Robinson said Atomic helped his company arrive at a special moment in time.
“We'd never done anything this big. Ever,” he said. “We’re live across all the major pillars Atomic said they would deliver on. It was delivered on time, on budget, to expectation, live. Not three or four milestones late with people leaving and the platform half-baked and full of bugs.”
StoryLoom began open-beta in December 2022. A global launch is scheduled for the spring of 2023.
“Our future is pretty bright,” said Robinson. “We’ve been given a rare opportunity to find success by chasing opportunities Starship Enterprise-style: going where people aren’t—pushing boundaries.”