Feature Comparison

Feature Comparison: Launcher 3 vs. Launcher 4

All features are part of the BlueFletch Launcher platform:

Launcher 3 Feature	Feature/Functionality	Launcher 4 Feature	Feature/Functionality
	No AppConfig object	AppConfig	Introduces a new appConfig object to centralize configurations for individual applications
	No reusable app configurations	Application Object Variables	Supports reusable app configurations with key-value pairs
Quick Start Applications Folder	Appears as a footer on the home screen. Prioritizes the first folder in a group for display on the Launcher.	Quick Start Applications Folder	Appears either as a footer or anywhere in the workspace. Supports layout options like columnSpan and rowSpan.
Layouts	Apps grouped by roles into folders or groups. Role-based app visibility.	Tabbed Layouts	Apps grouped into tabs linked to layouts. Widget with shortcuts to tab pages.
Custom Field Display	No IMEI capability.	Custom Field Display	Enables the use of IMEI as a unique device identifier instead of just the serial number. Customers can configure the Launcher to display the IMEI in the header.
Theme	No options for iconShape.	Theme	A new field, iconShape, has been introduced to define the shape of app icons in the main workspace. Supported values for this field include roundedCorner, square, squircle, and circle.
	No footer option; only custom headers.	Footer	Footers can now be configured just like headers. Any widget can now be a footer.
Custom Intents Platform Actions	No support for polling for changes or updates to a Site List URL.	Custom Intents Platform Actions	BlueFletch Launcher can now specify a Site List URL for downloading site information. This enables polling for changes or updates to the Site List URL. When the broadcast action com.bluefletch.action.ACTION_UPDATE_SITES is received, the Launcher triggers polling for updates to the list via a Custom Intent.
Luggage Tag	No geofencing lockdown functionality.	Luggage Tag	With geofencing lockdown functionality.
Secure Device	Secure Device config block part of Launcher.json Settings configuration. Variables using 'unsecured' and 'secure' at the beginning of the variables.	Secure Device	With its own config block secureDevice. Any reference to 'unsecured' and 'secured' had been removed. A new 'enabled' field is added to turn secureDevice mode on/off more easily.