Apple Rumours floating about...Nano Redesign, iPod Touch...


Recommended Posts

gizmodo_logo-300x85.png

New iPod Nano Mock-up Takes the Sting Out of the New iPod Nano

1:50 PM on Wed Aug 27 2008 By Mark Wilson

nanoidea2.jpg

I can't speak for everyone in the room, but I'm not all that excited about the possibility of the iPod nano returning to its long, skinny origins. Originally repulsed by the latest iteration of nano, the deformed, squat body won me over the first time I actually held it in my hand. And it instantly made the styling of its thin predecessor seem like a vanity device?a lipstick-like accessory, not something designed to easily play my music. Anyway, these concept mock-ups by flickr's Umpa reminded me that skinny is still pretty hot. Widen the screen a tad and I might be sold, again. Bonus shot:

nanoidea1.jpg

You see, putting Wall-E on the screen makes the concept oh so much more convincing. And adorable.
@The mockups

The clickwheel magically turns with the iPod? :p lol

I was wondering the same thing as well...

(and that change from Neowave to .Neo was easy to notice, but from .Neo to .Reo while changing your avatar and your sig... it took me a while :p)

And now, with all these mockups and covers, there's no more reason to call it a rumour.

I mean, who would lose its time to do a mod to an older iPod, then create covers, or to photoshop so many pictures?

I'm not saying all these informations are true, like that strange iPhone interface fitted in an iPod nano, but the physical design of the device has to be true.

Am I the only person who loves the nano 3G? I hated the long, skinny design. I just find the shorter, wider version to be much more comfortable, at least just for me.

Also, someone brought this up on MacRumors... Rarely, if ever, does Apple replace one gen with another one based on an old design. Yes, the materials change from time to time, but not usually the overall design. It seems like Apple clearly wants the nano to have an even larger screen than what it has now. Couldn't they accomplish this by simply making the screen larger on the current design, and either move the click wheel to the back (un-Apple like) or make it software based? (More like the touch.)

Am I the only person who loves the nano 3G? I hated the long, skinny design. I just find the shorter, wider version to be much more comfortable, at least just for me.

No, you're not alone :p although I admit that these mockups on the previous page look hot, even for a long and skinny iPod.

I know technology moves fast, but I hate it when Apple release their iPod lineup so fast. It's buggy as hell when first release. Takes a few months for updates to be release & maybe finally it's running good. Then boom! Another iPod. Same can be said about iPod accessories. You wait months later to get a great case or any accessory. Boom! Another iPod that will only work with whatever new is coming out later. And it won't work with the older iPods.

I give Jobs a lot of credit for being great at marketing. They get everyone so giddy up for that "day" that people will automatically jump on & buy whatever they release. Bugs or not. Cool or not. Keep this up, they can release new iPods every 6 months & make even more money.

I know I don't have to buy every new iPod & Apple is a business and all. But that's just greed. Get your act together Jobs.

Edited by Lqv2015

What was so fast?

It's been a year now, and I think they'll go for new iPods every year, starting... last year.

If they had to make a new iPod every 2 years, they wouldn't follow the market, thus they would be incompetitive.

By releasing ipods every year they can update the design, make the hard drive or whatever bigger, change the components to make it environment-friendly, change the firmware, and create a new marketing buzz on the release day and on the next few days.

The last point is a good reason to release it every 12 months for them IMO. The other points are good enough for us.

There are bugs on ipods? :p

No seriously, what have you encountered?

Also, when you encounter something, it is always better if you tell Apple, if it isn't fixed, it's probably because they missed it.

Owners of the iPhone & touch knows what I'm talking about. Ever since I've upgraded to 2.0, nothing but crashes. 2.0.2 is out & it's still the same.

Owners of the iPhone & touch knows what I'm talking about. Ever since I've upgraded to 2.0, nothing but crashes. 2.0.2 is out & it's still the same.

That's a software issue which they are actively working on. iPhone OS 2.1 is coming out next month.

Oh yeah, if you're talking about iTouch and iPhone, I've got one and I know what you mean. But they ARE working on a 2.1 firmware and you've got to admit that this firmware is actually a complete OS, thus it must be quite big, quite hard to develop, and contain a couple of hundred thousands of lines of code, if not millions.

As for the iPod nanos, iPod classics, and iPod shuffles, they're pretty much flawless according to me. Either people don't know how to use it, or they received a lemon, which they have to replace in store.

My old iPod Nano 2G only crashed on me once, which caused me to lose my music. Aside from that, it worked beautifully.

As for this upcoming one, I hope they do return to that long, skinny form factor, as the 3G version was just butt ugly! :D

man i always love these rumor-threats on neowin. seriously. =)

however, i never cared too much for the nano eversince i bought an ipod g5 to replace my 4gb ipod mini, which i loved (i had the rare gold one, it was rare in germany at least!) but always felt restricted because of the space...

i love how apple releases new ipods every year. i mean i bought mine in early... lets see... 2006 or 2005, i dont remember and i never felt the need to update. just buy one, sit back and watch technology evolve. and at the time you see the need for a replacement... go for it. and then again, sit down, relax and watch technology go its way. =)

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

    • No registered users viewing this page.
  • Posts

    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • And with SO much better perf than the laggy mess that is Files.
    • BrowserOS 0.46.0 by Razvan Serea BrowserOS is a free, open-source Chromium-based browser that runs AI agents natively, offering a smarter, more productive browsing experience. It supports Chrome extensions and integrates AI agents to automate tasks, fill forms, and streamline workflows. Your data stays on your computer: you can use your own API keys or run local models via Ollama, making it a privacy-first alternative to tools like Perplexity, Comet, or Dia. With built-in productivity tools and app integrations, BrowserOS boosts efficiency while keeping control firmly in your hands. Being Chromium-based, BrowserOS lets you effortlessly import your bookmarks, passwords, and Chrome extensions in just a few clicks. BrowserOS works with OpenAI GPT models, Anthropic Claude, Google Gemini, and local AI models via Ollama or LMStudio. You can use your own API keys and effortlessly switch between providers. BrowserOS Agent Your AI productivity assistant that organizes and manages your browsing effortlessly Quickly list, group, or close tabs Save and resume browsing sessions Search your history and organize bookmarks Switch instantly to the tab you need BrowserOS Navigator – Automate web tasks with ease Navigate websites and search automatically Interact with pages without manual effort Handle repetitive tasks in seconds What makes BrowserOS special Feels like home - same familiar interface as Google Chrome, works with all your extensions AI agents that run on YOUR browser, not in the cloud Privacy first - bring your own keys or use local models with Ollama. Your browsing history stays on your computer Open source and community driven - see exactly what's happening under the hood MCP store to one-click install popular MCPs and use them directly in the browser bar (coming soon) Built-in AI ad blocker that works across more scenarios! BrowserOS 0.46.0 changelog: Run Claude Code & Codex right in your browser — We've extended the agent harness to bring full coding agents into BrowserOS. Claude Code and Codex now come bundled and plug straight into the assistant, so you can drive your browser with the agent — and the subscription — you already use. A brand new experience — A redesigned new tab, a calmer composer, and a rebuilt command center for switching between agents. The whole assistant is cleaner, faster to reach, and easier to live in. New MCP tools — We rebuilt the browser tool surface from the ground up — a tighter, more reliable set of tools for agents to drive the browser. Plus one-click install of BrowserOS as an MCP server into the agents you already run, with automatic URL sync. Chromium 148 — Updated to the latest Chromium base with all recent upstream fixes and security patches. Streamlined — We've pulled back a few features that weren't getting much use — Skills, Soul, and Memory — so we can focus and ship better versions of them soon. Download: BrowserOS 0.46.0 | 181.0 MB (Open Source) Download: BrowserOS for macOS | 485.0 MB Links: BrowserOS Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • First Post
      BizSAR earned a badge
      First Post
    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      596
    2. 2
      +Edouard
      188
    3. 3
      PsYcHoKiLLa
      80
    4. 4
      Michael Scrip
      76
    5. 5
      Steven P.
      67
  • Tell a friend

    Love Neowin? Tell a friend!