It can be necessary, sometime, to collect device information, especially to identify a specific kind of device for debugging purpose, or to identify unique devices. In Dart/Flutter, one can install the device_info_plus package to have access to lot of informations regarding the device where the application is installed. Let have a quick look on this one.

$ flutter pub add device_info_plus Resolving dependencies... Downloading packages... cupertino_icons 1.0.9 (2.0.0 available) + device_info_plus 13.3.0 + device_info_plus_platform_interface 8.1.0 + ffi 2.2.0 + ffi_leak_tracker 0.1.2 + file 7.0.1 + flutter_web_plugins 0.0.0 from sdk flutter material_color_utilities 0.13.0 (0.13.1 available) meta 1.18.3 (1.19.0 available) + plugin_platform_interface 2.1.8 test_api 0.7.12 (0.7.15 available) vector_math 2.4.2 (2.4.3 available) + web 1.1.1 + win32 6.4.0 + win32_registry 3.0.3 Changed 10 dependencies! 5 packages have newer versions incompatible with dependency constraints. Try `flutter pub outdated` for more information.

The first step is to import the device_info_plus package in your code.

import 'package:device_info_plus/device_info_plus.dart';

One can extract only a small subset of all device information available, for example, to extract the device id, the id property can be retrieved and returned.

Future<String> getDeviceId() { DeviceInfoPlugin deviceInfoPlugin = DeviceInfoPlugin(); String deviceInfo = await deviceInfoPlugin.deviceInfo; return deviceInfo.id; }

If more information about a device is required, one can extract all of them as a Map<String, dynamic> using the data property.

Future<Map<String, dynamic>> getDeviceInfoMap() { DeviceInfoPlugin deviceInfoPlugin = DeviceInfoPlugin(); BaseDeviceInfo deviceInfo = await deviceInfoPlugin.deviceInfo; return deviceInfo.data; }

Some information are only available on a specific kind of device (e.g. iOS, Android, Browser). If the application has been developed with portability in mind, it can also be a good idea to extract device's information based on the architecture/platform.

Future<Map<String, dynamic>> getAndroidDeviceInfoMap() { DeviceInfoPlugin deviceInfoPlugin = DeviceInfoPlugin(); AndroidDeviceInfo deviceInfo = await deviceInfoPlugin.androidInfo; return deviceInfo.data; }

Here an example of the data extracted on an Android emulator:

I/flutter ( 3959): physicalRamSize: 2472 I/flutter ( 3959): type: user I/flutter ( 3959): manufacturer: Google I/flutter ( 3959): freeDiskSize: 464072704 I/flutter ( 3959): bootloader: unknown I/flutter ( 3959): fingerprint: google/sdk_gphone64_x86_64/emu64xa:16/BE2A.250530.026.D1/13818094:user/release-keys I/flutter ( 3959): host: e8e8f3751cda I/flutter ( 3959): isLowRamDevice: false I/flutter ( 3959): model: sdk_gphone64_x86_64 I/flutter ( 3959): id: BE2A.250530.026.D1 I/flutter ( 3959): brand: google I/flutter ( 3959): hardware: ranchu I/flutter ( 3959): product: sdk_gphone64_x86_64 I/flutter ( 3959): totalDiskSize: 6228115456 I/flutter ( 3959): supportedAbis: [x86_64, arm64-v8a] I/flutter ( 3959): supported32BitAbis: [] I/flutter ( 3959): display: BE2A.250530.026.D1 I/flutter ( 3959): isPhysicalDevice: false I/flutter ( 3959): version: {baseOS: , securityPatch: 2025-07-05, sdkInt: 36, release: 16, codename: REL, previewSdkInt: 0, incremental: 13818094} I/flutter ( 3959): systemFeatures: [android.hardware.sensor.proximity, android.software.adoptable_storage, android.hardware.sensor.accelerometer, android.software.controls, android.hardware.faketouch, android.software.telecom, android.hardware.telephony.subscription, android.hardware.reboot_escrow, android.hardware.telephony.data, android.software.backup, android.hardware.touchscreen, android.hardware.touchscreen.multitouch, android.software.erofs, android.software.print, android.software.activities_on_secondary_displays, android.software.device_lock, android.software.voice_recognizers, android.software.picture_in_picture, android.hardware.fingerprint, android.hardware.sensor.gyroscope, com.google.android.feature.PERSONAL_SAFETY, android.software.vulkan.deqp.level, android.software.cant_save_state, android.hardware.security.model.compatible, android.hardware.telephony.messaging, android.hardware.telephony.calling, android.hardware.sensor.relative_humidity, android.hardware.bluetooth, android.software.window_magnification, andr I/flutter ( 3959): tags: release-keys I/flutter ( 3959): supported64BitAbis: [x86_64, arm64-v8a] I/flutter ( 3959): availableRamSize: 967 I/flutter ( 3959): name: sdk_gphone64_x86_64 I/flutter ( 3959): time: 1753213259000 I/flutter ( 3959): device: emu64xa I/flutter ( 3959): board: goldfish_x86_64

More information can be found on Android via the AndroidBuildVersion object (including the base name, the code name and the release).

Depending on the platform, a lot of values can be extracted. Here a quick list enumerating few of them (the ones the most interesting to me):

The next step will be to generate an unique reproducible identifier from different systems using those information. A list of resources to help thinking about all of that:

As usual, happy hacking!

Cover image by Elena Ramseier on Unsplash