Signavale · Connected wallet

Accounts, permissions, and signing across two product surfaces.

Signavale began as a browser proof of concept with a separate mobile direction. The product needed one language for accounts, connected applications, permissions, activity, and transaction decisions.

Delivered project

This case study covers a real UnicornX project and the product system delivered around it.

This case study covers a real UnicornX delivery. The interface, scope, technology, and operating decisions below reflect the work completed for Signavale.

Signavale browser extension and mobile wallet interfaces

Project scope

The visible interface is one part of the delivery system.

The work combined product flows with the backend state, integrations, permissions, payments, and operating tools needed to make the experience coherent.

Shared account language

A Manifest V3 extension and Flutter mobile companion shared account and activity concepts across two product surfaces.

Connected-site permissions

Permission and activity flows gave connected applications an understandable boundary around account access.

Transaction review

Review journeys exposed recipient, asset, network fee, and total before a user approved a transaction.

Reference frame

A compact view of the product boundary.

Timeline
February to December 2023 · 11 months
Product surfaces
Browser extension · mobile companion
Project scope
$190K+
Technology
React · TypeScript · Manifest V3 · Flutter · Node.js · PostgreSQL · WalletConnect · viem · Keychain/Keystore

“Security work is where most agencies slow down. UnicornX got faster. The extension, the mobile companion, and the shared accounts layer all shipped in the same release window.”

Yuki TanakaLead Developer, Signavale

Have a related product in mind?

Shipping a wallet or extension where signing decisions have to be clear?

Tell us about the account model, the connected-app surface, and the release window. We can review the architecture or join the build.

Discuss your project