The app already has several screens in place: Home, Hunt, Ads, Frens, and Wallet. The Home screen shows the user's city and progress. The Hunt screen is the entry point for AR interaction. Frens handles referrals. Wallet tracks app progress and connection-related flows.

The project is still in the stage where real-device behavior matters more than feature volume.

Current Decision: Keep AR Hunting Paused

AR hunting is one of the more interesting parts of the app, but it is not the first thing being pushed publicly right now.

The current decision is to keep AR hunting paused while the basic Android experience is checked:

• install flow

• permissions

• screen navigation

• camera opening behavior

• wallet connection

• progress tracking

• device trust behavior

• referral flow

This makes debugging cleaner. A location-based app can fail for many different reasons, and adding AR on top too early makes it harder to isolate what went wrong.

What Real Testers Can Help With

The most useful feedback does not need to be complicated. A good report can be as simple as:

I used a Samsung phone on Android 14. The app opened, city detection worked, but the wallet screen stayed loading after I tapped connect.

That kind of report gives enough information to reproduce or narrow the issue.

Useful reports include:

• device model

• Android version

• app version

• screen tested

• expected result

• actual result

• screenshot or short recording

Links

Android build:

https://github.com/Iulian85/Eliezer-Go/releases

Repository:

https://github.com/Iulian85/Eliezer-Go/

Community updates:

https://t.me/eliezergo

Important note: current communication is about the Eliezer Go Android app. ELZR token distribution is not active now, and the first planned airdrop is scheduled for 2027.