Nostr Web App UX Testing Script

As Nostr adoption grows and more web applications integrate decentralized identity, payments, and social functionality, it's critical to ensure a seamless and reliable user experience across platforms, devices, and authentication methods. This UX testing script was created to validate core functionality, such as login via popular signing tools (Alby, nos2x, Amber, NAK), zapping on both mobile and desktop, and contact list management, while also ensuring consistency across browsers and operating systems. The goal is to catch usability issues early, maintain trust in decentralized apps, and support a smoother on-boarding experience for new and existing Nostr users.

🧰 Environment Setup

Browsers to test:

Chrome (latest)
Firefox (latest)
Brave (latest)
Safari (latest macOS/iOS only)

Platforms:

Desktop (Windows/macOS/Linux)
Mobile (Android/iOS)

Signing Extensions & Tools:

Alby (Browser extension)
nos2x (Browser extension)
Nostash (iOS browser extension)
Amber (Mobile key manager)
NAK (CLI + Bunker)
Plaintext NSEC login (insecure method, for dev testing)

✅ Test Areas & Steps

1. 🔐 Authentication & Signing

1.1 — Browser Extension Login (Alby, nos2x, Nostash)

Install Alby and nos2x on supported browsers.
Visit the Nostr web app.
Attempt login with:
- Alby
- Nos2x
- Nostash (iOS only)
Confirm the app correctly detects the extension.
Confirm the login signature is accepted and the session is established.

1.2 — NAK + Bunker Flow

Connect to a NIP-46 bunker using NAK CLI or Amber Bunker.
Approve login request via terminal or Amber.
Confirm successful login.
Refresh and ensure the session persists.

1.3 — Amber Login (if applicable)

On a mobile browser, log in using Amber (NIP-46) if applicable.
Ensure QR connection/flow works as expected.
Confirm login and session persistence after navigation.
Refresh and ensure the session persists.

1.4 — NSEC Login (if supported)

Enter raw NSEC in the login field.
Confirm app accepts login and reflects correct pubkey.
Log out and verify session clears.

2. ⚡ Zaps & Payments

2.1 — Mobile Zaps (if applicable)

On mobile browser with WebLN support (Alby or integrated app):
- Locate a zappable post or profile.
- Initiate a zap.
- Confirm zap invoice resolves and payment completes.
- Validate that it shows in the zap list.

2.2 — Desktop Zaps with Alby

Log in using Alby.
Zap a post.
Confirm the popup appears correctly and doesn't get blocked by the browser.
Ensure sats are deducted and confirmation appears.

3. 👥 Contact List Management

3.1 — Add Contacts

Add a known pubkey or profile to the contact list.
Reload app and confirm the contact persists.
Verify that the contact list was not nuked.

3.2 — Remove Contacts

Remove contact(s).
Reload and ensure they are removed.
Add a new contact again to confirm the list wasn’t nuked.

3.3 — Add and Remove in Sequence

Add two contacts.
Remove one.
Add another.
Reload and ensure only the intended changes were applied and contact list is intact.

4. 🧭 Core App Functionality

Check the following features while logged in with each signing method:

View content feed / following feed if applicable
Post a note / create app event if applicable
Like and reply to another note if applicable
Search for a profile or note if applicable
Update profile metadata (name, picture, bio, etc.) if applicable
Upload image to test Blossom functionality if applicable
Test each feature with Alby, nos2x, Nostash, NAK/Bunker, Amber, and NSEC.

5. 📱 Mobile vs Desktop Parity

Compare mobile and desktop flows:

Are all buttons and features accessible?
Does any modal or extension popup get blocked on mobile?
Is scrolling and navigation smooth?

🧾 Post-Test Checklist

After testing with each setup:

App detects and prioritizes correct signing method
Contact list is preserved correctly after changes
Zaps complete successfully and reflect in UI
Feeds load consistently across logins
Profiles can be updated
Mobile and desktop experiences are consistent