# nfc Published articles for nfc. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## ENILINX TICKEY - An ESP32-S3-based color e-Paper badge with open firmware (Crowdfunding) DevFeed: [ENILINX TICKEY - An ESP32-S3-based color e-Paper badge with open firmware (Crowdfunding)]() Original publisher: [Read original article]() Author: Debashis Das Published: 2026-09-17T00:00:34Z Content type: news Language: en Sources: [CNX Software - Embedded Systems News]() Topics: [ESP32-S3](), [e-ink](), [Microcontroller](), [Embedded Systems](), [Open Source]() Tags: [ble](), [bluetooth](), [display](), [e-paper](), [embedded](), [embedded-systems](), [epaper](), [esp32](), [esp32-s3](), [espressif](), [firmware](), [hardware](), [kickstarter](), [low-power](), [news](), [nfc](), [open-source](), [qr-code](), [screen](), [video]() ### AI overview ENILINX has launched the TICKEY, a 3.7-inch color e-paper badge and desk display based on the ESP32-S3. It includes Wi-Fi, Bluetooth, NFC, a rechargeable battery, and support for smartphone updates, with standard and Developer Edition storage options. The company describes the firmware as open source, but no repository or further implementation details were available when the article was written. ### Source excerpt ENIAC (operating as ENILINX) has launched the TICKEY, a 3.7-inch color e-Paper smart badge and desk display built around an ESP32-S3 MCU. The device features Wi-Fi, Bluetooth, and NFC connectivity, allowing users to update the screen from a smartphone without requiring continuous power to hold a static image. The display uses Modos' color e-paper technology to deliver 48+ native colors, with refresh times as fast as 3 seconds and sunlight readability. Measuring just 3.8mm thick and weighing 45 grams, TICKEY features an aluminum-alloy body and interchangeable faceplates, and supports NFC and QR code-based web profile sharing. The standard version includes 8MB of storage, whereas the Developer Edition offers 128MB for more advanced applications. These features make it suitable for desk reminders, event identification, digital business cards, and interactive maker projects. TICKEY specifications: Wireless MCU - ESP32-S3 Dual-core Tensilica LX7 microcontroller @ up to 240 MHz Wireless - 2.4 GHz 802.11n [...] The post ENILINX TICKEY - An ESP32-S3-based color e-Paper badge with open firmware (Crowdfunding) appeared first on CNX Software - Embedded Systems News. ## FREE-WILi 2 portable hacking multitool features two RP2350 MCUs, ESP32-C5, ICE40 FPGA, and Raspberry Pi CM0 DevFeed: [FREE-WILi 2 portable hacking multitool features two RP2350 MCUs, ESP32-C5, ICE40 FPGA, and Raspberry Pi CM0]() Original publisher: [Read original article]() Author: Debashis Das Published: 2026-09-09T00:00:02Z Content type: news Language: en Sources: [CNX Software - Embedded Systems News]() Topics: [Embedded Systems](), [Raspberry Pi](), [ESP32-C5](), [Hardware](), [Hacking](), [Linux]() Tags: [802-15-4](), [ble](), [bluetooth](), [broadcom-bcmxxxx](), [c-c-plus-plus](), [can](), [electronics](), [embedded](), [esp32](), [esp32-c5](), [espressif](), [fpga](), [hack](), [hacking](), [hardware](), [lattice](), [linux](), [lora](), [meshtastic](), [nfc](), [open-hardware](), [python](), [raspberry-pi](), [raspberry-pi-rp2350](), [rfid](), [rust](), [security](), [som](), [stm32](), [stmicro-stm32](), [texas-instruments-simplelink](), [thread](), [tools](), [video](), [wi-fi](), [wifi-6](), [wireless](), [zigbee]() ### AI overview The FREE-WILi 2 Founder Edition is an open-hardware, portable multitool for hardware hackers, pentesters, and embedded-system developers. It combines two Raspberry Pi RP2350 MCUs, an ESP32-C5, a Lattice ICE40UP5K FPGA, and a Raspberry Pi CM0 capable of running a full Linux OS, along with touchscreen controls, expansion headers, and multiple wireless interfaces. ### Source excerpt The FREE-WILi 2 (Founder Edition) is an open-hardware, portable hacking multitool and lab designed for hardware hackers, pentesters, and embedded system developers. Designed as an "open electronics multitool," it combines a range of chips and modules into a handheld device, including two Raspberry Pi RP2350 MCUs, an ESP32-C5 for wireless connectivity, a Lattice ICE40UP5K FPGA, and a Raspberry Pi CM0 for running a full Linux OS. The device also features a 3.5-inch capacitive touchscreen, a 14-button physical interface, and modular "Orca" headers for hardware expansion. Its wireless features include 2.4/5GHz Wi-Fi, Bluetooth, LoRa, sub-GHz RF, NFC, 125kHz RFID, and IR. These features make it very suitable for wireless testing, embedded hardware debugging, real-time control, electronics development, and retro gaming, with support for Adafruit Fruit Jam, PICO-8, and Doom. FREE-WILi 2 specifications: Compute Main MCUs - 2x Raspberry Pi RP2350B (One for main controls, one dedicated to display) SoM - Raspberry [...] The post FREE-WILi 2 portable hacking multitool features two RP2350 MCUs, ESP32-C5, ICE40 FPGA, and Raspberry Pi CM0 appeared first on CNX Software - Embedded Systems News. ## Announcing Espressif's Aliro SDK DevFeed: [Announcing Espressif's Aliro SDK]() Original publisher: [Read original article]() Author: John Lee Published: 2026-07-16T00:00:00Z Content type: release Language: en Sources: [Blog on Developer Portal]() Topics: [Espressif](), [SDKs](), [Matter]() Tags: [aliro](), [blog](), [bluetooth-le](), [espressif](), [matter](), [mobile](), [nfc](), [protocol](), [sdk]() ### AI overview Espressif announces esp-aliro, an SDK for supporting the Aliro standardized mobile access-credentials protocol on Espressif SoCs. Initial support covers Aliro over NFC, while Bluetooth LE and UWB support are planned. ### Source excerpt Aliro brings mobile access credentials to Espressif devices and is compatible with Matter. We are excited to announce esp-aliro, an SDK that enables support for the Aliro standardized protocol on Espressif SoCs. ## NFC, Crypto, Biometrics, And A New Build Cloud DevFeed: [NFC, Crypto, Biometrics, And A New Build Cloud]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-05-22T00:00:00Z Content type: release Language: en Sources: [CodeName One]() Topics: [Device APIs](), [Framework](), [Cloud](), [Bluetooth](), [Cryptography](), [ui](), [JavaScript]() Tags: [android](), [bluetooth](), [cloud](), [crypto](), [device-apis](), [framework](), [ios](), [javascript](), [nfc](), [preview](), [ui]() ### AI overview This weekly Codename One update covers biometrics, cryptography, and NFC APIs moving into the framework core, a Bluetooth simulator change, and a new Build Cloud UI available as a preview for feedback. ### Source excerpt Device APIs move into the framework core, revolutionary Bluetooth debugging, and the Build Cloud's new UI is live in preview. ## ESET Threat Report H2 2025 DevFeed: [ESET Threat Report H2 2025]() Original publisher: [Read original article]() Author: Jiří Kropáč Published: 2025-12-16T09:50:45Z Content type: article Language: en Sources: [WeLiveSecurity]() Topics: [Threat Research](), [ESET research](), [Malware](), [ransomware](), [Android](), [Artificial Intelligence](), [ClickFix]() Tags: [2025](), [ai](), [android](), [clickfix](), [eset-research](), [malware](), [nfc](), [ransomware](), [research](), [threat-detection](), [threat-report]() ### AI overview ESET's H2 2025 threat report describes rapid changes in the threat landscape, including the emergence of AI-driven malware such as PromptLock, major shifts in malware distribution, growth in ransomware activity, and increasingly sophisticated Android NFC threats. ### Source excerpt A view of the H2 2025 threat landscape as seen by ESET telemetry and from the perspective of ESET threat detection and research experts ## KMP vs Flutter vs React Native DevFeed: [KMP vs Flutter vs React Native]() Original publisher: [Read original article]() Author: IceRock Development Published: 2021-10-25T14:51:05Z Content type: comparison Language: en Sources: [Stories by IceRock Development on Medium]() Topics: [Kotlin Multiplatform](), [cross-platform](), [Flutter](), [React Native](), [Mobile](), [Development]() Tags: [android](), [bluetooth](), [business-logic](), [camera](), [cross-platform](), [dart](), [flutter](), [ios](), [javascript](), [kmp](), [kotlin](), [mobile-app-development](), [multiplatform](), [nfc](), [react-native](), [ui]() ### AI overview This comparison examines Kotlin Multiplatform Mobile, Flutter, and React Native for cross-platform mobile development. It explains that Kotlin Multiplatform shares business logic between Android and iOS while retaining native user interfaces, Flutter draws its interface using a canvas and Material Design specifications, and React Native maps native components to JavaScript. The article concludes that the best choice depends on the project's specific requirements. ### Source excerpt There is a wide range of options in cross-platform nowadays, among them Flutter, React Native, and, of course, Kotlin Multiplatform Mobile. Which technology should you choose, and why this one? Let's try to clear out! All technologies have their advantages and disadvantages, resolve particular problems, but never all of them. Thus, your choice will depend on specific tasks. Guys from Jetbrains have made an incredible attempt to optimize development costs and reuse the code. Moreover, such reuse is possible not only within one platform but also between different platforms (Android and iOS). If your development team wants to keep native UI for each platform, then Kotlin Multiplatform Mobile is your perfect option. It is due to the fact that Kotlin Multiplatform doesn't do UI at all. It, instead, does business logic for Android and iOS apps. Because of the special configuration of the project, it is possible to make a project that will be compiled in the Android library with specific code for Android, and in the iOS framework with the corresponding code for iOS. From a technical perspective, there are no more problems with using the same code on iOS and Android at the same time. When you debug your code, you only need to edit it once, and changes will happen on both platforms. However, on the native side of applications, it would be better not to share the following: the whole interface; binding the interface to the shared Viewmodel from the shared code library; platform-specific features: work with camera, NFC, Touch ID, or Bluetooth. And in any case, sharing UI code across platforms is not necessary. This usually requires several iterations to make the user UI and behave more natively. This, in turn, requires additional development cycles. Flutter uses canvas from native SDK of different platforms and draws its UI component on that canvas using Material design specifications. React Native uses native components mapped to js code. React makes it possible to update the ## За двумя мобильными сервисами: HMS и GMS в одном приложении DevFeed: [За двумя мобильными сервисами: HMS и GMS в одном приложении]() Original publisher: [Read original article]() Author: and291 (Кошелёк) Published: 2020-10-05T06:51:28Z Content type: tutorial Language: ru Sources: ["Кошелёк" RU]() Topics: [hms](), [Android](), [huawei]() Tags: [android](), [android-4143319ed9f7](), [android-development](), [gms](), [hms](), [huawei](), [map](), [mobile-services](), [nfc](), [safety]() ### AI overview The article explains how the Wallet Android app integrated Huawei Mobile Services alongside Google Mobile Services in one application. It covers support for HMS Push Kit, Map Kit, and Safety Detect, runtime service selection, and the development tradeoffs of maintaining a shared version across distribution platforms. ### Source excerpt Привет, Хабр! Меня зовут Андрей, я делаю приложение "Кошелёк" для Android. Уже больше полугода мы помогаем пользователям смартфонов Huawei оплачивать покупки банковскими картами бесконтактно -- через NFC. Для этого нам потребовалось добавить поддержку HMS: Push Kit, Map Kit и Safety Detect. Под катом я расскажу, какие проблемы нам пришлось решать при разработке, почему именно так и что из этого вышло, а также поделюсь тестовым проектом для более быстрого погружения в тему. Читать дальше -> ## YubiKey for SSH, Login, 2FA, GPG and Git Signing DevFeed: [YubiKey for SSH, Login, 2FA, GPG and Git Signing]() Original publisher: [Read original article]() Published: 2017-04-15T00:00:00Z Content type: tutorial Language: en Sources: [Marco Pivetta]() Topics: [Security](), [OpenSSH](), [Authentication](), [Cryptography](), [Open Source](), [USB](), [Git](), [Linux](), [Development]() Tags: [authentication](), [crypto](), [cryptography](), [dell](), [development](), [git](), [linux](), [nfc](), [open-source](), [pc](), [ssh](), [tutorial](), [usb](), [xps]() ### AI overview A tutorial on using YubiKey Neo devices to improve developer security through two-factor authentication, PAM login authentication, GPG mail and Git commit signing or encryption, and SSH authentication. It also explains the need for a backup key and introduces NFC-based 2FA setup. ### Source excerpt I've been using a YubiKey Neo for a bit over two years now, but its usage was limited to 2FA and U2F. Last week, I received my new DELL XPS 15 9560, and since I am maintaining some high impact open source projects, I wanted the setup to be well secured. In addition to that, I caught a bad flu, and that gave me enough excuses to waste time in figuring things out. In this article, I'm going to describe what I did, and how you can reproduce my setup for your own safety as well as the one of people that trust you. Yubi-WHAT? In first place, you should know that I am absolutely not a security expert: all I did was following the online tutorials that I found. I also am not a cryptography expert, and I am constantly dissatisfied with how the crypto community reduces everything into a TLA, making even the simplest things impossible to understand for mere mortals. First, let's clarify what a YubiKey is. That thing is a YubiKey. What does it do? It's basically an USB key filled with crypto features. It also is (currently) impossible to make a physical copy of it, and it is not possible to extract information written to it. It can: Generate HMAC hashes (kinda) Store GPG private keys Act as a keyboard that generates time-based passwords Generate 2FA time-based login codes What do we need? In order to follow this tutorial, you should have at least 2 (two) YubiKey Neo or equivalent devices. This means that you will have to spend approximately USD 100: these things are quite expensive. You absolutely need a backup key, because all these security measures may lock you out of your systems if you lose or damage one. Our kickass setup will allow us to do a series of cool things related to daily development operations: Two Factor Authentication PAM Authentication (logging into your linux/mac PC) GPG mail and GIT commit signing/encrypting SSH Authentication I am not going to describe the procedures in detail, but just link them and describe what we are doing, and why. Setting up NFC 2FA