How to use the Next.js Serwist Thirdweb embedded wallet template
This guide walks you through using the template which uses Next.js, Serwist (offline capabilities), and Thirdweb embedded wallet to build a Progressive Web Application (PWA) on Monad.
Prerequisites
- Node.js (v18 or higher)
- a Thirdweb account
Setup
-
Clone the repository:
git clone https://github.com/monad-developers/next-serwist-thirdweb.git -
cd
into the project directory:cd next-serwist-thirdweb -
Install dependencies:
npm install -
Create a
.env.local
file in the root directory:cp .env.example .env.local -
Start adding your environment variables to the
.env.local
file:# Thirdweb Configuration (Required)NEXT_PUBLIC_THIRDWEB_CLIENT_ID=your_thirdweb_client_id_here# Web Push (Required)WEB_PUSH_EMAIL=user@example.comWEB_PUSH_PRIVATE_KEY=your_vapid_private_keyNEXT_PUBLIC_WEB_PUSH_PUBLIC_KEY=your_vapid_public_keyIf you lost your Thirdweb Client ID, you can find it in the Thirdweb dashboard.
-
Generate VAPID keys for web push notifications:
npx web-push generate-vapid-keys --jsonCopy the generated keys to your .env.local file (replace the placeholder values from step 5).
-
Running the Application:
Development Mode:
npm run devThe application will be available at http://localhost:3000.
Production Mode:
For full PWA functionality (including install prompts):
npm run build && npm run start
Folder structure of the template
next-serwist-thirdweb/├── app/│ ├── components/ # React components│ │ ├── InstallPWA.tsx # PWA install prompt│ │ └── ...│ ├── ~offline/ # Offline page│ └── ...├── public/ # Static assets└── ...
Changing the app name
- Edit
public/manifest.json
:- Change the
name
andshort_name
fields
- Change the
- Run
npm run build
to update the app
Notification Setup
To receive push notifications from this app, you need to enable notifications in your browser and/or system settings.
Browser Settings
Chrome/Edge
- Click the lock icon 🔒 in the address bar
- Set "Notifications" to "Allow"
- Or go to Settings → Privacy and security → Site Settings → Notifications
Firefox
- Click the shield icon 🛡️ in the address bar
- Turn off "Enhanced Tracking Protection" for this site (if needed)
- Allow notifications when prompted
- Or go to Settings → Privacy & Security → Permissions → Notifications
Safari
- Go to Safari → Settings → Websites → Notifications
- Find your site and set it to "Allow"
System Settings
macOS
- System Preferences → Notifications & Focus
- Find your browser and ensure notifications are enabled
- Check "Allow notifications from websites" in browser settings
Windows
- Settings → System → Notifications & actions
- Ensure your browser can send notifications
- Check browser notification settings
iOS
- Settings → Notifications → [Your Browser]
- Enable "Allow Notifications"
- Also enable in browser settings
Android
- Settings → Apps → [Your Browser] → Notifications
- Enable notifications
- Check browser notification permissions
Backend Integration Required
SendNotification.tsx
component is sample codeSendNotification.tsx
requires backend implementation:
- Save subscription data when users subscribe (see TODO comments in code)
- Delete subscription data when users unsubscribe
- Implement
/notification
endpoint to send actual push notifications - Use
web-push
library or similar for server-side notification delivery
Customizing Notification Content
To customize your push notification content, edit app/notification/route.ts
and modify the title
, message
, icon
, and other properties in the sendNotification
call.
Modifying the App Icon & Splash Screen
App Icons
Replace the icon files in the public/icons/
directory with your custom icons:
icon-512x512.png
- Main app icon (512×512px)android-chrome-192x192.png
- Android icon (192×192px)apple-touch-icon.png
- iOS home screen icon (180×180px)
Also update the favicon:
public/favicon.ico
- Browser faviconapp/favicon.ico
- Next.js app favicon
Splash Screen
Splash screens are automatically generated from your app icon and theme colors defined in public/manifest.json
. To customize:
- Update the
theme_color
andbackground_color
inpublic/manifest.json
- Ensure your main icon (
icon-512x512.png
) represents your brand - Run
npm run build
to apply changes
Use tools like PWA Asset Generator to create all required icon sizes from a single source image.
Deploying to Vercel
Using Vercel Dashboard
-
Connect your repository:
- Push your code to GitHub
- Visit vercel.com and import your repository
-
Configure environment variables:
- In your Vercel project dashboard, go to Settings → Environment Variables
- Add the same variables from your
.env.local
:NEXT_PUBLIC_THIRDWEB_CLIENT_IDWEB_PUSH_EMAILWEB_PUSH_PRIVATE_KEYNEXT_PUBLIC_WEB_PUSH_PUBLIC_KEY
-
Deploy: Vercel will automatically build and deploy your app
-
Update Thirdweb settings: In your Thirdweb dashboard, add your Vercel domain (e.g.,
your-app.vercel.app
) to the allowed origins
PWA features (install prompts, offline support, push notifications) work automatically on HTTPS domains like Vercel deployments.
Using Vercel CLI
Alternatively, deploy using the Vercel CLI:
-
Install Vercel CLI:
npm i -g vercel -
Login to Vercel:
vercel login -
Deploy:
vercelFollow the prompts to configure your project.
-
Add environment variables:
vercel env add NEXT_PUBLIC_THIRDWEB_CLIENT_IDvercel env add WEB_PUSH_EMAILvercel env add WEB_PUSH_PRIVATE_KEYvercel env add NEXT_PUBLIC_WEB_PUSH_PUBLIC_KEYOr you can go to the Vercel dashboard and add the environment variables there.
-
Redeploy with environment variables:
vercel --prod
Learn more
- Serwist: docs | guides
- Thirdweb: docs | guides
- Monad: supported tooling and infra