airg.github.io

Organization page

View on GitHub

airG

airG is a pioneer in the mobile software industry having released its first mobile application in 2000. Since then the company’s products and services have been used by over 100 million consumers globally, generating more than $1 billion in revenues. Our products inform, entertain and connect.

airG Open Source

airG Open Source is a collection of open source libraries, published under the Apache 2.0 License.

Android Async

The airG android async library is a group of utilities for easier management of asynchronous tasks. The main components of this library are:

  • ThreadPool allows you to easily run tasks on a background or the main (UI) thread from anywhere.
  • AsyncHelper helps you determine (and assert) whether a specific piece of code runs on the UI or background thread.
  • Promises allow you to run tasks asynchronously and be informed when each task is completed, cancelled, or failed.

Android Countries

The airG android countries contains a complete list of countries, their alpha2 and alpha3 codes, international prefix code, flags (48dp), latin names, and local names.

Android Device

The airG android device library provides a collection of utility methods for getting runtime information about the device such as API Level, Camera availability, Connectivity, Soft Keyboard utilities, and generic hardware information

Android Logging

The airG android logging library provides formatted and tagged logging for Android so that you can

  • Tag once and log often
  • Use String.format style formatting for log messages.

Android Miscellaneous Library

The airG Miscellaneous library gives you useful bits of functionality that are too small to be their own library, but useful enough to be needed in more than one place.

Android Runtime Permissions

The airG Runtime Permissions library provides an easy way to handle handle Marshmallow’s runtime permissions from any Fragments or activity, paving our way to everlasting Android fame.

Contributing

Contributions are appreciated and welcome. In order to contribute to any of the above libraries, follow these easy steps:

  1. Write a clear and concise description of your change refer to issue tracker ids where available (ideally, you’d file an issue with this information).
  2. Fork the repo
  3. Make your changes (besure to format your code according to the included codestyle settings)
  4. Add tests or usage examples where applicable (i.e. update the tests and samples) and make sure they pass.
  5. Add the original repo as your upstream repo (git remote add upstream <repo-url>)
  6. Rebase (skipping this step is an easy way to disqualify your commit).
  7. Submit a pull request and reference the issue id as well as the paragraph in #1 above.