Skip to content

marecar3/WordPress-Android

 
 

Repository files navigation

WordPress for Android

Build Status

If you're just looking to install WordPress for Android, you can find it on Google Play. If you're a developer wanting to contribute, read on.

Build Instructions

  1. Make sure you've installed JDK 8 and Android Studio, a Standard Setup would work.
  2. Clone this GitHub repository.
  3. Copy gradle.properties-example to gradle.properties.
  4. In Android Studio open the project from the local repository as a Gradle project (this will auto-generate local.properties with the SDK location).
  5. Make sure you have an emulation device setup in AVD Manager (Tools → Android → AVD Manager).
  6. Run.

Notes:

  • To use WordPress.com features (login to WordPress.com, access Reader and Stats, etc) you need a WordPress.com OAuth2 ID and secret. Please read the OAuth2 Authentication section.

Once installed, you can now build, install and test the project from the command line:

$ ./gradlew assembleVanillaDebug # assemble the debug .apk
$ ./gradlew installVanillaDebug  # install the debug .apk if you have an
                                 # emulator or an Android device connected
$ ./gradlew cAT                  # assemble, install and run unit tests

Directory structure

|-- libs                    # dependencies used to build debug variants
|-- tools                   # script collection
|-- gradle.properties       # properties imported by the build script
`-- WordPress
    |-- build.gradle        # main build script
    `-- src                 # android specific Java code
        |-- androidTest     # test assets, resources and code
        |-- main            #
        |   |-- assets      # main project assets
        |   |-- java        # main project java code
        |   `-- res         # main project resources
        |-- vanilla         # vanilla variant specific manifest
        `-- wasabi          # wasabi variant specific resources and manifest

OAuth2 Authentication

In order to use WordPress.com functions you will need a client ID and a client secret key. These details will be used to authenticate your application and verify that the API calls being made are valid. You can create an application or view details for your existing applications with our WordPress.com applications manager.

When creating your application, you should select "Native client" for the application type. The applications manager currently requires a "redirect URL", but this isn't used for mobile apps. Just use "https://localhost".

Once you've created your application in the applications manager, you'll need to edit the ./gradle.properties file and change the WP.OAUTH.APP_ID and WP.OAUTH.APP_SECRET fields. Then you can compile and run the app on a device or an emulator and try to login with a WordPress.com account. Note that authenticating to WordPress.com via Google is not supported in development builds of the app, only in the official release.

Read more about OAuth2 and the WordPress.com REST endpoint.

Google Configuration

Google Sign-In is only available for WordPress.com accounts through the official app. Contributors can build and run the app without issue, but Google Sign-In will always fail. Google Sign-In requires configuration files which contain client and server information that can't be shared publicly. More documentation and guides can be found on the Google Identity Platform website.

How we work

You can read more about Code Style Guidelines we adopted, and how we're organizing branches in our repository in the Contribution Guide.

Need help to build or hack?

Say hello on our Slack channel: #mobile.

FAQ

  • Q: I can't build/test/package the project because of a PermGen space error.
  • A: Create a gradle.properties file in the project root directory with the following: org.gradle.jvmargs=-XX:MaxPermSize=1024m.

License

WordPress for Android is an Open Source project covered by the GNU General Public License version 2. Note: code in the libs/ directory comes from external libraries, which might be covered by a different license compatible with the GPLv2.

Packages

No packages published

Languages

  • Java 91.9%
  • JavaScript 3.6%
  • Kotlin 2.9%
  • PLpgSQL 0.5%
  • Ruby 0.3%
  • Shell 0.3%
  • Other 0.5%