We have been Pavlovian-conditioned to believe that if something is worth finding, it is worth flicking to the left or right. It started with dating, moved to food delivery, and eventually colonized our social feeds. Now, developer @osmankahraman is bringing that same primitive UI pattern to the world of open source.
His new project, _gitinder, was recently highlighted by the DEV editorial team in their weekly Top 7 roundup. It is a SwiftUI-based iOS application that turns the sprawling, often overwhelming world of GitHub repositories into a streamlined mobile experience.
The Signal in the AI Noise
The DEV community remains one of the few places where human curation still carries more weight than an algorithm. Every week, the editorial team handpicks their favorite posts, a practice that has become a necessary barometer for the industry.
We are currently living through a flood of AI-generated technical content. While it is easy to find a thousand words on how to write a basic function, it is increasingly difficult to find genuine, human documentation of a weekend project that actually works. Curation matters because it highlights the projects that solve niche problems with clever architecture.
When the DEV team selects a post like @osmankahraman’s work on _gitinder, they are not just looking for a finished product. They are looking for the thought process behind the build. In a where documentation is often stripped of its personality by LLMs, these community highlights serve as a reminder that software engineering is still a deeply personal craft.
SwiftUI and the Gamification of Discovery
Building a mobile tool for developers is a risky move. Most of us spend eight to ten hours a day staring at a high-resolution monitor with a mechanical keyboard under our fingers. The idea of managing code on a five-inch screen usually sounds like a recipe for a migraine.
However, _gitinder shifts the focus from management to discovery.
By using SwiftUI, @osmankahraman has created a native experience that feels fast and responsive. SwiftUI has changed the developer experience for solo creators, allowing for rapid prototyping of complex UI patterns (like the swiping cards popularized by Tinder) without the boilerplate that used to plague UIKit development.
For a project like _gitinder, the goal is to make repo discovery feel less like research and more like a game. You see a project, you look at the stars, you check the language, and you swipe. It is a specialized tool for those moments when you are away from the desk but still want to keep a pulse on the open-source community.
The Reality of the OAuth Handshake
Perhaps the most valuable part of the project documentation is the focus on the friction. @osmankahraman was transparent about the hurdles he faced, specifically regarding the implementation of OAuth.
As any senior developer will tell you, authentication is where the fun ends and the real work begins.
Integrating GitHub’s OAuth into a mobile app is a rite of passage. It involves managing redirect URIs, handling secure token storage, and ensuring the handshake happens without dropping the user into a dead-end web view. I have always believed that we should value the documentation of "messy" code more than the polished final product.
Seeing how a developer navigates the authentication friction of a third-party API is far more educational than reading a sanitized tutorial. It reminds the community that even small, fun projects have to deal with the boring, difficult parts of security and architecture. Documenting these struggles is a service to every developer who will eventually hit that same wall.
The Rise of the Micro-Tool
The trend is undeniable. We are seeing a shift toward mobile-first developer tooling.
For years, mobile apps for developers were just watered-down versions of web dashboards. Now, we are seeing the rise of "micro-tools" that prioritize a specific user experience over raw power. You might not want to refactor a massive codebase on your iPhone, but you definitely want to browse trending repos while you are waiting for your coffee.
This move toward mobility suggests that the modern software engineer is no longer tethered to the terminal for every part of their workflow. As Apple continues to refine SwiftUI and mobile hardware becomes more capable, the gap between what we can do at a desk and what we can do on the go is closing.
The success of projects like _gitinder proves there is a massive appetite for tools that make the technical world more accessible and, dare I say, more enjoyable to navigate. The question is no longer whether we can do engineering work on mobile, but rather how we can design interfaces that make that work feel natural.
The "ugly" parts of your code are exactly what the community needs to see. What will you build when you stop worrying about perfection and start focusing on the experience?
