GHOST DEVELOPERANDROID DEVELOPER
Back to projects
Tools

Nexora Git

A real Git workspace for Android with local repository operations, code editing and GitHub integration.

View source code

Based on a real GitHub project. Features can change during development.

NG / GHOST DEVELOPER
01 / OVERVIEW

What does it do?

Native Android Git and GitHub workspace with code editing, repository workflows and service integrations.

A real Git workspace for Android with local repository operations, code editing and GitHub integration.

02 / CAPABILITIES

Key capabilities

  • Native Git engine using libgit2 and JNI.
  • Repository and GitHub workflows on Android.
  • Modern Jetpack Compose UI.
  • Service integration and delivery automation.
03 / MY ROLE

Engineering focus

Android, C++, native integration and CI/CD.

TECHNICAL DETAILS

How it is built

Architecture, implementation choices and the current state of the project.

Advanced development · VPS activation pending
01CHALLENGE

What problem does it address?

Provide Git and GitHub workflows on Android without using a WebView wrapper, Termux or an externally installed Git binary.

02ARCHITECTURE

Architecture and boundaries

01
UI and domain

Jetpack Compose, ViewModels, use cases and repository boundaries separate the UI from the Git engine.

02
Local Git engine

A Kotlin GitEngine implementation delegates to a JNI bridge and libgit2; native operations run off the main thread.

03
GitHub and authentication

An API layer separate from the local engine, with a self-hosted OAuth broker required for the complete production flow.

03TRADE-OFFS

Engineering decisions

  • Separate local Git from the GitHub API to avoid coupling repository operations to remote calls.
  • Use SAF and managed storage to respect Android permissions; content:// paths are not treated as filesystem paths.
  • Keep credentials out of Git remote URLs and constrain their handoff to approved transports.
04VERIFICATION

How it is checked

  • Separate Android, native Git and CodeQL workflows exist. These are reproducible checks, not proof of a stable release.
  • The repository documents signing checks, SHA-256 fingerprints and mandatory gates before publishing APK/AAB files.
  • The performance audit defines size and workload bounds but does not yet report measured real-device usage.
05LIMITATIONS

Current status and next steps

  • Do not advertise stable APKs or a live production VPS: signing approval and service deployment are still pending.
  • Official screenshots captured from the actual app are still pending; marketing graphics are not functional evidence.
  • Real-device usage, startup and latency measurements have not been verified as published outcomes.
Back to projects