2022-05-19
1911
#css#react#web3
MacBobby Chibuzor
111936
May 19, 2022 ⋅ 6 min read

Full-stack DApp tutorial with Vite + React, Tailwind CSS, and Solidity

MacBobby Chibuzor Go, Solidity, and Haskell developer interested in the cloud native world and blockchain technology. A fanatic for technical writing and open source contribution.

Recent posts:

Your AI Has Agency — Here’s How To Architect Its Frontend

Your AI has agency — here’s how to architect its frontend

AI’s not just following orders anymore. If you’re building the frontend, here’s how to design interfaces that actually understand your agent’s smarts.

Rosario De Chiara
Jun 25, 2025 ⋅ 5 min read
how to design apps with Apple Intelligence in mind

How to design apps with Apple Intelligence in mind

Apple Intelligence is here. What does it mean for frontend dev and UX? Explore the core features of the update, do’s and don’ts for designing with Apple Intelligence in mind, and reflect on the future of AI design.

Murat Yüksel
Jun 24, 2025 ⋅ 10 min read
How To Optimize Your Next.js App With After()

How to optimize your Next.js app with after()

Next.js’ after() is a new API that lets you run logic after your route has finished rendering, without blocking the client.

Temitope Oyedele
Jun 24, 2025 ⋅ 11 min read
JavaScript Loops Explained, And Best Practices

JavaScript loops explained, and best practices

JavaScript loops like for, for...of, and for...in are constructs that help run a piece of code multiple times.

Rahul Padalkar
Jun 23, 2025 ⋅ 8 min read
View all posts

2 Replies to "Full-stack DApp tutorial with Vite + React, Tailwind CSS, and Solidity"

  1. Have you seen moralis.io ? Speeds up web3 dev like crazy😅
    : Please check it out, it makes Dapps dev smoother and faster

    So we’ll just be needing => {

    React
    Solidity
    Moralis
    Remix
    }

    Nice content, I love the way you simplified your solidity though.
    This is my first time here👌

  2. Incomplete article. Footer.jsx, Loader.jsx, Navigation_bar.sx not being used anywhere. Neither is the transactionContext. Nor is the ABI.
    There is no interaction between the frontend and the smart contract.
    It looks like the article got truncated. Please fix it.

Leave a Reply