I am working on Eliezer Go, an Android app built around location-based discovery, AR-style interactions, referrals, wallet connection, and progress tracking.
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.
The reason is simple: if the base app is not reliable, the AR layer will make every bug harder to understand.
The Core Flows
The current build is centered on a few practical questions:
- Does the APK install cleanly?
- Does the app open reliably on different Android devices?
- Does the city/location screen make sense?
- Does the wallet screen behave correctly?
- Does the TON wallet connection flow fail clearly when something is wrong?
- Does the referral screen work without confusing the user?
- Does the AR camera screen open as expected?
- Do device trust checks behave differently on real phones, emulators, rooted devices, or spoofed GPS setups?
That is the unglamorous part of mobile development, but it is where most early apps either become usable or stay fragile.
Why Pause AR Hunting
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.
For now, Eliezer Go keeps AR hunting paused so testing can focus on:
- wallet connection
- progress tracking
- device trust checks
- app navigation
- stability on real hardware
Once those pieces are stable, AR can come back with fewer unknowns.
Distribution
The Android test build is available through GitHub Releases:
https://github.com/Iulian85/Eliezer-Go/releases
Repository:
https://github.com/Iulian85/Eliezer-Go/
Current Project Note
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.
Updates:
Top comments (0)