The latest articles on DEV Community by Sobo Martin Iulian (@iulian85). https://dev.to/iulian85 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3995311%2F39cd99e2-a278-4129-a976-f1f47ca34e9d.jpg https://dev.to/iulian85 en Sobo Martin Iulian Sun, 21 Jun 2026 12:58:06 +0000 https://dev.to/iulian85/what-i-am-testing-first-in-eliezer-go-an-early-android-location-app-4if1 https://dev.to/iulian85/what-i-am-testing-first-in-eliezer-go-an-early-android-location-app-4if1 <p>I am working on Eliezer Go, an Android app built around location-based discovery, AR-style interactions, referrals, wallet connection, and progress tracking.</p> <p>The most tempting thing would be to push the AR layer first, because that is the most visible part of the concept. I am doing the opposite for now. AR hunting is paused while the app's core flows are tested on real Android devices.</p> <p>The reason is simple: if the base app is not reliable, the AR layer will make every bug harder to understand.</p> <h2> The Core Flows </h2> <p>The current build is centered on a few practical questions:</p> <ul> <li>Does the APK install cleanly?</li> <li>Does the app open reliably on different Android devices?</li> <li>Does the city/location screen make sense?</li> <li>Does the wallet screen behave correctly?</li> <li>Does the TON wallet connection flow fail clearly when something is wrong?</li> <li>Does the referral screen work without confusing the user?</li> <li>Does the AR camera screen open as expected?</li> <li>Do device trust checks behave differently on real phones, emulators, rooted devices, or spoofed GPS setups?</li> </ul> <p>That is the unglamorous part of mobile development, but it is where most early apps either become usable or stay fragile.</p> <h2> Why Pause AR Hunting </h2> <p>AR features look good in screenshots, but they depend on many things working at once: camera permission, location permission, sensor behavior, device performance, and a clear user flow.</p> <p>For now, Eliezer Go keeps AR hunting paused so testing can focus on:</p> <ul> <li>wallet connection</li> <li>progress tracking</li> <li>device trust checks</li> <li>app navigation</li> <li>stability on real hardware</li> </ul> <p>Once those pieces are stable, AR can come back with fewer unknowns.</p> <h2> Distribution </h2> <p>The Android test build is available through GitHub Releases:</p> <p><a href="https://github.com/Iulian85/Eliezer-Go/releases" rel="noopener noreferrer">https://github.com/Iulian85/Eliezer-Go/releases</a></p> <p>Repository:</p> <p><a href="https://github.com/Iulian85/Eliezer-Go/" rel="noopener noreferrer">https://github.com/Iulian85/Eliezer-Go/</a></p> <h2> Current Project Note </h2> <p>Eliezer Go is being promoted as a mobile Android app in testing. ELZR token distribution is not active now. The first planned airdrop is scheduled for 2027.</p> <p>Updates:</p> <p><a href="https://t.me/eliezergo" rel="noopener noreferrer">https://t.me/eliezergo</a></p> android opensource mobile startup