RIM Commits to Supporting Android Apps on the PlayBook
Research In Motion today announced as part of its quarterly earnings report that it will add support for Android and Java applications in its forthcoming QNX-based PlayBook. It will work through two "app players" that provide an application run-time environment for Java apps and Android v2.3 apps. RIM has the APIs and other tools developers need to port their Android/Java apps to run on the PlayBook. Developers will only need to use the tools to recompile their apps, submit them to BlackBerry App World, and, once approved, their apps will be available for download through BlackBerry App World. This move will give PlayBook users access to a much wider range of applications than just those that will be initially available for the PlayBook's QNX platform.
Android Apps Headed to Google's Chromebooks
Google today said its Chrome operating system will soon have access to the Google Play Store and the Android apps therein. ChromeOS will support all Android phone and tablet apps, including games, productivity apps, and social networking.
Android Instant Apps Let Apps Run Even When Not Installed
Google today showed off what it calls Android Instant Apps. The idea here is to allow people to access content that's buried within apps that are not installed on their phone.
Developers Can (Finally) Create Instant Apps
Google today made its instant apps tool available to all developers. Google first announced instant apps at its I/O developer conference in 2016.
Windows 10 to Run Android and iOS Apps
Microsoft today said Windows 10 devices will be able to run Android applications. According to Microsoft, developers will be able to reuse Java and C++ code to run Android apps in an Android subsystem on Windows 10 devices.
Google to Help Developers Make Apps More Accessible
Google today released a tool for developers that will scan apps and provide feedback on their accessibility. The idea is to help developers view their apps from a different perspective and gain insight about how their user interface choices may or may not work for those with special accessibility needs.
hope HP follows suit