Vuzix Blade 2 Development Getting Started Guide

Getting started on developing software for the Vuzix Blade 2 is as simple as developing software for any other Android device. The Blade 2 utilizes the Android APIs and leverages the Android Studio to develop software for the device. There are ...

The Vuzix Blade 2 has a unique configuration for visual display. We need to create a new Device Profile to understand and visualize those screen limitations, while designing new User Interface and User experience. First, we need to acquire De...

It is recommended that you utilize Vuzix libraries to design your user experience. Adding these libraries to your Android project is simple and developer friendly. Vuzix provides a Jitpack repository for those libraries and other resources. Add...

The most important aspect to a well-designed user interface for an application intended to be used on the Vuzix Blade 2 is simplicity. This is largely driven by the limited amount of space on the Blade 2's display, but also by the constraints of the...

With the unique design and display that the Vuzix Blade 2 provides, there are some User Interface designs that work better than others. In our experience, we have found some styles and UI Designs fit better and are more useful for users. In the pr...

The Blade 2, by default, will have ADB (Android Debug Bridge) debugging disabled for security and privacy reasons. In the Blade 2 OS, we can enable ADB Debugging using the below steps. If you are having trouble with this please reach out to the ...

Overview Apps that you write for the Blade 2 can have user settings. Your app will typically have a mechanism for users to change those settings. You can also allow users to change app settings from within the companion app. Information about ...