About the client
The client runs a research-access platform made up of two applications that turn complex academic papers into simpler summaries and listening formats. It earns revenue through subscriptions and in-app purchases. The client wanted better performance, smoother subscription workflows and a responsive interface, with code that would stay maintainable as the product grew.
A growing product with no safety net
- Inefficient workflows. Subscription and in-app purchase workflows were inefficient
- Sign-in validation. The sign-in flow lacked validation
- Inconsistent UI. The UI was inconsistent and did not adapt well across devices
- Critical bugs. Several critical bugs affected both applications
- Test coverage. There was no automated test coverage, so every change risked regressions.
What FiftyFive built
A dedicated FiftyFive team delivered full-cycle development, bug resolution and QA automation: Subscriptions. Enhancements to subscription and in-app purchase flows, supported by R&D on RevenueCat. Authentication. Phone-number validation added to the sign-in flow. Interface. A responsive redesign using Tailwind CSS, including a redesigned login page, and keyboard shortcuts for audio navigation and playback speed. Notifications. Slack integration for automated system notifications. Stability. Bug fixes across multiple modules in both applications. Quality. RSpec test cases and coding standards enforced with RuboCop.
The platform runs on Ruby on Rails with PostgreSQL, Stimulus on the frontend and Sidekiq for background jobs, deployed on AWS and Heroku.
How the solution works
Application and background work
- Ruby on Rails serves both applications, with PostgreSQL as the database.
- Stimulus adds interactive behaviour to server-rendered pages, and Sidekiq processes background jobs outside the request cycle.
Quality controls
- RSpec test cases cover the code paths changed during the engagement, and RuboCop enforces consistent Ruby style, giving the client a baseline of automated checks it previously lacked.
Operations
- System events are posted automatically to Slack, so the team sees platform activity without checking logs by hand.
Technology stack
What the solution enabled
Business transformation
Delivered to production
Applications with bug fixes
Core technologies in the stack
Purchase workflows
Improved subscription and in-app purchase workflows.
Phone-number validation
In the sign-in flow.
A responsive Tailwind CSS interface
And redesigned login page.
An RSpec test suite
And RuboCop coding standards.
FiftyFive Technologies improved the research-access platform of an education-technology company that makes academic research easier to consume for students, researchers and professionals. The platform's two applications suffered from awkward subscription and in-app purchase flows, weak sign-in validation, poor responsiveness, critical bugs and no automated tests. In four months, a dedicated team on Ruby on Rails, PostgreSQL, Stimulus and Sidekiq improved subscription workflows, added phone-number validation, rebuilt the UI responsively with Tailwind CSS, fixed bugs across modules, added Slack notifications and introduced RSpec tests with RuboCop standards.
Technical questions
What do Stimulus and Sidekiq do?
Stimulus adds interactive behaviour to server-rendered pages, and Sidekiq processes background jobs outside the request cycle.
What do RSpec and RuboCop cover?
RSpec test cases cover the code paths changed during the engagement, and RuboCop enforces consistent Ruby style, giving the client a baseline of automated checks it previously lacked.