992 B
992 B
QFT Roadmap
v0.4 physical validation
- Use 450 B / single QR as the baseline and measure real-phone distinct new-frame/s at Windows 30 / 45 / 60 FPS.
- Record lock acquisition time, locked ROI area, camera FPS, successful decode/s, distinct new-frame/s and reacquire time per device.
- Only after real-device data exists, test nearby DATA payloads (e.g. 390 / 450 / 510 B) and keep the value with the highest effective file throughput rather than the highest theoretical bytes/frame.
- Add optional Windows FPS presets chosen from observed Android effective new-frame/s; the optical transport itself remains strictly one-way.
- Tune focus/exposure behavior across LCD/OLED and 60/120 Hz panels.
Later
- Fountain/RaptorQ to reduce whole-playlist replay cost without a reverse ACK channel.
- Native SIMD/custom visual decoder if ZXing remains the dominant bottleneck.
- Optional custom QFT Visual Code after the single-QR baseline is measured.
- iOS/macOS/Linux clients.