Oreo is coming! Are you ready?

The JetAdvantage Link platform development team has been working hard over many months to update the core of our device platform to conform to API version 26 (commonly known as Oreo, or 8.0).

Having concluded internal testing and a limited-release beta (Beta1), we are now ready to share our work with the entire app developer community for your evaluation and feedback (Beta2) and most importantly to give you time to adapt your apps if necessary prior to its official release.

Here are some tips for making sure your apps are “Oreo ready”:

• Review the API changes introduced between Kitkat (4.4) and Oreo (8.0), to identify any deprecated APIs you might be using:
  • 4.4. to 5.0 (https://developer.android.com/about/versions/android-5.0-changes )
  • 5.0 to 6.0 (https://developer.android.com/about/versions/marshmallow/android-6.0-changes )
  • 6.0 to 7.0 (https://developer.android.com/about/versions/nougat/android-7.0-changes )
  • 7.0 to 8.0 (https://developer.android.com/about/versions/oreo/android-8.0-changes)
• Due to a change in permissions, PrintFromMassStorageBuilder cannot be used to print files from a USB thumb drive. Instead, you must use PrintFromUSBBuilder.
• UI anomalies have been observed when id tags are used within the include tag in an xml layout file (<include android:id=”@+id/my_id” />). Remove ids from your xml layout files.
• UI anomalies have been observed when loading scalable vector graphics (svg) images. Use ContextCompat/AppCompatResources to load svg images from resources. Also ensure vectorDrawables.useSupportLibrary = true is added under defaultConfig  in the gradle file.
• UI anomalies have been observed on devices with higher resolution displays (1024x768). Include resources appropriate for a display density of mdpi/160dpi (res/drawable-mdpi).

Download the Oreo Beta2 firmware from the Download page now and take it for a test drive with your app. Please follow these steps:

1. Uninstall all apps and remove the printer from HP Command Center (if the printer had been previously added)
2. Perform a format disk operation
3. Install the Oreo Beta2 firmware from a USB thumb drive
4. Configure the printer’s web proxy (if necessary)
5. Register the printer with HP Web Services (if necessary)
6. Enable LDB mode
7. Install your app using the HPKTool
8. Push your app’s App Attestation debug credentials using the HPKTool (if necessary)
9. Run your app, noting all anomalies encountered

For any anomalies found, first check your usage of the APIs. In our testing so far, most of the anomalies were actually due to the app’s incorrect use of the APIs or reliance on deprecated APIs.

If a defect in the Link Platform is proven or even strongly suspected, please report it through the Link for Device SDK support forum. Indicate in your post that you are using the Oreo Beta2 firmware image.

When your Oreo Beta2 testing has concluded and any app adjustments have been made, please:

1. Perform a format disk operation
2. Install the latest Public Release Firmware Image from a USB thumb drive
3. Configure the printer’s web proxy (if necessary)
4. Register the printer with HP Web Services (if necessary)
5. Delete any copies of the Oreo Beta2 firmware you may have downloaded

Thank you in advance for participating in the Oreo Beta2.

-- The JetAdvantage Link Team

HP is pleased to announce the release of version 1.3.0 of the Link for Device Simulator.

Please note: This simulator is intended for use with version 1.3.0 of the Link for Device SDK.

Download the new Simulator from the Downloads page.

HP is pleased to announce the release of Lighthouse Apps for JetAdvantage Link

Lighthouse apps are:

• An open source collection of HP authored Link apps​
• Scan To… Apps
  • Scan to Email
  • Scan to FTP
  • Scan to SMB (Network Folder)
• Cloud Storage Apps
  • HP for Box
  • HP for Dropbox
  • HP for Google Drive
  • HP for OneDrive
  • HP for OneDrive Business
  • HP for SharePoint

Lighthouse apps provide:

• Proof that the Link platform supports sophisticated and valuable apps
• Validation that the Link APIs are simple to use and well documented​
• Componentized sample code to leverage for your own Link App development purposes - use the parts you need
• Demonstration of best practices (security, usability, etc.)
• Fully functional app source code that can be customized specifically to create derivative works
• Inspiration to accelerate innovation and App development ​by others

What clever and unique solutions can you build on top of these basic building blocks?​

For more information and to get access to the code, see the new Lighthouse Apps page.