A significant number of developers use as their primary development platform to host their repositories, manage their projects and collaborate with different teams. Although the website is optimized for mobile devices, there is no official native mobile app for the platform. Fortunately, GitHub provides excellent GraphQL and REST APIs that have allowed teams and individuals to create all types of integrations and extensions to enhance the functionality of GitHub to fit their needs.
Every currently available third-party mobile client for GitHub that I tried to use was either too simple, required payment for the most basic of features or didn't provide the best user experience. This gave me enough reason to build , an open-source mobile GitHub client, with React Native.
Why React Native
One of the primary concerns with teams needing to build native mobile applications is becoming familiar with all the different technologies. Swift and Objective-C are both languages supported by Apple that allow you to build applications for iOS. Java and Kotlin are some of the programming languages that can be used for Android development.
Instead of relying on WebViews and a bridge to access native resources such as the camera, React Native allows developers to write in the same way they would to build a web application with React, but to produce a mobile application with purely platform-specific native components. React Native apps are virtually indistinguishable from applications built with native components.
Github in Your Pocket
GitHub just recently announced the release of , a completely redesigned GitHub Desktop experience built with . With no current official native mobile, GitPoint aims to similarly extend the workflow of the platform to our mobile devices with a complete native mobile integration.
I started building this application on my free time when I started working at Rangle in January. Without any previous React or React Native experience, I slowly began with a number of the initial screens that showed repository and user data. With no understanding of Redux at this point, everything was still under local state.
At this point, I was happy with using local component state entirely throughout the application until I started noticing two things:
- Passing props throughout a number of components was becoming unwieldy
- GitPoint did not work offline whatsoever
Including a state container at this point made sense. then allowed me to persist and rehydrate my redux store to AsyncStorage so initial notifications and event data still showed without a working internet connection and when initial requests are being fired. If you’re interested in exploring offline persistence for your Redux state, I highly suggest taking a look at both the redux-persist as redux-offline libraries.
Currently, GitPoint leverages GitHub’s REST API v3 with plans to slowly migrate to their GraphQL API v4. Moreover, the majority of the application is styled using , an excellent UI library that provides a number of different components you can use.
In roughly two months of launching, the app has garnered over 200,000 Twitter impressions, 5000+ users, 2200+ GitHub stars, 33 contributors, 190+ issues and 150+ pull requests. The reception has been overwhelmingly positive and the community support has been amazing. GitPoint would not be close to where it is now without the help of some .
We have an active community on and there are a significant number of improvements and features we plan on adding. This includes refactoring changes such as rearchitecting our state logic and leveraging GitHub’s GraphQL API as well as a large number of feature requests we plan on addressing in future releases. A large majority of the contributors have never done React or React Native development before, and it’s amazing to have new developers learn so much as we work on making the platform better. Having a team of contributors happy to be part of a community is just awesome, and there is no better feeling waking up in the morning to read a tweet like this:
If you happen to have questions, feedback, feature requests or anything at all, please don’t hesitate to . We think GitPoint provides a lot to its users already, but we’re only just scratching the surface.