Explore
News Explorer
Browse every article collected by VIREXA. Newest articles appear first.
6,933 results • Page 511 of 578
Explore
Browse every article collected by VIREXA. Newest articles appear first.
6,933 results • Page 511 of 578
Supercell’s Ilkka Paananen calls out EU regulators over the Digital Fairness Act, warning that new laws could cripple Europe’s $27B gaming industry. Is Brussels protecting consumers or killing its own innovation engine?
Starting January 1, 2026, developers based in the Republic of Korea must provide a server‑to‑server notification endpoint when registering a new Services ID, or updating an existing Services ID, to associate their website with an app using Sign in with Apple . As a reminder, registering a notification endpoint allows Apple to send you important updates about the people who use your app and their account status, including: Changes in email forwarding preferences. Account deletions in your app. Permanent Apple Account deletions. To learn more about server-to-server notifications, see WWDC20 session 10173: Get the most out of Sign in with Apple . When you receive these notifications, you should immediately update any data associated with the account change in the app, as well as any necessary server infrastructure, to give people more control of the personal data they’ve shared. For more information, see Processing changes for Sign in with Apple accounts . Before submitting a new app to the App Store, or updating an existing app configuration to register a new Services ID or modify an existing Services ID, please read the guidance below. Account change guidance Account changes are directly related to privacy and control for the user and their personal data, and confirming account changes should be straightforward and transparent. For account email forwarding changes: Ensure any displayed user data affected by the account change matches the change event in the notification payload. Typically, this data is displayed in the app’s account settings or user profile. If people need to visit a website to finish changing or verifying their email address, include a link directly to the page on your website where they can complete the process. Keep users informed. If the email forwarding change affects other services you offer, let them know. If your app supports In-App Purchases, help people understand how billing, order tracking, and cancellations will be handled with the new email address. For account deletions: See TN3194: Handling account deletions and revoking tokens for Sign in with Apple . Note: Always follow applicable legal requirements for storing and retaining user account information and for handling account changes and deletions. This includes complying with local laws where your apps are available. If you have questions regarding your legal obligations, check with your legal counsel. Resources App Review Guidelines Human Interface Guidelines: Managing accounts
Beginning January 1, 2026, a new state law in Texas — SB2420 — introduces age assurance requirements for app marketplaces and developers. While we share the goal of strengthening kids’ online safety, we are concerned that SB2420 impacts the privacy of users by requiring the collection of sensitive, personally identifiable information to download any app, even if a user simply wants to check the weather or sports scores. Apple will continue to provide parents and developers with industry-leading tools that help enhance child safety while safeguarding privacy within the constraints of the law. Once this law goes into effect, users located in Texas who create a new Apple Account will be required to confirm whether they are 18 years or older. All new Apple Accounts for users under the age of 18 will be required to join a Family Sharing group , and parents or guardians will need to provide consent for all App Store downloads, app purchases, and transactions using Apple's In-App Purchase system by the minor. This will also impact developers, who will need to adopt new capabilities and modify behavior within their apps to meet their obligations under the law. Similar requirements will come into effect later next year in Utah and Louisiana. Today we’re sharing details about updates that we’re making and the tools we’ll provide to help developers meet these new requirements. To assist developers in meeting their obligations in a privacy-preserving way, we’ll introduce capabilities to help them obtain users’ age categories and manage significant changes as required by Texas state law. The Declared Age Range API is available to implement now, and will be updated in the coming months to provide the required age categories for new account users in Texas. And new APIs launching later this year will enable developers, when they determine a significant change is made to their app, to invoke a system experience to allow the user to request that parental consent be re-obtained. Additionally, parents will be able to revoke consent for a minor continuing to use an app. More details, including additional technical documentation, will be released later this fall. We know protecting kids from online threats requires constant vigilance and effort. That’s why we will continue to create industry-leading features to help developers provide age-appropriate experiences and safeguard privacy in their apps and games, and empower parents with a comprehensive set of tools to help keep their kids safe online.
This month: Watch a new code-along video to discover how to use the Foundation Models framework to access the on-device LLM that powers Apple Intelligence. Plus, dive into new games offerings, explore new App Store Connect features, and find out how the air-quality app Paku is helping its users breathe easy. Read the full story
A poker roguelike made by one person broke the internet, and Playstack turned it into a phenomenon. Here’s how they did it.
Hacker News
“GPT-5.5's API pricing is reshaping how startups build AI products”
