Does Apple need to introduce Widgets for iOS?


iOS and Widgets  

151 members have voted

  1. 1. Should widgets be added to iOS?

    • Yes!!
      78
    • No!!
      24
    • Don't care, next!
      49


Recommended Posts

Let's face it, Apple users are going to say widgets are unnecessary, and some might say that if Apple does introduce them, they'll do it better and it'll be useful to the people who wants to use them, which of course is not them. and when Apple does make them, they will go all out on how awesome widgets are on iOS :)

I don't know if Apple will add them, but I would suspect they will, they're feeling the competition, and people want easy informative widgets with the information right there. Android has it, WP7 has it built in even better, and in a way that doesn't add battery eating costs. Apple needs to eventually add them to compete. The wall of icons just doesn't work.

  • Like 8

I'm not sure if I want or need widgets.

If this does come at WWDC as part of iOS5 it is most likely just something to keep us happy to the iPhone 5 comes out, if it doesn't come out at WWDC.

Guess they come be handy for news apps and the likes of twitter apps, so I don't have to unlock my phone everytime I want to see the latest updates.

They wont call them widgets though, get ready for iWidge. New and revolutionary.

This won't happen, they'll just be called widgets, why? That's what they're called on the Dashboard.

To be honest, they don't need to introduce them, they can if they really want to, but they're not a crucial feature, especially not over a redesigned and improved notification system.

They wont call them widgets though, get ready for iWidge. New and revolutionary.

Other than your poor attempt at trolling, why wouldn't they call them widgets? They already use the term for Dashboard on OS X.

Added a poll to see what the general concensus is around these parts. :)

Ooh, very fancy. Thanks :)

Other than your poor attempt at trolling, why wouldn't they call them widgets? They already use the term for Dashboard on OS X.

It was a joke... no need to get your Apple defence gear on so quickly.

Well, they have built in widgets for OS X, so I would imagine the same thing will make it for iOS. I don't use them in OS X, I find them rather pointless. But I might find myself using them for iOS. Who knows if they will be in iOS 5... the only thing that is more-or-less safe to bet money on is a new notifications system.

I don't think Apple needs widgets in iOS 5 to keep selling i-hardware. I suspect that it is one of the lower features on a persons priority list when spec'ing out a phone... could be wrong though.

One of the main arguments for me to switch to Android a while back was widgets. Turns out I deleted them all after a while. So no, I don't need them. Put them in there, sure, why not, I for myself won't use them though.

I have never really felt like I needed them on my iPad. I honestly have never used it and said to myself more then once "I wish I had a widget" and the one and only thing that made me say that was the weather. Then again I just do not really utilize them on any of my desktops or my Droid phone, minus the weather one on my Droid, so I am just not a big widget user.

I hope they just steal the Android system, the pull down tray is just great. They'll have to call it iNotif though, and remember its magical and revolutionary ;)

Android is not perfect though, everything is pooled together. It can definitely be improved (but Android still is miles better than WP7 or iOS).

Once Mango hits I think then Mango>iOS. The widgets thing is nice, live tiles is good (its a middle ground between widgets and the iOS notifications or at least it feels that way) even though I am not happy about my WP7 I am happy I offloaded my iPhone as I was becoming bored. Think I will get an android next.

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

    • No registered users viewing this page.
  • Posts

    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
    • VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Too soon, I'm still not over this death!
  • Recent Achievements

    • 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
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      593
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      77
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!