Edited By
Laura Cheng

A growing number of Trezor users are expressing frustration over the prolonged lack of a promised feature in the Trezor Suite for iOS. Months after announcing custom backend functionality, users are left wondering about the delay, particularly for TOR support, essential for certain workflows.
Recent discussions in various user boards highlight a widespread dissatisfaction with the current situation. The custom backend feature, crucial for many workflows, is still inoperable, raising serious concerns about Trezor's commitment to its promises.
"That frustration is pretty understandable clearer communication would probably calm a lot of people down," shared a community member.
The sentiment reflects a mix of disappointment and a call for more transparency.
Many have pointed out that when a feature is publicly announced, expectations are built around it. Users feel abandoned without updates or acknowledgments of the technical difficulties causing the delays. As one commenter put it, "Can we at least get a bit more information?"
Community Anxiety: Users are increasingly anxious about the future of the application due to prolonged unfulfilled promises.
Expectation Management: Technical or security issues aside, users crave regular updates to manage their expectations.
Focus on Trezor Suite: The core conversation centers around Trezor Suite for iOS, reinforcing the belief that better communication is essential for credibility.
π» Users express frustration over delays in promised features.
β Clearer communication could alleviate concerns among the community.
π "It's YOU who proudly announced this functionality" reflects the shared sentiment for accountability.
With the iOS community growing increasingly vocal, Trezorβs next steps will be crucial for shaping user confidence. As frustrations mount, will the company step up to address these issues, or will the silence continue? Only time will tell.
Given the current frustrations and calls for clarity, thereβs a strong chance that Trezor will prioritize communication in the coming months. Users are likely to see some form of update regarding the custom backend feature, potentially within the next quarter, as the company understands the growing impatience in its community. If Trezor fails to address these concerns swiftly, experts estimate around a 60% probability that user confidence will wane further, possibly driving users to explore alternative wallets. The path forward may include regular updates about development setbacks, alongside a renewed commitment to transparency in its progress.
Looking back, this situation echoes the tech worldβs early days of video streaming platforms. Just as users clamored for new features during the launch of services like Netflix, frustrations over delays spurred creativity and alternatives within the industry. Users felt compelled to voice their demands, shaping the future of content consumption into what it is today. Similarly, Trezorβs current scenario could be a catalyst for profound change as users demand accountability; a scenario where silence could cultivate unforeseen innovation or competition.