Budget: 13000 UAH Deadline: 1 day
Good day, Oleg!
The case is described very clearly — and overall you are thinking correctly about the architecture. However, there are a few "underwater stones" that significantly affect the timelines.
Regarding the approach:
Foreground Service + SDK + decoding ISO 11784/11785 — okay
Insertion via Accessibility or IME — also correct options
The biggest risks (based on experience):
1. SDK from the manufacturer — often weak documentation or unstable callbacks
2. intercepting the physical button — not always available from the background service
3. insertion in Chrome — Accessibility may work unstably, IME is usually more reliable
4. background operation (Android 8+) — system limitations
Therefore, the key is not to "write code," but to quickly test these hypotheses.
I am the CEO of Mobiwolf. We have developed Android solutions with hardware/SDK integrations and background services, so we understand where blockers may arise.
How we would approach it:
first, we do a technical spike (3–6 days):
– check the SDK
– test the button
– test insertion (Accessibility vs IME)
After that, we finalize the architecture.
Estimation (roughly):
– spike: 24–48 hours
– full implementation: ~80–160 hours
Honestly: start in about ~3 weeks, but we can discuss the spike earlier.
Questions:
– is there access to the SDK and device right now?
– does the button currently open the native app?
– is it critical to use Chrome, or is a WebView fallback possible?
Let's continue the discussion privately.
Best regards,
Oleksiy
CEO, Mobiwolf