HN Showcase
Back to browse
Quick Issues: A Fast Mobile Issue Capture for GitHub, GitLab, and Gitea

Quick Issues: A Fast Mobile Issue Capture for GitHub, GitLab, and Gitea

by balthasarS·Feb 17, 2026·1 point·0 comments
Visit ProjectView on HN

AI Analysis

●●SolidSolve My ProblemShip It

Offline issue capture for GitHub/GitLab/self-hosted, but market is small and fragmented.

Strengths
  • •Genuinely offline-first with local SQLite sync queue; works on planes, subways, spotty Wi-Fi
  • •Supports all three major Git platforms plus self-hosted Gitea/Forgejo with PAT auth
  • •Native Swift, not Electron or React Native; optimized for iOS performance and UX
Weaknesses
  • •Mobile-only limits utility; most developers capture issues from desktop where browsers and native apps already exist
  • •Competitive pressure from GitHub/GitLab's own apps improving, plus Slack/Discord capture flows already ingrained
Target Audience

Mobile developers and engineering teams juggling multiple Git providers; GitHub, GitLab, self-hosted users

Similar To

GitHub Mobile · GitLab Mobile · Monodraw Workspace

Post Description

I got frustrated with how GitHub and GitLab's mobile apps handle issue creation. You need to be online, the flow is slow, and if you're on a self-hosted instance you're out of luck entirely.

So I built Quick Issues. It's a lightweight Swift app with an offline buffer -- you capture the issue, it syncs when you have connectivity. Supports GitHub, GitLab, and Gitea/Forgejo (including self-hosted and local with PAT).

A few technical notes for anyone interested: This was my first time using GRDB with SQLite instead of default Swift data structures, and the performance difference was significant. Setting up proper OAuth2 flows and GitHub/GitLab apps was more of an adventure than expected, but it's solid now.

Free for a single account/instance, paid tier if you juggle multiple providers.

My background is in GTD and data analytics, not traditional software engineering, so I'm genuinely curious: how does issue capture fit into your development workflow? Do you batch-create issues, capture them the moment they come up, use templates all the time or treat issues more as documentation only?

Similar Projects