Android Tutorial
In this tutorial, we will use the Android SDK to integrate Connect into your application.
Our frontend SDKs handle getting an authorization code representing a vehicle owner’s consent for your application to interact with their vehicle for the requested permissions. In order to make requests to a vehicle, please use one of our backend SDKs.
For security, token exchanges and requests to vehicles should not be made client side.
Overview
- The Mobile Application launches a
Chrome Custom Tab
with Smartcar Connect to request access to a user’s vehicle. On Connect, the user logs in with their vehicle credentials and grants the Application access to their vehicle. - The
Chrome Tab
is redirected to a specifiedREDIRECT_URI
along with an authorizationcode
. This will be the custom scheme set on the application. The Smartcar Android receives the authorizationcode
in a view listening for the specified custom scheme URI, and passes it to the Mobile Application. - The Mobile Application sends the received authorization
code
to the Application’s backend service. - The Application sends a request to the Smartcar API. This request contains the authorization code along with the Application’s
CLIENT_ID
andCLIENT_SECRET
. - In response, Smartcar returns an
ACCESS_TOKEN
and aREFRESH_TOKEN
. - Using the
ACCESS_TOKEN
, the Application can now send requests to the Smartcar API. It can access protected resources and send commands to and from the user’s vehicle via the backend service.
Prerequisites
- Sign up for a Smartcar account.
- Make a note of your
CLIENT_ID
andCLIENT_SECRET
from the Configuration section on the Dashboard. - Add a custom scheme redirect URI to your application configuration.
- Add the
app_server
redirect URI from Setup step 2. to your application configuration.
For Android, we require the custom URI scheme to be in the format of sc
+ clientId
+ ://
+ hostname
.
For now, you can just set it to sc
+ clientId
+ ://exchange
.
Please see our Connect Docs for more information.
Setup
-
Clone our repo and install the required dependencies:
Do not “checkout from version control” with the Getting Started repo in Android Studio, as it will not open the proper module.
-
Open
getting-started-android-sdk/tutorial
in Android Studio as an existing project and build from existing sources. Android Studio should automatically import the required dependencies and build gradle. We’re settingapp_server
tohttp://10.0.2.2:8000
to pass the authorizationcode
from the Handle the Response step later on in the tutorial to our backend.strings.xml
Build your Connect URL
- Instantiate a
smartcarAuth
object in theonCreate
function of theMainActivity
.MainActivity.java
The Android SDK does not support simulated
mode at this time - only test
and live
.
Feel free to set testMode
to false
where you instantiate your SmartcarAuth
object to
connect to a real vehicle.
-
The Android application will launch a Chrome Tab with Smartcar Connect to request access to a user’s vehicle. On Connect, the user logs in with the username and password for their vehicle’s connected services account and grants the application access to their vehicle.
To launch Connect, we can use the
addClickHandler
function that oursmartcarAuth
object has access to.MainActivity.java
Registering your Custom Scheme
Once a user has authorized the application to access their vehicle, the user is redirected to the REDIRECT_URI
with an authorization code
as a query parameter.
Android applications use custom URI schemes to intercept calls and launch the relevant application. This is defined within the AndroidManifest
.
Handle the response
Using the Android SDK, the application can receive the code in the SmartcarCallback
object passed into the SmartcarAuth
object.
Launching Connect
Build your application in Android Studio and click on the Connect your vehicle button.
This tutorial configures Connect to launch in test
mode by default.
In test
mode, any username
and password
is valid for each brand.
Smartcar showcases all the permissions your application is asking for - read_vehicle_info
in this case.
Once you have logged in and accepted the permissions, you should see your authorization code
printed to your console.
Getting your first access token
After receiving the authorization code
, your iOS application must exchange it for an ACCESS_TOKEN
. To do so, we can send
the code to a backend service. Let’s assume our backend service contains an endpoint /exchange
that receives an authorization code
as a query parameter and exchanges it for an ACCESS_TOKEN
.
Notice that our backend service does not return the ACCESS_TOKEN
.
This is by design. For security, our frontend should never have access
to the ACCESS_TOKEN
and should always be stored in the backend.
Getting data from a vehicle
Once the backend has the ACCESS_TOKEN
, it can send requests to a vehicle using the Smartcar API. The Android app will
have to send a request to the backend service which in turn sends a request to Smartcar. We have to do this because
our frontend does not have the ACCESS_TOKEN
.
Assuming our backend has a /vehicle
endpoint that returns the information of a user’s vehicle, we can make this query in
our completion callback
and start another activity
to show the returned vehicle attributes.
Setting up your backend
Now that our frontend is complete, we will need to create a backend service that contains the logic for the /exchange
and /vehicle
endpoints.
You can use any of our backend SDKs below to set up the service starting from the Obtaining an Access Token step.
When setting up the environment variables for your backend SDK, make sure to set REDIRECT_URI
to the custom scheme
used for this tutorial i.e. sc + "clientId" + ://exchange
.