[Hackathon demo] Show the native build number in Settings

Open Beginner friendly
#5 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
90/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
react-native, typescript
Domain
mobile

Research direction

Start with app/(tabs)/settings.tsx and read docs/mobile-agent-loop.md for the validation steps. Use the existing About version value as the comparison point, then use agent-device before and after the change. Done means the native build version appears when available, the version-only fallback remains, and the PR includes labeled Before and After evidence.

Written by the indexing model from the issue text.

Description

enhancement good first issue

Hackathon demo ticket. This is intentionally small and self-contained.

Problem

Settings shows the marketing version only, which makes it harder to tell two local native builds apart during QA.

Scope

Update the About version value in app/(tabs)/settings.tsx using Expo Constants. Show the native build version when available and retain the current version-only fallback.

Acceptance criteria

  • Settings displays Version (build) when a native build version exists.
  • It still displays Version when the native value is unavailable.
  • No new dependency or settings row is added.

Validation

Follow docs/mobile-agent-loop.md.

Before: capture the About section and read its version value with agent-device.

After: return to the same section, prove the full version and build text with agent-device, and capture the matching screenshot.

The PR description must include clearly labeled Before and After evidence.

Dominant language
TypeScript
Stars
0
Forks
0
Avg merge
1d 7h
Merged PRs (30d)
10

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from appandflow/trailhead

All issues in appandflow/trailhead

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.