-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Description
📝 Description
Based on the Polkadot.js roadmap announcement, we are creating this major issue to track upcoming features and enhancements. The following tasks focus on improving the developer experience within the Polkadot JS UI by streamlining workflows, enhancing visibility, and reducing friction for both developers and users.
✅ Task List
-
🔍 Event Filtering by Account
Add an optional toggle to filter events involving only accounts registered in the user’s PolkadotJS extension.
Improves developer experience by decluttering event views. -
⭐ Favorite Chains #11707
Enable users to mark parachains as "favorites" for quick access in a top-level dropdown or side menu.
Reduces friction for users who frequently switch between specific chains. -
🌐 Simplified Chain Endpoint Selection
Implement automatic endpoint rotation from a pool of verified public RPCs, with an advanced manual override.
Improves accessibility for new users and balances traffic across providers. -
🔁 Enhanced Teleport UX from Asset Hub #11705
Expand teleport destinations beyond Relay Chain to include other system parachains like People, BridgeHub, etc.
Enables more flexible asset teleporting as Asset Hub expected to play a central role post AHM. -
🛎️ Notification Panel
Add a notification panel to show recent transactions with details like type, status, block number/hash.
Include toast popups with direct links.
Makes activity tracking easier, especially on chains without Subscan. -
🖋️ Multisig Tab
Add a dedicated “Multisig” tab under the Accounts section to view and manage pending approvals.
Improves visibility and actionability of multisig transactions. -
⚛️ Electron App Deprecation ❗ Community Feedback Wanted
The Electron version of the Polkadot JS UI hasn’t seen much usage, and maintaining it requires effort—especially around security—that could be redirected toward new features.
We are considering ending active support for Electron.
Each task will be broken out into its own issue linked to this master ticket as development begins, allowing for modular tracking, implementation, and review.