Need MERN React/Web3 developers
Budget: $120 – $160 USD
I’ve got an established MERN application and now the interface needs a refresh. The scope is strictly User Interface—workflow logic stays the same—so your first task will be translating our detailed Figma mock-ups into clean, responsive React components.
I need someone who understands the subtleties of wallet connections, on-chain state updates, and error handling in a decentralised environment. If you have never shipped a Web3 feature, this job isn’t a good fit.
Key points you’ll tackle
• Rebuild screens and shared components exactly as shown in the mock-up, keeping the current React, Redux Toolkit, Express and MongoDB stack.
• Preserve or improve gas-sensitive UX touches—e.g., optimistic UI that rolls back on failed transactions.
• Commit early and often to our GitHub repo so code reviews stay fluid; the CI pipeline will flag lint and test issues automatically.
Acceptance criteria
1. Every page pixel-matches the approved design at desktop and mobile breakpoints.
2. All existing smart-contract calls (read & write) function flawlessly after the UI swap.
3. No new eslint, TypeScript or unit-test errors are introduced.
If this sounds straightforward given your React + Web3 track record, let’s get started.
I need someone who understands the subtleties of wallet connections, on-chain state updates, and error handling in a decentralised environment. If you have never shipped a Web3 feature, this job isn’t a good fit.
Key points you’ll tackle
• Rebuild screens and shared components exactly as shown in the mock-up, keeping the current React, Redux Toolkit, Express and MongoDB stack.
• Preserve or improve gas-sensitive UX touches—e.g., optimistic UI that rolls back on failed transactions.
• Commit early and often to our GitHub repo so code reviews stay fluid; the CI pipeline will flag lint and test issues automatically.
Acceptance criteria
1. Every page pixel-matches the approved design at desktop and mobile breakpoints.
2. All existing smart-contract calls (read & write) function flawlessly after the UI swap.
3. No new eslint, TypeScript or unit-test errors are introduced.
If this sounds straightforward given your React + Web3 track record, let’s get started.