The gold standard for browsing, offering tabbed navigation, password management, and smooth zoom rendering.
One of the earliest iterations of the note-taking giant, allowing users to sync notes with their desktops—a precursor to the modern cloud. 2. Communication: Windows Live & Skype
The default "X" button on Windows Mobile windows did not actually close apps; it merely minimized them, quickly draining the device's limited RAM. Utilities like and HTC Task Manager were essential installations. Resco Explorer replaced the basic File Explorer with a robust system that included ZIP compression, built-in FTP support, and a registry editor, while task managers allowed users to force-close applications with a single tap. Multimedia and Web Browsing Pioneers
Stock Windows Mobile 6 was notoriously difficult to navigate with a finger, relying heavily on a stylus. To counter this, became one of the best-selling mobile applications of its era. It overlaid a gorgeous, finger-friendly, widget-based 3D carousel over the native "Today Screen," modernizing the device's aesthetics and utility. File Managers and Task Killers
The GPS locked. A tiny satellite icon blinked green. Then WeatherPanel did something unexpected: it pulled up a from that exact date—May 17, 2009. The last time Elena had used the app.
A massive toolbox that added tabbed browsing to Internet Explorer, closing buttons to apps, and file management enhancements. 2. Customization and UI Enhancements (The "Skinning" Era)
WM6’s killer feature was Direct Push Technology via Exchange Server 2007. Applications like Outlook Mobile (Email, Calendar, Contacts) and Office Mobile (Word, Excel, PowerPoint viewers/editors) were preinstalled. Third-party apps included terminal emulators (for mainframe access), SAP/Microsoft Dynamics mobile clients, and custom line-of-business (LOB) data entry apps using SQL Server Compact Edition.
When designing a feature for WM6, you can leverage several built-in system capabilities: Today Screen Integration
The Golden Era of Pocket Computing: A Deep Dive into Windows Mobile 6 Apps
The .NET CF was a subset of the full desktop .NET Framework. It provided garbage collection, a forms designer (Windows Forms, not WPF), and controls optimized for 240x320 or 480x640 pixel screens. However, performance was often a concern; graphics-heavy apps frequently fell back to native C++.
: A popular, lightweight alternative for handling complex PDF documents. Internet & Communication
WM6’s UI was designed for a . Buttons, scroll bars, and menu items were small (typically 20-24 pixels), making finger operation frustrating. The "Today Screen" displayed upcoming appointments, unread emails, and tasks—optimized for glanceability rather than deep engagement.
Before WhatsApp, there was . For many users, this was the primary way to stay connected. Additionally, Skype for Windows Mobile allowed for early VoIP calling, saving users significant money on international minutes—provided they were near a rare (at the time) Wi-Fi hotspot. 3. Web Browsing: Opera Mobile vs. Internet Explorer
In the days before iMessage and WhatsApp, these apps were essential for staying in touch with friends and colleagues.
Windows Mobile 6 offered APIs and development tools that leveraged Microsoft’s strong developer ecosystem. Developers used Visual Studio and the .NET Compact Framework to create managed applications in C#, or native C/C++ for performance-critical tasks. The Microsoft Mobile Internet Toolkit and SDKs provided emulators, sample code, and debugging tools, lowering barriers for enterprise developers already familiar with Windows development. This compatibility encouraged porting of desktop utilities and enterprise applications to handheld devices.