< Kabir />
Please wait while we prepare your content
Please wait while we prepare your content

This platform is built specifically for Nitex buyers, providing a seamless way to manage collections, sample requests, costing requests, Pick & Choose (P&C), and order workflows. Account managers can share curated collections directly from the Admin Platform, while buyers can explore designs in the Design Lab and instantly place sample or costing requests. To enhance communication, buyers can chat directly with their account managers within the Platform. Buyers can also create folders, invite team members, and organize shared content for efficient collaboration. From these folders, detailed requests can be submitted and, once approved, easily converted into orders. A real-time order tracker offers complete transparency, showcasing each stage of production—from cutting and sewing to washing—along with live updates and notifications for better visibility and control.
Image loading delays in certain countries. Our site was deployed in the AWS Singapore region, causing slower image load times for users in Europe while performing well in Asia.
We implemented CDN caching and added a geolocation detector in the frontend to identify the user’s location and load images from the nearest region.
Image load times improved significantly, resulting in a much better user experience.
Large initial bundles and excessive re-renders on list and search screens were significantly degrading responsiveness and user experience.
Introduced route-level code splitting to reduce bundle size, optimized data subscriptions to limit unnecessary updates, implemented list virtualization for efficient rendering, and compressed/optimized media assets.
Achieved faster initial load times, smoother navigation, and noticeably reduced rendering and network overhead, resulting in a more responsive user experience.
Mixed data flows (custom HTTP, thunks, and context) along with scattered storage access made application behavior difficult to manage and understand.
Introduced a clear separation of concerns — using RTK slices for app/UI state, RTK Query for server state, a centralized auth/session guard, and a feature-based project structure.
Resulted in cleaner boundaries, easier testing and onboarding, and significantly fewer side-effect-related bugs.
We were facing undetected production bugs due to insufficient test coverage.
We covered the entire application with unit tests using Jest (React Testing Library) to catch issues early and improve overall stability.
Significantly reduced production bugs, improved reliability, and increased developer confidence in releases.
30% Improvement
20% Improvement
40% Improvement