Neowin Survey - Neowin mobile, what device do you use?


What device would you use for Neowin Mobile?  

533 members have voted

  1. 1. Device choices:

    • iPhone / iPod Touch / Android / Palm Pre
      272
    • Blackberry
      52
    • Nokia S60 based device
      54
    • Windows Mobile 6.5
      81
    • Other (Please Specify)
      74


Recommended Posts

In the past I always used my Blackberry (Pearl) which was a huge hassle before the mobile site came online. Even with that, the Blackberry has never been that easy to use Neowin on. I just won an iPod touch three weeks ago so I plan on using that more often to visit Neowin while I'm out and about.

Pre listed next to Safari browsers? Is Pre Browser powered by webkit? Also the Pre browser only scores 1/100 on the Acid 3 test so far from standards compliant. I'm not bashing the Pre I'm just pointing out it may need to be coded slightly differently.

Pre listed next to Safari browsers? Is Pre Browser powered by webkit? Also the Pre browser only scores 1/100 on the Acid 3 test so far from standards compliant. I'm not bashing the Pre I'm just pointing out it may need to be coded slightly differently.

It is based on WebKit, and in our tests it rendered the same as the iPhone. Acid3 can be a finicky test - point is, the Palm Pre browser is, for all intensive purposes, the same as the Android and iPhone/iPod touch browsers.

I don't have a Pre myself (iPhone user), but it is my understanding that it definitely uses webkit in one form or another.

It is based on WebKit, and in our tests it rendered the same as the iPhone. Acid3 can be a finicky test - point is, the Palm Pre browser is, for all intensive purposes, the same as the Android and iPhone/iPod touch browsers.

I don't have a Pre myself (iPhone user), but it is my understanding that it definitely uses webkit in one form or another.

10ic3t2.png

I'm always changing my mobile phone and i would like to access Neowin on each device without any limitations. No matter what size of screen the device has it should be able to display Neowin regardless.

At the moment i have a Nokia 5800, which was upgraded from a Nokia 6500s, Nokia N91, XDA Argon, Blackberry Curve 8320 and i'm looking to change to the Nokia N97 in the next few weeks.

Out of those devices not many have a decent size screen but you should be able to view Neowin regardless.

None. I believe sites should be viewed as full and I HATE when a site forces you to view their mobile version without giving a option to view as the full version.

Its seems Neowin will still give that option so thank you :)

You find it much easier to navigate and hell of a lot quicker to load viewing a full HTML page such as Neowin on a mobile device?

kdog.png

Kanye is correct. Currently it's a bitch to browse Neowin in a CLI, so assuming the mobile webpages are going to be as lean and clean as possible, I assume that they are possibly CLIable. And thus, I humbly propose adding the user agents of ELinks, Lynx, w3m into this list of mobile devices.

Well hey, guys, grouping the Palm Pre, Android, and the iPhone together? What do you think is going to get more votes here?

I say Windows Mobile 6.5. I plan on making a Touch Pro2 my next device, and a client like that would be really nice to have. As of now, I'm relying on Opera Mini and Bolt to get my news on the go.

You find it much easier to navigate and hell of a lot quicker to load viewing a full HTML page such as Neowin on a mobile device?

Yes.

kdog.png

I dont know if you made the image but whoever made it misquoted him, made it unfunny and problably killed a future internet meme....

I'm always changing my mobile phone and i would like to access Neowin on each device without any limitations. No matter what size of screen the device has it should be able to display Neowin regardless.

At the moment i have a Nokia 5800, which was upgraded from a Nokia 6500s, Nokia N91, XDA Argon, Blackberry Curve 8320 and i'm looking to change to the Nokia N97 in the next few weeks.

Out of those devices not many have a decent size screen but you should be able to view Neowin regardless.

That's all very nice but we won't be supporting every device. It's not as simple as "no matter what size of screen".

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • The fact that memory in general is so high I have to take a loan out to build a computer now is just beyond stupid. Who's really to blame here? Low supply or high demand?
    • Display Driver Uninstaller (DDU) 18.1.5.5 by Razvan Serea Display Driver Uninstaller (DDU) is a utility for completely removing AMD/NVIDIA/INTEL graphics drivers and related packages from your system, attempting to eliminate all leftovers (including registry entries, folders and files, driver store). Though AMD/NVIDIA/INTEL drivers can usually be removed via the Windows Control Panel, this uninstaller tool was created for situations where standard uninstall fails, or when you need to fully remove NVIDIA or ATI graphics card drivers. After using this driver cleaner, your system will behave as though it’s the first time you’re installing a new driver—similar to a fresh Windows installation. As with all such tools, we recommend creating a restore point beforehand, allowing you to undo changes if issues arise. If you're having trouble installing an older or newer driver, try it—there are reports that it resolves such problems. Recommended usage: The tool can be used in Normal mode but for absolute stability when using DDU, Safemode is always the best. Make a backup or a system restore (but it should normally be pretty safe). It is best to exclude the DDU folder completely from any security software to avoid issues. You do NOT need to uninstall the driver prior using DDU. Requirements: .NET Framework 4.8 Compatible with Windows 7, 8, 8.1, 10, and 11 (32-bit or 64-bit) Note: Using on Insider Preview builds is at your own risk. Display Driver Uninstaller (DDU) 18.1.5.5 changelog: Added 'Reset to recommended' button for the Options. General fixes and improvements. Download: Display Driver Uninstaller (DDU) 18.1.5.5 | 1.7 MB (Freeware) Download: DDU Portable | 1.2 MB Links: Display Driver Uninstaller Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • WACUP 1.99.51.24568 Preview by Razvan Serea WACUP (WinAmp Community Update Project) is a modern, enhanced version of the classic Winamp music player, designed for better stability, performance, and compatibility. Built for Windows, WACUP retains the familiar Winamp interface while adding 64-bit support, bug fixes, and new features like improved audio format support, customizable skins, and optimized playlist management. Unlike bloated alternatives, WACUP focuses on lightweight performance and regular updates, making it the best choice for fans of the classic Winamp experience. Basically, if you miss the good old days of Winamp and want a modern upgrade that doesn’t mess things up, WACUP is for you! WACUP key features: Classic Winamp Feel – Keeps the familiar interface and functionality. Bug Fixes & Stability – Fixes old Winamp issues and improves performance. 64-Bit Support – Works better on modern systems. More Formats & Plugins – Supports additional audio formats and third-party plugins. Customizable UI – Skins and tweaks for a personalized look. Better Library Management – Improved playlists, media organization, and search. No Bloat – Focuses on performance without unnecessary extras. Regular Updates – Community-driven development with new features and fixes. WACUP 1.99.51.24568 Preview changelog: Fixed a deadlock seen from the recent crash reports when doing some of the drag + drop actions within the media library window Fixed a loading crash seen related to a problem with some of the artwork cache image files being restored which should now be better handled allowing for the bad image to be removed without it failing Fixed a deadlock seen from the recent crash reports when the internal metadata cache clearing is triggered which could block the main ui thread for too long with this now being moved to a background thread Fixed some performance issues with some of the methods related to determining artwork support which mainly affected the local library import / refresh (this is still slower for some compared to other players because there's more data & artwork aspects being checked for which means doing more processing on a single file despite the best of attempts to reduce duplicate / heavy processing where possible) Fixed a crash with the JTFE based missing files hotkey which no one seems to have used for an age for this to appear (maybe it's time to seriously consider stripping out features that aren't being used) Fixed how some of the file types which use extra information to reference their sub-songs is handled which was preventing some from being correctly resolved back to their base file (noticed fixing above) Fixed an issue with the handling of files with underscores in their filepath which wasn't being correctly handled causing some of the filename to be lost when shown as the title if title reading is delayed Fixed a few things that might be behind NotSoDirect not being stable for some setups though am still not certain that the changes done for this are going to fully resolve the problem from the crash reports Fixed the OS toast handling when there's no prior shortcut in the OS start menu to now create the shortcut (needed to allow the yes/no buttons for the new build / post-release toast) to be done as a hidden one so it's less likely to cause annoyance for those not wanting to see it whilst still allowing this less than ideal OS api implementation requirement to be met to avoid toasts without the needed buttons Fixed a regression when moving from taglib1 to taglib2 which broke some of the handling in place to allow for external programs to still access files when wacup has a held open cached instance of the file Everything else Updated cppwinrt (gen_win10shell.dll) to 3.0.260520.1 (26 May 2026) Updated libcurl (libcurl.dll) to 8.2.1 (24 Jun 2026) Updated Monkey's Audio (in_ape.dll) to 13.15 (28 Jun 2026) Updated mpg123 (mpg123.dll) to 1.33.6 (6 Jun 2026) Updated OpenSSL (libcurl.dll) to 3.5.7 (9 Jun 2026) Updated pugixml to 1.16 (16 Jun 2026) Updated taglib (tag2.dll) to 2.3.0 (11 May 2026) Updated vgmstream (in_vgmstream.dll) to the latest Git commit from 28 Jun 2026 Download: WACUP 64-bit | 9.6 MB (Freeware) Download: WACUP 32-bit View: WACUP Website | Screenshots Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • "over a thousand engineering hours" and started selling it but could not take a couple of minuets to send an AI email to ask permission. What an expensive lesson.
    • just tested it yesterday, a simple page with autoloading ADS takes 60mb....just 1 page for 60 megabytes.   poor people with a limited internet never will visit neolose
  • Recent Achievements

    • Week One Done
      Collagen Project earned a badge
      Week One Done
    • Reacting Well
      Wakeen1966 earned a badge
      Reacting Well
    • Rookie
      Almohandis went up a rank
      Rookie
    • Apprentice
      jahara21 went up a rank
      Apprentice
    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      526
    2. 2
      +Edouard
      265
    3. 3
      PsYcHoKiLLa
      146
    4. 4
      Steven P.
      99
    5. 5
      macoman
      55
  • Tell a friend

    Love Neowin? Tell a friend!