Cross-Platform React Component Library
Budget: $10 – $1,000 AUD
I already have a React JS package built with TypeScript and Storybook. Now I need the codebase reorganised into a true cross-platform library that runs seamlessly on both React JS for the web and React Native for mobile, with the bulk of the logic written once and platform-specific files split into .web and .native variants.
The main objective is code reuse, so every shared behaviour, prop interface, and test must live in a single source of truth. The UI surface will start with core elements—Button, Input Field and Dropdown—plus a small set of layout primitives (Centre, Stack, Grid, GridItem, Box, Flex and a few more). Think of the basic coverage you get from PrimeReact, but implemented in a way that can be consumed by either platform without API changes.
To make this happen, the library should:
• Keep all shared logic in one package folder.
• Expose platform files that only swap presentation (e.g., styling or hooks that differ between DOM and native components).
• Ship an updated Storybook that can preview the components in both environments.
• Remain fully typed with TypeScript and ready for publishing to npm.
I will supply the existing repository and Storybook configuration; you return the refactored mono-repo (or workspaces) structure with clear build scripts, reusable tests and at least one working example app per platform to prove installation works through yarn/npm.
If this sounds straightforward and you are comfortable juggling React JS, React Native, TypeScript and Storybook, let’s get started.
The main objective is code reuse, so every shared behaviour, prop interface, and test must live in a single source of truth. The UI surface will start with core elements—Button, Input Field and Dropdown—plus a small set of layout primitives (Centre, Stack, Grid, GridItem, Box, Flex and a few more). Think of the basic coverage you get from PrimeReact, but implemented in a way that can be consumed by either platform without API changes.
To make this happen, the library should:
• Keep all shared logic in one package folder.
• Expose platform files that only swap presentation (e.g., styling or hooks that differ between DOM and native components).
• Ship an updated Storybook that can preview the components in both environments.
• Remain fully typed with TypeScript and ready for publishing to npm.
I will supply the existing repository and Storybook configuration; you return the refactored mono-repo (or workspaces) structure with clear build scripts, reusable tests and at least one working example app per platform to prove installation works through yarn/npm.
If this sounds straightforward and you are comfortable juggling React JS, React Native, TypeScript and Storybook, let’s get started.
Related categories:
JavaScript
Mobile App Development
HTML5
AngularJS
Yarn
Web Development
React Native
Mobile Development