Full-Stack Developer Needed to Complete Existing Novel Platform — 5-Week Full-Time Project

Full-Stack Developer Needed to Complete Existing Novel Platform — 5-Week Full-Time Project Project Overview I am looking for a highly experienced full-stack developer to complete the remaining development work on an existing novel/web-fiction platform. This is not a project that needs to be built from scratch. The frontend, UI/UX design, page structure, and major backend foundation already exist. The existing admin panel is also functional. Some features in the current system are already partially implemented, some are UI-only, and others have not yet been started. The purpose of this contract is to take the existing codebase and complete all remaining functionality, connect the existing frontend to the backend, implement the missing systems, fix incomplete features, integrate payments and monetization, test everything thoroughly, and deliver a properly functioning production-ready platform. The target completion period is 5 weeks. This is a full-time, high-priority engagement. I am looking for someone who can dedicate substantial daily time to this project and make it their primary development focus during the contract. Please do not apply if you are currently committed to several other projects and cannot give this project serious, consistent attention. What Already Exists The current project already has: Existing frontend pages and UI/UX. Existing website structure. Existing admin panel. Existing backend foundation. Existing database/codebase. Existing authentication implementation. Existing reader pages and interface. Existing author/publishing interface. Existing wallet/payment-related UI. Existing mobile application/backend integration structure. However, several areas still require backend implementation, API integration, feature completion, correction, testing, and productionization. Some existing features are: Fully implemented but require integration. Partially implemented. UI-only/mock implementations. Not started. Functionally incomplete. Using static data instead of real database/API data. You will be working with the existing codebase rather than rebuilding the platform unnecessarily. Before beginning, you are expected to review the existing code and understand the current architecture. REQUIRED 5-WEEK MILESTONE PLAN WEEK 1 — Foundation, Public APIs & Core Backend The first milestone focuses on the backend/API foundation required by the rest of the platform. Public Reader APIs Implement and complete public/session reader endpoints for: Published stories. Story details. Chapters. Chapter access rules. Authors list. Search. Genres. Trending stories. Recommended stories. New releases. Rankings. The APIs must return proper dynamic data from the existing database and be suitable for both the website and mobile application where applicable. Admin → Website Content Synchronization Connect the existing admin-published/approved content to the public website. Admin-approved stories and authors must dynamically appear where required, including: Homepage. Discover. Recommendations. Rankings. Search. Author profiles. The website must no longer depend on static/mock story data where dynamic data is required. Routes & Missing Pages Implement/fix: .htaccess routes. Authors page. Trending page. Recommended page. New Release page. Last Read page. Broken/404 links. Proper 404 page. Centralized Configuration Implement centralized: Route constants. URL configuration. API paths. Business-rule constants. Minimum word requirements. Minimum chapter requirements. Reward amounts. Other shared configuration required by the platform. Week 1 Expected Result The core API and backend foundation must be functional and ready for the reader-facing features to consume real data. WEEK 2 — Reader Experience & Core Platform The second milestone focuses on converting the existing reader UI into a fully dynamic platform. Homepage Connect the existing homepage to real API data: Story carousel. Authors. Continue Reading. Recommended stories. New releases. Loading states. Empty states. Error handling. Discover Implement: Trending stories. Genre/category filters. Story grid. Functional genre buttons. API-driven content. Library Complete: Reading shelf. Saved shelf. Completed shelf. Reading progress. Persistent library state. Tabs. Filters. Search. Backend integration. Rankings Implement: Today. Week. Month. All-time. Dynamic podium. Dynamic ranking list. Ranking API. Functional filter drawer. Functional time-period buttons. Search Implement: Live search. Story search. Author search. Genre search. Search tabs. Dynamic results. Proper loading/empty/error states. View Book Connect the existing UI to dynamic data: Story information. Author information. Chapter list. Story metadata. Reading status. Unlock status. Read Book Complete: Dynamic chapter loading. Chapter navigation. Reading progress. Persistent reading progress. Chapter access checks. Unlock integration. Loading/error states. Week 2 Expected Result A user must be able to discover, search, open and read real stories through the platform, while their library and reading progress are properly persisted. WEEK 3 — Wallet, Coins, Unlocking, Payments & Rewards This milestone focuses on the complete monetization infrastructure. Wallet & Coin Ledger Implement: User wallet balance. Transaction records. Credit APIs. Debit APIs. Transaction history. Balance display. Profile wallet balance. Top-up integration. Secure transaction handling. Protection against duplicate/invalid transactions. Story Unlocking Implement the actual story/chapter unlocking system: Unlock rules. Locked chapter detection. Coin deduction. Unlock records. Gated chapter access. Duplicate-unlock prevention. View Book integration. Read Book integration. The existing cosmetic/UI-only story-lock functionality must be replaced with actual backend enforcement. Flutterwave — Website Integrate Flutterwave for website coin purchases: Coin packages. Checkout. Payment initiation. Payment verification. Webhook verification. Successful payment handling. Failed payment handling. Transaction records. Server-side coin crediting. Duplicate payment protection. Transaction history. Google Play Billing — Android Implement the required backend/payment integration for Android: Product IDs. Purchase flow integration requirements. Purchase-token/receipt validation. Server-side verification. Idempotent coin credit. Transaction logging. Shared wallet integration. Rewarded Ads / AdMob Implement: Rewarded-ad flow. Watch-ad task. Server-side reward granting. Reward validation. Abuse prevention. Wallet integration. Reward Amount Correction The current rewarded-ad amount is incorrect. It must be changed and enforced as: 0.1 coins per rewarded ad This must be corrected in both frontend and backend. Week 3 Expected Result The complete coin economy must function correctly: Top-up → Payment verification → Wallet credit → Balance → Unlock → Coin deduction → Transaction record and: Watch rewarded ad → Server verification → 0.1 coin reward → Wallet WEEK 4 — Social, Author Rules, Localization, Authentication & Supporting Features Follow / Unfollow Implement: Follow API. Unfollow API. Follower counts. Following counts. Network lists. Profile counts. Persistent follow state. Bookmark / Saved Library Implement: Save story. Remove saved story. Persistent saved state. Saved-library integration. Block / Mute / Report Implement: User blocking. Unblocking. Mute functionality. Reporting. Admin review queue. Appropriate handling of blocked users/content. Reviews & Comments Implement: Submit reviews. Retrieve reviews. Display reviews on View Book. Comments. Validation. Appropriate moderation handling. Author Rules Implement the required publishing rules. Chapter minimum: 300 words Backend validation. Save/publish validation. Author UI feedback. write.js integration. Minimum 18 chapters before Completed Count published chapters. Prevent premature completion. Backend enforcement. Author-center feedback. Internationalization Framework Implement: Locale resolver. Translation files. PHP translation helper. JavaScript translation helper. Language switcher. User language preference. Shared translation architecture. Public Page Translation Migrate hardcoded strings across: Public pages. Includes. JavaScript messages. Toasts. API messages. Story Content Translation Implement the agreed multi-language story/chapter content structure or translation workflow. Google OAuth Complete the existing partial implementation: Google Identity Services. Authorized origins. Browser testing. Chrome testing. Error handling. Email Verification Complete: Production SMTP configuration. .env configuration. Verification email. Deliverability testing. Verification flow. Profile & Settings Replace hardcoded profile information with dynamic data. Connect: Email. Phone. Wallet balance. Other required account information. Legal & Support Pages Implement/link: About Us. Content Licensing. Privacy Policy. Terms & Conditions. Replace placeholder # links. Week 4 Expected Result The remaining major application features should be implemented and connected. No major feature should remain merely as a cosmetic UI mockup. WEEK 5 — FULL QA, INTEGRATION, BUG FIXING & FINAL DELIVERY The fifth milestone is dedicated to making sure everything built during the previous four weeks actually works together. This week is not intended to be used for starting major unfinished features from the previous milestones. Full System Integration Test the complete user journey: Admin → Publish Story → Homepage → Discover → Search → View Book → Read Book → Library → Reading Progress → Unlock → Wallet → Payment → Transaction Also test: Author → Write → Chapter Validation → Publish → Story Appears Publicly And: User → Follow → Profile → Network → Library → Reviews/Comments Cross-Browser Testing Test on: Chrome. Safari. Firefox. Edge. Responsive Testing Test: Desktop. Tablet. Mobile web. Different screen sizes. Reader. Navigation. Forms. Filters. Modals. Library. Profile. Settings. Payment pages. API Testing Verify: Authentication. Authorization. API responses. Invalid requests. Missing parameters. Unauthorized access. Locked chapters. Wallet operations. Payment verification. Reward claims. Duplicate requests. Error handling. Security & Abuse Testing Pay particular attention to: Coin manipulation. Unlock bypass. Payment verification bypass. Reward abuse. Unauthorized chapter access. Unauthorized user actions. Duplicate transaction credit. API authorization. Input validation. Bug Fixing Fix all discovered: 404 errors. Broken links. JavaScript errors. API errors. Database errors. Authentication problems. Reader problems. Payment problems. Wallet problems. Responsive issues. UI rendering issues. Integration issues. Reader Protection Implement reasonable web-reader protection such as: Copy/select restrictions. Context-menu restrictions. Optional watermark. Other practical web-reader protections. The developer should understand the technical limitations of screenshot prevention on normal web browsers. Mobile API Documentation Document the APIs required by the mobile application, including: Reader APIs. Story APIs. Chapter APIs. Unlock APIs. Wallet APIs. Transaction APIs. Payment validation. Google Play purchase validation. Reward APIs. Authentication. Request/response formats. Error responses. Final Production Readiness Before final delivery: Verify production configuration. Verify environment variables. Verify API configuration. Verify payment configuration. Verify email configuration. Remove unnecessary mock/test data. Confirm database changes. Confirm production error handling. Confirm critical user flows. Confirm all milestones are integrated. Developer Requirements I am specifically looking for someone with strong experience in: Full-stack web development. PHP/backend development. REST APIs. MySQL/database architecture. JavaScript. Existing-codebase debugging and completion. Authentication. Payment gateway integration. Flutterwave. Google Play Billing. AdMob rewarded ads. Wallet/ledger systems. Transaction systems. API security. Responsive web development. Mobile/backend API integration. Localization/i18n. Production deployment and testing. Experience with novel platforms, publishing platforms, reading platforms, subscription/coin systems, marketplaces, or similar content platforms is a strong advantage. IMPORTANT — READ BEFORE APPLYING This project has a 5-week target completion period. I am not looking for someone who will work on this project for a few hours whenever they are free while simultaneously handling multiple other projects. I need a developer who is fully available, highly committed, responsive, and prepared to dedicate substantial daily time to this project. This is a serious full-time engagement. If you already have several active clients or projects that will prevent you from giving this project your primary attention, please do not apply. I also do not want unnecessary delays, repeated excuses, or a situation where the agreed timeline continuously changes after the contract begins. The milestone schedule will be used to track progress throughout the five weeks. Each milestone must have clearly demonstrable deliverables. Existing Codebase Review The developer will be working on an existing platform. You are expected to: Review the existing codebase. Understand the existing architecture. Identify what is already completed. Identify what is partially implemented. Identify what is UI-only. Identify what is missing. Work with the existing implementation where appropriate. Avoid unnecessarily rebuilding functioning components. Complete and integrate the remaining requirements listed above. Do not assume that everything needs to be rebuilt. Payment Structure Payment will be handled through milestone-based payments. The five milestones correspond to the five-week development schedule: Milestone 1 — Week 1: Foundation, APIs & Backend Milestone 2 — Week 2: Reader Experience & Core Platform Milestone 3 — Week 3: Wallet, Unlocking, Payments & Rewards Milestone 4 — Week 4: Social, Author Rules, Localization & Supporting Features Milestone 5 — Week 5: Full QA, Integration, Bug Fixing & Final Delivery The exact milestone amounts will be agreed before the contract begins. Before You Apply Please do not send a generic message such as: "I can do this. Please contact me." I want developers who have actually read the requirements. In your proposal, briefly provide: Your experience with similar platforms. Your experience working with existing codebases. Your experience with payment integrations, especially Flutterwave and Google Play Billing. Your experience with wallet/coin/transaction systems. Your availability during the 5-week period. How much time you can dedicate to the project daily. Your proposed milestone/payment expectations. Your estimated approach for completing the five milestones. Examples of relevant work you have completed. Only apply if you are confident that you have the technical ability and availability to complete this project within the target timeframe. The goal is simple: Take the existing platform, complete the remaining functionality listed above, properly integrate everything, fix the incomplete areas, thoroughly test it, and deliver a stable working product within the 5-week target.