Streaming as infrastructure
Signed media access, byte-range responses, duration accuracy, and URL refresh behavior were treated as one playback contract across storage, API, and mobile.
06
Neginawave
A gospel-media platform recovered across every product surface
ExpoNode.jsS3Paystack
Overview
Neginawave gives gospel artists, pastors, and podcasters one platform to publish music, sermons, and podcasts while listeners discover and stream faith-centred media across devices. My contract focused on recovering the existing product and turning its mobile, backend, web, creator, and administrative surfaces into one dependable system.
One home for gospel media,
from creators to listeners.
My role at Neginawave
Fullstack Developer · Contract
August—September 2026
Remote · Nigeria
I led a coordinated recovery across mobile, backend, web, creator, and admin systems.
- 01
Prepared the backend for production on Railway with validated configuration, Resend, SendGrid and SES email providers, Paystack verification, and S3-compatible storage.
- 02
Hardened signup, password recovery, email normalization, account deletion, and premium-status synchronization across platforms.
- 03
Built secure media delivery with signed URLs, byte-range streaming, format validation, accurate durations, and large-file upload support.
- 04
Upgraded the mobile application to Expo SDK 54, configured EAS builds, and fixed native playback, signed-URL refresh, and overlapping-audio failures.
- 05
Implemented deep links and shareable smart links with Apple and Android association files and branded Open Graph previews.
- 06
Completed the creator portal, administrator console, moderation workflows, catalog discovery, support tooling, premium management, and listen-session analytics.
01 / Challenge
The conditions that shaped the system.
A useful architecture begins with the real constraint.
The product’s failures crossed application boundaries. A playback issue could involve the Expo client, expiring signed storage access, HTTP range behavior, media validation, or backend authorization. At the same time, incomplete creator and admin tools blocked publishing, moderation, payments, analytics, and catalog growth.
02 / System map
From input to outcome
01Listener & creator
→02Expo and web clients
→03Node.js backend
→04Signed media storage
→05Payments & smart links
→06Admin & analytics
03 / Approach
How the build was organised.
Make the boundaries clear, then move.
- 01
Made the Railway backend production-ready with environment validation, provider-independent email delivery, Paystack verification, S3-compatible storage, and stronger authentication and account lifecycle handling.
- 02
Built secure streaming around signed URLs, byte-range requests, upload validation, duration calculation, and large-file support, then stabilised native playback after upgrading the mobile app to Expo SDK 54.
- 03
Completed the creator portal, administrator console, public web experience, smart links, catalog features, moderation flows, and analytics as one coordinated platform recovery.
Decisions that carried the product.
One link, correct destination
Smart links connect public sharing, mobile deep links, app association, and branded previews for music, sermons, podcasts, and playlists.
Recovery across boundaries
Changes were traced through clients, APIs, storage, payments, deployment, and administration so fixes held across the whole platform.
What changed after the work.
- ↗Stabilised native audio playback and upgraded the application to Expo SDK 54 with EAS build support.
- ↗Delivered functional creator, administration, moderation, premium-account, support, and analytics tooling.
- ↗Implemented production-ready streaming, payments, smart links, catalog discovery, playlists, likes, follows, and caching across mobile and web.
