Feedback
Changelog

Have something to say?

Tell us how we could make the product more useful to you.

Completed

UI/UX Recommendations for the new Alcor Exchange UI Upgrades

As of February 13, 2026, the following recommendations are derived from Piga’s feedback on the new Alcor Exchange interface. These suggestions aim to enhance usability, accessibility, and user confidence while addressing reported issues in navigation, functionality, and responsiveness. They are categorized into core features, minor UI improvements, and UX enhancements for risk mitigation. 1. Core Feature Transition Support To facilitate a smooth migration from the legacy version (Alcor v1) to the new UI, especially while certain features are still under development: Add a "Return to Alcor v1" Link: Place a persistent link in the footer of the new UI, allowing users to easily switch back to the original version. This provides flexibility for users who prefer the familiar interface or encounter missing functionalities. Rationale: Reduces frustration during the transition period and accommodates diverse user preferences. Priority: High. 2. Minor UI Improvements and Bug Fixes These address specific usability hiccups identified in the Trade/Spot markets and related sections, focusing on consistency, redundancy, and visual clarity: Auto-Fill Price on Order Click: Restore the functionality where clicking an order price in the Trade/Spot order book automatically populates the price field in the trade panel. Rationale: This was a valued feature in the previous version, streamlining the trading process and reducing manual input errors. Priority: Medium. Default Trade Mode Configuration: Set the default trade view to Limit Order with input fields visible but disabled when "Market Trade" is selected (e.g., via a toggle switch or checkbox). Users can then enable and set a price if desired. Rationale: This educates users on available options without forcing tab switches, promoting discovery of limit orders while maintaining simplicity for market trades. Priority: Medium. Enhance "Market Price" Display: Replace or supplement the "Market Price" field (which shows the last traded price) with current Swap Price rates, displayed prominently above the slippage indicator. Retain the last traded price if needed, but ensure it's not redundant with chart displays. Rationale: The last traded price is already visible in multiple locations (e.g., chart and above-chart indicators), making the current field less useful. Showing Swap rates provides more actionable context for decision-making. Priority: Medium. Favorites Display Format: When adding favorites in the Trade/Spot market, display both the Quote and Base tokens in the favorites row (e.g., "QUOTE/BASE"). Rationale: Showing only the Base token can appear inconsistent, especially with multiple markets for the same base, leading to confusion in quick scans. Priority: Low. Correct Farm Earnings Estimates: Fix the display of Farm earnings estimates on the Pools overview and individual position pages, as they currently appear inflated by a factor of approximately one million. Rationale: This is likely a calculation or formatting bug that could mislead users about potential returns, eroding trust in the platform. Priority: High (potential financial misinformation). Responsive Design Optimization: Adjust the layout breakpoints to ensure seamless functionality across screen sizes. Specifically, bridge the gap between mobile (up to 768px) and desktop (from 1440px) by introducing an intermediate tablet-friendly layout or flexible components. Rationale: Users with screen widths between 768px and 1440px (common on laptops or tablets) currently cannot place trades, creating a significant accessibility barrier. Priority: High (affects a wide range of devices). 3. UX Enhancements for Risk Mitigation To build user trust and prevent negative experiences, particularly for novice traders in Spot Markets where liquidity is often low and spreads high: Market Order Confirmation with Swap Alternative: Implement a modal confirmation dialog for Spot Market orders that compares the estimated output with equivalent Swap pair options. If the Swap yields a better rate (e.g., higher output due to better liquidity), display a warning notice with details and an option to redirect to Alcor Swap for execution. Rationale: Spot Markets on platforms like WAX can lead to suboptimal trades for inexperienced users, potentially causing significant losses or confusion. This proactive guidance educates users on better alternatives, reduces "gotcha" moments, and fosters confidence in the platform's DeFi features. It aligns with best practices for user-centric design by simplifying complex choices without overwhelming the interface. Priority: High (directly impacts user safety and retention). Estimated Impact: Could prevent accidental poor trades, turning potential frustration into educational opportunities and encouraging broader platform exploration. These recommendations position Alcor Exchange as a more intuitive, reliable, and user-friendly platform, ultimately driving higher adoption and trust among both novice and experienced traders. If additional data or prototypes are needed, further analysis can be conducted.

Henrik Piga 18 days ago

Completed

Burn / Lock LP token to increase trust in token pairs

The ability to properly block LP token pairs is present in all important DEXs and it's a key factor when it comes to providing safety for users when interacting with unknown tokens. As well, as project developers, it's best to do everything in our power to make our users trust in our projects. By having the possibility to do either (burn or lock) the LP pairs, we could all benefit in the long term.

HaveANiceDaySir Almost 2 years ago

Completed

API for Farms

Please create an api that would return all the current farms an account is currently in. I have a collab that has invested in a bunch of farms and I collect daily to spread the rewards around. Currently if I switch farms, I have to update the scripts to account for the new farm positions and ids. Would love to be able to directly query and then parse what I needed Thanks

Christopher Glinski About 2 years ago