Fewer bot flags, but no guarantee of account safety
According to PiunikaWeb, co-founder Chanhee said the forthcoming update would substantially reduce how often websites identify Aside’s assistant as a bot. The report provides no version number, numerical results, test methodology, or list of affected websites. That makes this a developer performance claim—not yet a demonstrated reliability improvement.
Asked about LinkedIn, Chanhee reportedly cautioned that conspicuously rapid activity could still cause problems, using three profile visits in ten seconds as an example. That illustration should not be read as a published LinkedIn limit or a safe automation threshold. The report establishes neither.
The practical conclusion is narrower than “the bot problem is solved.” A reduction in automated detection would not, by itself, establish permission to automate a website or guarantee protection from account restrictions. Users evaluating the update should distinguish fewer interruptions from approved automated activity.
Windows support already exists
Aside’s official download page already identifies the browser as available for macOS and Windows and provides Windows installation instructions. An Arm64 edition would therefore expand its Windows architecture support rather than mark its first arrival on Microsoft’s operating system.
PiunikaWeb reports that co-founder and CTO Dora Lee separately asked whether users wanted an Arm64 Windows version. The same report says Chanhee expected v2, including Windows support, around late October to early November 2026. That remains an anticipated window, not a firm release date.
There is a further indication beyond the social-media question: an inspected capture of Aside’s official download page labels Windows x64 for Intel/AMD and Windows ARM64 as “Coming soon.” That supports treating Arm64 as an advertised forthcoming option, but it does not establish a delivery date or an available installer.
What native Arm64 could change
Microsoft’s Windows Arm-based PCs FAQ supplies useful context: Windows 11 on Arm can run many applications through emulation, while applications rebuilt for Arm offer the best performance. Microsoft also documents Prism emulation in Windows 11 version 24H2, with improved performance for emulated applications. Emulated does not automatically mean unusable; native remains the preferred performance path.
For Aside, that makes native Arm64 support worth watching—but it does not justify promising longer battery life, faster tab switching, or lower CPU use. Those would require measurements of Aside itself on relevant hardware. Microsoft’s general compatibility guidance cannot substitute for a browser benchmark.
A roadmap, not a finished overhaul
The announcements sit alongside Aside’s reported v2 shift toward background automation and desktop control. That broader ambition explains why both dependable website interaction and Windows support matter, but the reporting does not establish that the bot-detection adjustment and Arm64 release will arrive together.
For Windows users, the sensible checkpoint is delivery: release notes identifying the detection changes, a downloadable Arm64 installer, and results showing how each behaves in practice. Until then, these are encouraging development signals—not reasons to hand an assistant the keys to a business-critical account.