Scholastic hired Atomic to join Literacy Pro’s mission to inspire a love of reading. That mission was our spark: it helped us make technical decisions that everyone on the team could understand. At every point, the whole team knew to focus on reading in the user experience, reduce the steps to get to a book, use data to support book choices, implement technology that fit easily in the classroom, and present the books front and center.
In our engineering plan, we chose tools that would support Scholastic's mission in the long term:
React was the choice as a UI framework because it was proven reliable, capable of all the planned user experience for students across the device matrix, and was a good fit for the in-house tech team.
NextJS was our choice to extend the React framework for full-stack development.
We chose Cypress as our tool for QA automation, because it integrates right into a full-stack TypeScript implementation, providing clear views into the testing for the Atomic and Scholastic engineering team.
All our choices were carefully reviewed with the whole team to make sure they met the organization's strategic goals, matched the technical direction, and could achieve the outcomes for the mission: let's get kids into books!
It was a great example of how Atomic engineering works together with the whole product team:
We bring engineering, content, design, and business people together as early as possible.
We provide different options for engineering to meet the product goals, so partners can manage their budget, deadlines, user experience, and communications.
By integrating into a long-term development plan, we save costs with a lower total cost of development.
The result is a sustainable product that can operate for years.
Comments