Introduction The current iteration of dynamic weather wallpapers, while functional, has become visually stagnant. With the rapid advancement of Generative AI, there is a significant opportunity to transform these backgrounds from simple realistic simulations into dynamic, artistic experiences. The Core Concept The proposal is to replace or supplement standard weather backgrounds with AI-generated Vector Art that evolves in real-time. Instead of a static image, the wallpaper would be a living piece of art that adapts to: Local Time: Seamlessly transitioning from dawn's golden hues to midnight’s deep blues. Weather Conditions: Using distinct vector animations for rain, thunderstorms, or heatwaves. Location-Specific Context: Incorporating stylized vector landmarks of the user's current city. Key Features Artistic Variation: Users could choose from various styles, such as Minimalist, Flat Design, Isometric, or Cyberpunk, making the phone interface feel like a curated gallery. Information at a Glance: The vector elements themselves could convey data. For example, the intensity of "wind" animations could reflect actual wind speeds, or the "sun's" position could represent the actual UV index. Emotional Connection: Unlike realistic photos, vector art provides a "vibe" that is less cluttered and more visually soothing, improving the overall user experience and aesthetics of the Lock Screen. Conclusion Integrating AI-driven vector animations would make the Weather Wallpaper not just a tool, but a signature design feature. It would bridge the gap between utility and art, making every glance at the phone a unique experience.

I have made a screensaver for mac in swift, but couldn't find how to add an icon the logo image that shows up on saver file) and thumbnail (the cover image that shows up in the screensaver catalogue). Currently, it just shows a default blue spiral galaxy thumbnail and no icon image

The title says it all, and I've filed FB FB22353950 that includes an Xcode 26.4 Screen Saver test project, QT movie demonstrating the error, and a PDF with complete steps to build and test. I'm asking here just to learn if this sounds familiar. The SS built on 26.4 fails in 26.4, works fine on 26.3.1. I'll supply the test files if there's interest. Thanks.

I have a .saver file. I want to sell it. Apparently, Guideline 2.4.5(ii) states that apps “cannot install code or resources in shared locations”. Can I sell a disk image that has the .saver file and instructions to the user to double-click it? Are there any other ways of doing this? Thank you, —bc

Noticing a few issues with Screen Savers in macOS Tahoe developer beta 1 : The command open x-apple.systempreferences:com.apple.ScreenSaver-Settings.extension no longer works to open the Screen Savers preference pane. The reason? There is no longer a Screen Saver preference pane - it still exists, but it's now a Modal dialog (that can not be resized) that is opened from within the Wallpaper preference pane, by clicking a button. Something funny is happening with legacyScreensaver - I think that ScreenSaverView.Init(frame:isPreview) may be passing wrong values, e.g. the isPreview boolean is false in Preview mode? I've submitted Feedback # FB17895600 about some of these, and will report back more as I figure things out. Please feel free to add to this thread, thanks!

Since legacyScreenSaver is still the thing running screensavers we make, and it's still buggy, why won't they give us a new template for building screensavers that run in the new engine? And hopefully they don't require them to blend in with the desktop, because most of us don't want that. A wallpaper is a wallpaper, and a screensaver is a screensaver.

If the Safari Technology Preview window is located on an external monitor with DisplayLink and the computer goes to sleep (screen saver), when it returns, it closes with an error. If the window is located on another monitor that is connected by USB, it does not close. Equipo: Macbook Pro M4 Pro SO: MacOS Sequoia 15.6.1 Safari Technology Preview: Release 227 (preview version work fine) DisplayLink Manager: 13.0.1 (build 46)

I haven't been looking at screensavers for a long time because of Apple's lack of will (or resources?) to provide a public version of the private modern SDK used by Apple for a very long time now. I'm now looking at the Screen Saver pane in System Settings (the What-If version of System Preferences in an alternate universe where all screens are in portrait mode). In macOS Sequoia, it seems like 3rd party screensavers are not welcome considering that they are relegated to the "Other" section at the bottom of the list and you have to click Show All to start seeing 3rd party screen savers. I also had a quick look at macOS Tahoe Beta 3 and it looks like that all the real screensavers are gone (3rd party and the ones from Apple: Hello, Message, Flurry, etc.) or at least it requires to be a Nobel Prize to find them (and the Search field is not useful). I tried to install a 3rd party screen saver on macOS Tahoe Beta 3, it doesn't show up in the list. To summarize: No public access to modern APIs AFAIK. UI that is hostile to 3rd party screen savers on macOS Sequoia. Apparently only screensavers that are slideshows or movies curated by Apple in macOS Tahoe b3. Hence the question: Is there any future for screen savers on macOS? Because if there's none, I won't waste my time trying to update some old screen savers.

Hey all, I’m experiencing a consistent issue with notarizing a signed .pkg file that contains a macOS screen saver (.saver) bundle. Nothing online so far except 1 thread on the form from the altool time pre-2023 so i thought it worth another update. Here is what I did: I signed the .saver bundle using my Developer ID Application certificate. I packaged it into a .pkg using pkgbuild with my Developer ID Installer certificate: I submitted the resulting .pkg via xcrun notarytool: xcrun notarytool submit saver-name.pkg --apple-id email@email.com --password [app-specific-password] --team-id xxxxxxxxx The submission appears to be accepted and uploads successfully. However, the notarization status remains stuck at “In Progress” for hours (over 12h), with no update. I also tried: Repackaging the .pkg with a new name using a zip Resubmitting it under a new submission ID All attempts are stuck in the same “In Progress” state indefinitely. Did anyone solve this yet?

Hello, Im am running Sequoia 15.2 beta. When my screensaver starts en i move my mouse the screen turns black and i only see my mouse pointer. Further nothing happens and i need to force reboot my macbook pro m1. Is this a familiar issue or does any one know what to do in this case? Kind regards, Martin

I want to be able to write a cross-platform screensaver that works on both Windows and macOS using the Pygame 2D graphics library in Python. On Windows, this is super easy - you just write your program with three possible command line arguments: /p for preview mode, /c for the configuration dialog mode, and /s for the actual full-screen screensaver mode. Then you just use pyinstaller to build an .exe file and rename the extension to .scr, and you're good to go. However, it seems that making a screensaver on macOS is a pretty convoluted process, and there was stuff about specific Objective-C functions that you had to write, and I didn't really understand the documentation. Could you please tell me if there is any way to simply get my Python Pygame program to build as a proper .saver file? Thanks!

I'm developing a ScreenSaverView which uses WKWebview internally. This screensaver responsds to mouse events, and I'm using a helper app which is granted Accessibility permissions to watch mouseEvents and then serializes them to the Screen Saver, where they are recreated and send to the WKWebView. This all works fine - the WKWebView can respond to mouseDown, mouseUp, MouseDrag, scrollWheel (etc.) events. The one exception is that mouseMoved events are ignored. I see a similar issue posted here: https://stackoverflow.com/questions/17057254/when-webview-is-added-to-a-specific-view-in-nswindow-hover-stops-working-how?rq=2 but that's from 2016 so not sure if it's relevant. Things I've tried: adding a NSTrackingArea to the WKWebView setting the parent NSWindow.acceptsMouseEvents = true

Okay so in one of the new IOS 18 Beta’s you can select a specific wallpaper genre that has to do with Planets (Earth, Mars, Saturn, ex.). There is one called “Earth Detail” where it zooms in and when you open your iPhone it will do a pulse of a green circle (showing where you are in the world) pretty cool feature. In “Earth Detail” you can also see the clouds and all the lights during the night, but what if you could see the northern lights at that specific time when they are visible in the sky? I think this would be a minor feature but a cool little easter egg to have. Let me know what you guys think of this. Thanks!

I've run into a really weird bug with a macOS screen saver I've been developing using the ScreenSaver framework. It works fine on Ventura, but on Sonoma, when the user dismisses the screensaver, it continues to animate invisibly in the background using up CPU and GPU cycles. Even worse, when the user activates the screensaver a second time, yet another copy appears to be created, and so on. The call to stop animating is also never sent to the view, as far as I can tell. I logged this as FB13041503 already, but I'm trying to come up with a workaround now, since this is still happening in the release version of macOS 14.0. Any ideas how I can detect that the screensaver has been dismissed, so I can minimise my resource usage? I've even tried watching for things like NSWindowDidChangeOcclusionStateNotification but nothing seems to get called that I can use.

Hello everyone, I am reaching out to you today regarding an issue I am encountering with a customer who owns an iPhone 15 Pro. The customer purchased a new screen protector for the device, but there is a problem with the fit of the protector in the corners of the screen. The protector does not adhere properly to the corners, and there is a small gap between the protector and the screen. As a result, there is a concern about damage to the screen in the event of a drop or bump. I have tried several possible solutions, such as thoroughly cleaning the screen and protector before installation, but the problem persists. Do you have any recommendations or possible solutions for this issue? I would appreciate any help you can provide in resolving the problem for the customer.

Hi all, I've been playing around with making a screen saver using ScreenSaver.framework and having issues with (what appears to be) macOS caching the previous version of the screensaver until I reboot. I have written a screen saver that works, however if I make some changes to the code, re-archive and reinstall the newly compiled screen saver still presents the old screen saver. I've tried incrementing the build number to no avail. Does anyone have a solution to this? My workflow :- Uninstall and delete all instances of my screen saver. Reboot Open Xcode, compile, re-archive my screen saver. Double-click the archived screen-saver, click to install for this user. Test screensaver -- success! Now, Delete the screensaver by right-click on screensaver in System Settings, "Delete " Make changes to my code, rearchive. Double-click the archived screen-saver, click to install for this user. Test screensaver -- fail! Still shows the old version of the screensaver. Reboot machine Test screensaver -- success! Screensaver now shows the changes I made. Many thanks all.

The BOINC installer asks the user if they would like to set BOINC as their screensaver. If they answer yes, it sets it for them. Both of the following methods work under Ventura and earlier, but no longer work under MacOS 14.0 Sonoma. Applescript: tell application "System Events" to set current screen saver to screen saver "BOINCSaver" Shell script: defaults -currentHost write com.apple.screensaver moduleDict -dict moduleName "BOINCSaver" path "/Library/Screen Savers/BOINCSaver.saver" type 0 The defaults method also worked under Ventura and earlier by passing the corresponding CFMutableDictionaryRef to CFPreferencesSetValue. What is the way to set a screensaver for all spaces and displays under Sonoma?

How to disable the screensaver when I running my iPad app onto m1 macbook programmatically? Especially in video playing case I mean that how to disable screen in my ios code or project Thanks

Hey @eskimo or anybody who can help, we are on 14.0 beta 7 and screensaver bugs with Sonoma are still happening. In this case the bug shows up one or more monitors, for screensavers that use WKWebView internally. The WKWebView will render HTML and JavaScript, but only partially: video tags don't play unless you goose them with a hack JavaScript SetAnimationFrame() fails JavaScript SetInterval() only fires about once per second These issues affect many third-party screensavers which internally use a HTML/CSS/Javascipt engine. reported as FB13094564 There are a bunch of other legacyScreenSaver issues with Sonoma that aren't WebKit-related as well, but most of those we have been able to find workarounds for. Thanks!

Hey @eskmio or anybody who can help, we are on 13.3 RC and this multimonitor screensaver bug is still happening. It's affecting most (but not all) screensavers when run on a 2+ monitor system. Relevant discussions: https://forums.macrumors.com/threads/macos-13-3-rc-bug-fixes-changes-and-more.2384357/post-32056536 https://forums.macrumors.com/threads/multimonitor-screensaver-bug-in-ventura-13-3.2384444/ https://iscreensaver.com/forum/discussion/568/ventura-13-3-beta-bug-with-multimonitor-screensavers https://github.com/JohnCoates/Aerial/issues/1286