developer documentation

AppWizard
October 5, 2026
IAB Tech Lab has released version 1.6.10 of its Open Measurement SDK for Android, introducing the ability for verification scripts for native ads to run within Android's Jetpack JavaScriptEngine instead of the traditional WebView. This update, effective from October 1, 2026, allows for a significant reduction in verification check initiation time, with the sandbox environment taking approximately 11 milliseconds compared to 268 milliseconds in the WebView. Applications that do not implement this new feature will continue to function as before, and HTML-based ads are not included in this update. The JavaScriptEngine library allows JavaScript evaluation without a WebView, reducing resource consumption and enabling compatibility with background services. The adoption process for this feature involves updating to OM SDK Android 1.6.10 or later, integrating the androidx.javascriptengine dependency, and maintaining the sandbox throughout the app's lifecycle.
AppWizard
September 22, 2026
When an Android app encounters issues, the cause may be related to the device's settings rather than the app itself. Factors such as missing permissions, battery restrictions, or disabled notifications can affect app functionality. Users should check the specific feature that is failing, such as verifying microphone permission for voice messages or camera access for QR code scanners. Background restrictions can hinder apps that require background functionality, and different apps have varying background requirements. Notification settings should be inspected if alerts are absent, as these can differ by application and device. Storage space and cache management are important, with a recommendation to avoid clearing everything at once. If problems arise after installing an app from an untrusted source or if it requests excessive permissions, the app itself may be the issue. Android settings can vary between devices, so users may need to search for specific settings if guides do not match their device. Troubleshooting should be done one step at a time to identify the root cause of the issue.
Winsage
September 11, 2026
Microsoft released Experimental Windows 11 build version 26340.9354, which includes a mock-up of a new Resume hovercard featuring a redesigned mouse pointer. The new pointer has a broader shape, a softer curve on its lower-left side, and a more symmetrical appearance, differing from the traditional thin tail-like extension of Windows cursors. Although Microsoft has not confirmed any changes to the system cursor, the release notes mention a known issue with cursor customization but do not address any redesign. Reports from June indicated that Microsoft was testing a new cursor as part of its Windows 11 modernization initiative. The mock-up resembles a Fluent icon, with a cleaner and wider shape compared to the classic Windows arrow. Despite this, the current developer documentation still refers to the traditional pointer as the "arrow cursor." Windows 11 has modernized many UI elements, but the pointer has remained largely unchanged, with limited customization options. The combination of the recent mock-up and previous reports suggests a potential transformation in the cursor design may be forthcoming.
AppWizard
August 5, 2026
Advertising companies provide software development kits (SDKs) for mobile app monetization, which often automatically transmit users' location data to ad systems and location data brokers, raising privacy concerns. Many developers and users may be unaware of this data sharing. When developers allow SDKs to collect location data, it poses risks beyond targeted ads, including potential misuse by agencies like ICE and global surveillance. Location data brokers harvest precise movements of individuals, often without their consent, through mobile applications. Some apps directly collaborate with data brokers, while others leak data through advertising SDKs during real-time bidding (RTB) auctions. An incident in 2025 revealed that many apps unknowingly contributed to a location data broker's database. Developers must understand their SDKs' location-sharing practices to mitigate risks. Advertising SDKs can collect location data automatically once users grant permission, without specific permissions for the SDKs themselves. Precise location data can be collected when apps have location permissions, leading to potential privacy violations. Several SDKs have been identified as collecting location data by default, increasing the risk of unintentional data leaks. The Electronic Frontier Foundation (EFF) found that four advertising SDKs collect users' location data by default when location permissions are granted. InMobi encourages location sharing for higher revenue, while BidMachine updated its documentation after EFF's inquiry, confirming precise location data collection. Verve's SDK also collects location data by default but presents a cautious narrative in its Play Store guidance. Huawei's SDK recommends obtaining location permissions to enhance revenue, with default location sharing occurring if permissions are granted. Location data can be shared without users' knowledge or meaningful consent, complicating informed consent issues. The focus on four SDKs does not imply that others adequately protect location data, as many have faced criticism for similar practices. Studies indicate that SDKs often encourage increased data collection through design and documentation, leading to minimal control for developers over data transmission. The EFF's analysis highlights that advertising SDKs incentivize location data sharing through default settings and unclear documentation. Developers should assess third-party SDKs and disable unnecessary data collection. Regulators must hold developers accountable for unlawful data sharing, while legislators should enact laws to protect location privacy and address online behavioral advertising, which drives data tracking.
Winsage
June 9, 2026
Microsoft announced a suite of agent-centric features for Windows 11 at the Build 2026 conference, introducing the Microsoft Agent Platform for local AI agents. This includes enhanced integration with Microsoft Foundry, GitHub, and the M365 suite. The developer documentation covers local agent runtimes and isolation patterns, highlighting the Microsoft Execution Containers SDK and Entra Agent ID. Enterprise controls like Intune and Agent 365 are also featured. The upcoming Copilot Actions will allow agents to interact with local files and applications, aimed at improving workflows. Microsoft is addressing security concerns with resources outlining strategies to mitigate risks such as cross-prompt injection. Industry commentary indicates a growing discussion about privacy and security in relation to these changes.
AppWizard
June 8, 2026
Google has introduced AppFunctions, a framework for Android that allows applications to expose callable functions to AI assistants, currently in experimental preview. This framework enables apps to register capabilities with an OS-level registry, requiring specific permissions for callers, including agents and assistants, to maintain user privacy and security. As of May 2026, integration with Gemini is in a private preview for select testers. AppFunctions targets devices running Android 16 or higher and provides developers with tools like an agent skill and Jetpack tooling for creating Kotlin bindings. The framework aims to enhance Gemini's capabilities, allowing it to use multiple extensions and execute background agent skills, facilitating automation of tasks for users.
Search