ROWERR CASE STUDY / IPSPECIALIST
IPSpecialist: Custom LMS, eCommerce Website & Mobile App Development
From a WooCommerce learning store to one connected web-and-mobile education platform.
Custom LMS, eCommerce website & mobile app development helped IPSpecialist move from a WordPress and WooCommerce learning store to a connected web-and-mobile platform. Rowerr built the original commerce, courses, memberships and booking workflows, then began a custom rebuild in 2025 after discovery in 2023 and planning in 2024. The new React web and React Native mobile applications share Node.js/Express services and one Supabase PostgreSQL data source, with development continuing in 2026.
Key Challenges
- Growing plugin dependencies.
- Performance and custom workflow limits.
- Purchases linked to learning access.
- Complex staff and learner roles.
- Regional payments and mobile usage.
- Consistent records across devices.
Connected Solutions
- Custom e-store, LMS and memberships.
- Bookings, events and editorial tools.
- Role-based dashboards and administration.
- Community, messaging and notifications.
- Web and mobile on shared data.
Core Stack
- Earlier: WordPress and WooCommerce.
- LearnDash · MemberPress · Amelia.
- Web: React + TypeScript.
- Mobile: React Native + TypeScript.
- Node.js · Express · Supabase PostgreSQL.
Our Process
- Map requirements and existing workflows.
- Plan modules, roles and shared records.
- Build connected business functionality.
- Develop web and mobile interfaces.
- Deploy, add CDN and continue expanding.
In this case study
The Project Timeline: Discovery Before Development
WordPress, WooCommerce, LearnDash, MemberPress, Amelia and Elementor established the learning store. Its initial launch year is not assigned here.
Mapped products, users, learning, memberships, bookings, content, permissions and future mobile needs.
Defined functional modules and the relationships between commerce, learning and operational data.
Began replacing the plugin-centred architecture with purpose-built web application modules.
Developed the React web experience, React Native mobile application and shared backend/data architecture.
Continued platform development, server infrastructure work and CDN implementation as requirements evolved.
PHASE 1 / THE ORIGINAL PLATFORM
WooCommerce Development: Bringing Commerce and Learning Together
IPSpecialist needed a practical platform for selling learning products while delivering courses and managing its audience. WordPress supplied content management, and WooCommerce became the commerce engine for courses, digital resources and other products.
LearnDash supported learning delivery, MemberPress handled memberships and user requirements, Amelia supported events and bookings, and Elementor with related add-ons provided page design, galleries and presentation.
This was a useful starting architecture, not a mistake to erase from the story. It combined established tools so the business could operate its learning and sales workflows in a familiar environment.
As requirements expanded, performance, dependencies and highly customised functionality became harder to manage within that combination. The next decision was about the complete operating model, not a blanket conclusion that WooCommerce cannot scale.
| Original tool | Responsibility |
|---|---|
| WordPress | Publishing and website management |
| WooCommerce | Products, purchases and commerce workflows |
| LearnDash | Courses and learning delivery |
| MemberPress | Memberships and user requirements |
| Amelia | Events, appointments and bookings |
| Elementor and add-ons | Page design, galleries and presentation |
A growing store does not automatically need a rebuild.
Start with the workflow causing the problem. We can assess WooCommerce performance, checkout, access rules and integrations before recommending a larger change.
Discuss Your WooCommerce Requirements →Explore WooCommerce Development ServicesPHASE 2 / THE CUSTOM APPLICATION
WordPress Migration: Rebuilding the Business Functions, Not Just the Pages
Discovery began in 2023 and architecture planning continued in 2024. Development of the replacement platform began in 2025. This sequence gave the team a map of the business before changing the technology.
Rowerr developed custom modules for the e-store, LMS, memberships, events and bookings, administration, content publishing, profiles and portfolios, community, messaging and notifications. These functions were built around IPSpecialist's requirements rather than assembled as another set of WordPress plugins.
The web application uses React and TypeScript; Node.js and Express provide backend services. The React Native and TypeScript mobile application offers a dashboard-oriented interface to relevant platform workflows. Both use the same underlying Supabase PostgreSQL data source.
Commerce remains central: the purpose of the transformation is to connect what customers buy with the learning, access and ongoing interaction they need afterward.
Challenges and Solutions at a Glance
| Store-owner challenge | What Rowerr developed |
|---|---|
| Performance and plugin dependencies | Purpose-built modules, server configuration and CDN. |
| Purchases disconnected from access | Commerce, LMS, memberships and bookings in one platform. |
| Regional payment requirements | Paystack, PayFast and relevant local integrations. |
| Complex staff and learner roles | Role-based dashboards and permission-controlled workflows. |
| Mobile platform requirements | React Native application connected to the same business system. |
| Conflicting records across devices | One underlying Supabase PostgreSQL data source. |
Performance and plugin dependencies
The business challenge
As the WordPress platform grew, performance concerns and dependencies between specialist plugins made new requirements harder to accommodate. The problem was the combined workload and workflow complexity, not simply a plugin count.
Our solution
We rebuilt the major functions as purpose-built modules within a custom application. That gave the team direct control over the implementation rather than requiring each new workflow to fit another plugin's interface.
What this enables
The application was deployed to client-provided server infrastructure, followed by CDN configuration. This provides an architecture the team can tune and extend; it is not evidence of a particular load time or percentage speed gain.
Connecting purchases, courses, memberships and bookings
The business challenge
For a learning business, taking payment is only the beginning. The same customer may need course access, membership permissions, digital resources, a booking and a usable account dashboard.
Our solution
The custom e-store, LMS, memberships and events/booking systems were developed as connected modules. Purchase and access workflows could be organised around the same user and business records.
What this enables
The platform supports the journey beyond checkout, with learning, content, profiles and community functionality in the same product. Specific refund, expiry or renewal policies should be defined for each implementation rather than assumed.
Payment options that reflect the buyer's market
The business challenge
An international learning store needs payment choices aligned with the countries and customers it serves. One generic payment route may not suit every market.
Our solution
We incorporated Paystack, PayFast and additional regional payment integrations according to IPSpecialist's requirements, connecting the commerce experience with the wider platform.
What this enables
Provider availability, currency and billing capabilities remain configuration-dependent. The project demonstrates custom payment integration, not universal gateway compatibility or a measured reduction in failed payments.
Connect the sale to the service that follows it.
Course access, memberships, bookings and payment workflows should work as one customer journey. Tell us where your current store needs support.
Plan Your Commerce Workflow →Explore WooCommerce Development ServicesOperational roles without fragmented administration
The business challenge
IPSpecialist needed separate responsibilities for administrators, employees, instructors, students, editors and article writers. A generic customer-versus-manager split did not describe its organisation.
Our solution
We developed role-based administration, user dashboards and permission-controlled workflows across learning, commerce, content and community modules.
What this enables
Staff and learners can use interfaces appropriate to their responsibilities. Profiles, student portfolios, article publishing, messaging boards and notifications are platform functions rather than disconnected account systems.
A mobile application, not just a smaller webpage
The business challenge
The client wanted a full platform experience away from the desktop, including useful account management and communication for more than students alone.
Our solution
We built a React Native application with TypeScript as another interface to the learning and commerce platform. Relevant dashboards and workflows are available to students, instructors and administrators according to permissions.
What this enables
The mobile product shares business data with the web application rather than maintaining a separate learner database. Public app-store distribution, offline learning and identical feature availability on every screen are not asserted.
Custom LMS Development: One Backend, One Database, Two Applications
- Web: React + TypeScript.
- Mobile: React Native + TypeScript.
- Application services: Node.js + Express handle APIs, validation, authorisation and business logic.
- Data access: ORM-based application code.
- Shared records: Supabase PostgreSQL for the platform's core business data.
The frontends are interfaces to shared records, not independent databases. Browser and mobile access must pass through appropriately authorised interfaces; sharing data does not mean exposing unrestricted database credentials.
| Layer | Technology and role |
|---|---|
| Web frontend | React + TypeScript: customer and operational interfaces |
| Mobile frontend | React Native + TypeScript: role-based mobile application |
| Backend | Node.js + Express: APIs and business logic |
| Data layer | ORM-based access; exact library not specified |
| Database | Supabase PostgreSQL: common platform data |
| Payments | Paystack, PayFast and additional regional integrations |
| Infrastructure | Client-provided server, additional configuration and CDN |
This is a PostgreSQL-based application, not a MERN stack. The exact production ORM and alternative data-access methods are not presented as simultaneously implemented technologies.
Technical context: Supabase database documentation and React Native documentation describe the underlying technologies; the project history and delivered modules follow Rowerr's supplied account.
What the Platform Delivered
- A commerce foundation that evolved beyond the original WordPress store.
- Custom learning, membership, booking and operational modules.
- Purpose-specific roles, dashboards and administrative workflows.
- Community, messaging, notifications, content, profiles and portfolios.
- Web and mobile applications using the same PostgreSQL business records.
- Server deployment, CDN work and continuing development through 2026.
The documented outcome is a connected, adaptable application platform. No verified before-and-after revenue, conversion-rate or speed measurements are available for publication, so no numerical uplift is claimed.
For store owners, the lesson is to diagnose the requirement first. Improve WooCommerce when focused changes can solve the problem; consider a custom application when the wider business model genuinely needs it.
Related Rowerr work: Sustainability Education Academy, Couples Fight School and Too Ambitious.
Custom LMS, eCommerce and Mobile App Development FAQs
01What did Rowerr build for IPSpecialist?
Rowerr built the original WordPress and WooCommerce platform, then developed a custom e-store, LMS, memberships, bookings, role-based dashboards, content, community, messaging and notifications. The later platform combines a React web application with a React Native mobile application and shared PostgreSQL data.
02Why did IPSpecialist move from WordPress to a custom platform?
Its requirements expanded across commerce, learning, memberships, bookings, communication and multi-role administration. Performance concerns, growing plugin dependencies and increasingly specialised workflows led to a purpose-built application. The decision followed requirements discovery in 2023 and architecture planning in 2024; development began in 2025.
03Does a slow WooCommerce store always need a rebuild?
No. Investigate hosting, database work, extensions, frontend assets, checkout and integrations first. Many issues can be resolved through optimisation or targeted WooCommerce development. A custom rebuild is appropriate only when the business requirements justify the development, migration and maintenance responsibilities.
04Which plugins powered the original IPSpecialist platform?
WordPress provided content management, WooCommerce powered the e-store, LearnDash supported courses, MemberPress handled memberships and user requirements, Amelia supported events and bookings, and Elementor with add-ons provided page design and presentation. These tools belong to the original phase, not the custom replacement stack.
05How can an eCommerce purchase connect to courses and memberships?
Define which purchased products grant which course or membership entitlements, then connect confirmed payment and access rules to the customer account. In the IPSpecialist rebuild, commerce, learning, memberships and bookings became modules in the same platform rather than separate plugin workflows.
06How were regional payment requirements handled?
The custom e-store incorporated payment integrations including Paystack, PayFast and additional regional options around the client's markets. Availability, currencies, settlement and recurring-payment support still depend on each provider and merchant configuration; integration does not mean every payment method supports every billing model.
07What can users manage through the IPSpecialist mobile application?
The React Native and TypeScript application provides a role-based interface to the broader platform, including relevant dashboards, learning, profiles, communication, community activity and notifications. Students, instructors and administrators access functions according to their permissions. A public App Store or Google Play release is not claimed here.
08Do the web and mobile applications use the same database?
Yes. Both use the same underlying Supabase PostgreSQL data source for shared customer, learning and commerce records. Frontends work through authorised application interfaces rather than acting as separate databases. A shared database does not automatically refresh every open screen; that requires appropriate application refresh or real-time behaviour.
09What technology replaced the WordPress platform?
The custom web application uses React and TypeScript, with Node.js and Express for backend services and Supabase PostgreSQL for data. The mobile application uses React Native and TypeScript. An ORM-based access layer connects backend code with database models; a specific ORM is not named without production confirmation.
10What results are documented, and when should a store consider similar development?
The documented result is a connected custom commerce, learning and operations platform with web and mobile interfaces. No verified before-and-after revenue, conversion or speed dataset is available for this case study. Consider similar development when clearly mapped business workflows cannot be supported maintainably within the existing architecture, rather than migrating solely because a store is growing.
Is your eCommerce platform growing faster than its architecture?
Whether you need WooCommerce development, checkout improvements, a custom LMS or connected web and mobile applications, start with the business problem.
Discuss Your eCommerce Project →Explore WooCommerce Development Services