// the take
A solo-developer Android ride-hailing prototype built to address the driver identity fraud problem on platforms like Didi. It implements NFC/RFID chip scanning to verify driver credentials against a backend database, OCR-based license number recognition using OpenCV, and Baidu Maps route planning — all wired into a single app. Aimed at Android developers who want a worked example of NFC + NDK + OpenCV integration in a real-world feature context.
The NFC/RFID flow is genuinely complete end-to-end: chip scan → NDK MD5 encryption → OkHttp3 POST → server validation → result display, not just a stub. The OCR pipeline in DigitImageProcessor uses real computer vision techniques (Scharr gradient, binary threshold, morphological open operations) rather than just calling a cloud API. JNI integration is done correctly — the native-lib.cpp bridge follows the Java_packagename_classname_method naming convention and the CMakeLists is present. Code is organized into clear modules (DriverLicenseNFC, DriverLicenseRecognition, utils) rather than dumped into MainActivity.
Last pushed October 2019, depends on OpenCV 3.2 and Baidu Maps SDK 5.3 — both years behind; the Baidu Maps SDK in particular requires an API key that points to a China-only service, making this non-functional outside China without significant refactoring. The OCR number extraction in findCardNumBlock uses hardcoded pixel offsets (numberROI.x = 3 * roi.x + 120, width = binary.cols() - roi.x - 390) calibrated to one specific license format — it will silently produce wrong crops on any other card layout. The server backend is a personal Tencent Cloud VM running PHP/MySQL with no source code published, so the validation and analytics features are completely opaque and presumably gone. MD5 is used as a security primitive for RFID data integrity — that's not a security guarantee, it's just obfuscation.
We read the README, the directory tree and a key source file in June 2026. Nobody pays to be listed. How we judge →