Media Hub was delivered using SolGuruz 10-stage development lifecycle, scaled for cross-format content architecture and editorial CMS depth.
Stage 01
Discovery & Content Licensing Analysis
Stakeholder interviews to understand iMusti's content distribution business, publisher and creator relationships, target audiences, and digital transformation goals. Content licensing analysis covering book publishing rights, audiobook narrator agreements, video creator agreements, and music label partnerships. Competitor teardowns across single-format leaders (Audible, Kindle, Netflix, Spotify) and multi-format platforms (Scribd, Hoopla, Everand). Deliverable: discovery document, content licensing matrix, prioritised feature list.
Stage 02
Requirement Analysis & Documentation
User stories and acceptance criteria for every workflow across consumer, editorial, and rights management roles. Cross-format content discovery user flows, personalised recommendation flows, content consumption flows for each format type. Data flow diagrams for content ingestion, catalog search, recommendation engine, and royalty distribution.
Stage 03
UX/UI Design
Information architecture, wireframes, interactive prototypes, and full design system in Figma. Designed against three primary personas: the cross-format consumer (reads books, listens to audiobooks, watches video, plays music), the discovery-first browser (explores curated collections, follows editorial recommendations), and the library-builder (saves favourites, builds reading lists). Visual design system with cross-format consistency, the same content card pattern works for books, audiobooks, video, and music with format-specific accent treatments.
Stage 04
Architecture & Cross-Format Database Design
System design covering React + Next.js component architecture, Node.js backend service decomposition, recommendation engine architecture, and cross-format database schema. Database design with shared content metadata plus format-specific extensions, relational integrity for rights and royalty data, and graph edges for cross-format relationships. CDN architecture for content delivery.
Stage 05
Frontend Development (React + Next.js)
React + Next.js build for the consumer-facing web app. Server-side rendering for SEO-critical pages (content detail pages, category pages, search results). Component library covering catalog browse, content cards (cross-format), content detail views (format-specific players for ebook reader, audiobook player, video player, music player), search interface, recommendation surfaces, and account management. Responsive design across desktop, tablet, and mobile web.
Stage 06
Backend & Recommendation Engine Development
Node.js API layer handling authentication, catalog search, cross-format recommendations, content metadata management, royalty tracking, and notification orchestration. PostgreSQL for relational integrity. Recommendation engine combining collaborative filtering and content-based filtering with cross-format awareness. Firebase for real-time content sync across devices.
Stage 07
CMS Integration & Editorial Workflows
CMS configuration for the iMusti editorial team. Content ingestion workflows for bulk catalog upload from publishers and creators. Editorial curation tools for cross-format collections. Rights agreement capture per content piece. Release scheduling for coordinated launches. Takedown request handling with audit trail.
Stage 08
Quality Assurance & Cross-Browser Testing
Functional testing across desktop browsers (Chrome, Safari, Firefox, Edge), tablet, and mobile web (iOS Safari, Chrome Android). End-to-end testing of catalog browse, content discovery, format-specific consumption (ebook reader, audiobook player, video player, music player), payment, and CMS publishing flows. Performance testing for page-load speed and content streaming reliability.
Stage 09
Launch & SEO Foundation
Production deployment with AWS hosting, CDN configuration, SSL certificate setup, and search console submission. SEO foundation includes structured data, meta tags, Open Graph tags, sitemap, and robots.txt. Initial Google Search Console and Google Analytics 4 configuration for performance tracking.
Stage 10
Post-Launch Support & Iteration
2-week sprint cadence for performance fixes, UI refinements, and feature additions based on iMusti team feedback and consumer behaviour. Critical bugs are fixed within 24 hours, high-priority within 72 hours. Quarterly performance reviews covering organic traffic, recommendation engine performance, content consumption per user, and subscription conversion.