• 0

Heading Back to 2005 - Widget Apps?


Question

Are there any small widget apps out there that are still supported?

This all started when I had the Spotify app showing me what was currently playing on the right hand side of the window.

I then thought it would be nice to have a little widget on the desktop to show me this as I have two screens so can afford to waste some space on the desktop.  Updated the app and then the right hand panel disappeared - turns out it's experimental but now I've updated, I can't get it back.

Found that Windows 11 has it's own widget system but it's rubbish as all the widgets are in a little flyout thing that opens and closes.  The spotify widget just wants me to play whatever instead of showing me nice album art and stuff, so that's a shame.

I discovered I can press WINDOWS KEY + G and it'll open up a little thing where I can "pin" widgets but it's not that nice.

I don't really want to install another program but if there is one that plays nicely with Spotify then I may be convinced.

Cheers

Link to comment
https://www.neowin.net/forum/topic/1430119-heading-back-to-2005-widget-apps/
Share on other sites

5 answers to this question

Recommended Posts

  • 0
On 09/06/2023 at 15:35, Nick H. said:

I think Rainmeter would do this?

I just took a quick look and found this Spotify Player Rainmeter Skin.

That skin doesn't work any more.

I don't think it's possible any more.  Shame really but I might take a look at Rainmeter again and see if there's anything else I may use.

  • 0
On 27/06/2023 at 08:39, Sir Topham Hatt said:

That skin doesn't work any more.

I don't think it's possible any more.  Shame really but I might take a look at Rainmeter again and see if there's anything else I may use.

Well that was just supposed to be an example anyway.

I've taken another look and it seems that Spotify support can be a bit iffy. But I would still think that Rainmeter is the best way to achieve this, and it comes with plenty of other options for desktop items as well!

  • 0
On 09/06/2023 at 07:31, Sir Topham Hatt said:

I then thought it would be nice to have a little widget on the desktop to show me this as I have two screens so can afford to waste some space on the desktop.  Updated the app and then the right hand panel disappeared - turns out it's experimental but now I've updated, I can't get it back.

Emphasis mine ^

This.  This is completely lost on Microsoft.  Widgets shined in the era of big monitors (which still exist) and using that extra space.  Nowadays, regretfully, they seem to think that you're maximizing your screens or using your huge screens in a perfectly split window instead of, you know, having windows.

Except of course for the weather which they'll happily put on the taskbar.  But that's literally the only app they allow at-a-glance.  Everything else - all other widgets - are effectively "launched" by opening the panel.  If I wanted to "launch" something, I'd launch the app that gives me all the information.

Omnipresent minimalistic information is good, and should be a user choice.  I thought Rainmeter did this.  I also thought I heard something that said MS was considering or doing this in an upcoming release.  I mean honestly, Microsoft, what the frick is a desktop for?  If it's not to place information or data, then have all apps go through start or file manager.  Putting data on the desktop should be a user choice.  Widgets are a UX problem not a design problem -- it's almost like having a car but only being able to park it at your destination, which you constantly have to walk to.  There's just no point to minimal information when it's not at-a-glance.

Gee, do I launch the app that shows me some of the weather, or launch the app that shows me all of the weather?
Gee, do I launch the app that shows me some of the stocks, or launch the app that shows me full stock info?

The key difference is the user effort - you have to perform an action to get the data instead of just looking at that spot on your taskbar or widget that is omnipresent.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Waymo recalls self-driving software after cars enter closed freeway work zones by Paul Hill Waymo, the self-driving car maker owned by Alphabet – the parent company of Google –, has recalled some of its fifth-generation Automated Driving Systems (ADS). It did so after some of its cars drove through closed construction zones. According to the National Highway Traffic Safety Administration (NHTSA), the affected vehicles were capable of driving through a closed freeway construction zone and continuing to drive at speed. The listing on the NHTSA website says that Waymo is currently developing a solution to fix this issue, but in the meantime, freeway driving is being restricted. Waymo will update its ADS software so that vehicles can detect when they can avoid entering construction zones. According to the Safety Recall Report, on April 20, 2026, Waymo’s Field Safety Committee began meetings reviewing an event from April 11, 2026, and five events from April 19, 2026, where Waymo’s autonomous vehicles didn’t recognize and drove past ramp closure signs into the pre-planned freeway construction zones. This took place in Phoenix, Arizona. Separately, on May 18, 2026, seven Waymo vehicles entered freeway lanes with active construction in the San Francisco Bay Area by driving between cones that were placed to show the lane was closed. On the back of both of these events, Waymo restricted freeway driving until it could address the issue. In June, Waymo’s Safety Board reviewed the issue and additional information related to ADS performances around construction zones; then, as a result, it decided to conduct a recall. This development is not good for Waymo as it adds to a growing list of technical hiccups its cars have experienced. Ultimately, it will lead to more scrutiny from lawmakers around the world who will be more cautious about letting autonomous vehicles on their roads without tighter regulation. For readers in areas where Waymo operates, does this news make you more wary about stepping into one of these vehicles?
    • 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.
  • 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
      598
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      80
    4. 4
      Michael Scrip
      76
    5. 5
      Steven P.
      69
  • Tell a friend

    Love Neowin? Tell a friend!