Skip to content
Xamarin bindings for the Curbside SDK
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
samples
src
.gitignore
Curbside.Xamarin.Bindings.sln
Curbside.Xamarin.Full.sln
Curbside.nuspec
LICENSE
README.md
azure-pipelines.yml
build.cake
build.sh
nuget.config

README.md

Curbside SDK for Xamarin

The Curbside ARRIVE SDK delivers reliable arrival prediction. Battle-tested by millions of customer arrivals in real world commerce, ARRIVE sends an accurate alert before arrival and gives you true visibility into customer ETA and dwell time. ARRIVE hooks easily into a mobile commerce infrastructure and on-site apps or POS for notifications.

This is the source code to Xamarin bindings for the Curbside SDK. Currently the bindings are created for Xamarin.iOS and Xamarin.Android projects.

There are also some simple bindings for io.reactivex.rxandroid which is a dependency of Curbside's Android SDK.

There are sample reference apps under samples built using the Xamarin bindings for iOS and Android

Curbside Xamarin Bindings Nuget package

Building

There is a Cake build script which handles building the project and the nuget package.

The Xamarin.iOS bindings need to be built on a mac.

You can build everything by running:

sh build.sh

Arrive SDK Prerequisite

Register for an account at Curbside Platform. Sign in and do the following:

Running

  • Grant permission to use location services
  • Add a tracking identifier
  • Add a track token
  • Add a site identifier that was created on the Curbside Platform.
  • Start track
  • Go on a test drive

View User Trip

  • Check ARRIVE dashboard to see your current location and to note that your status changed from In-Transit to Arrived.
  • Use the monitor app to view detailed information about your arrival.

Quick Start Guides

The documentation is mostly in Objective-C, Swift and Java, but the Xamarin/C# APIs are almost 1:1 with the native APIs,so the docs should still be quite useful.

License

See the repo root directory for licensing information.

You can’t perform that action at this time.