Add a ‘Buy’ Button to Your App (No Coding Required)

Today URX is releasing an enhancement to our iOS and Android SDKs that lets you create buttons in your app tied to actions in other apps — like buying a concert ticket in SeatGeek or booking a reservation in OpenTable — without having to write any code and without having to build a user interface from scratch.

On iOS (Android instructions here), simply drag and drop an object onto an interface in Xcode, enter a few words in the object’s inspector and you’re up and running: the object generates an app icon, a call to action (e.g., “Buy Tickets in SeatGeek”) and a deep link to an action in an app that’s complementary to the content your user is viewing at any given moment.

Infusing buttons with this kind of intelligence is now as easy as dragging the URX frameworks into your project in Xcode (or downloading the frameworks with CocoaPods), exposing an object’s identity inspector in interface builder and filling in custom fields like:

  1. Action Type: determine a set of apps to potentially show in the button, each related to an action like buying something, listening to music, traveling somewhere or reserving something.
  2. Domain Filter: optionally specify one or more apps you would definitely like to show in the button and resolve users to.
  3. Near Filter: specify a location you would like the in-app destination to be related to.

You’ll also want to include a text query with your button which you can do by right-clicking the button in interface builder and dragging its context to an element on the page that contains text.

(STEP-BY-STEP GUIDE TO ADDING A URX BUTTON ON IOS)

For example, say you’ve created a music news app and you’d like to use URX to render a button that links your users to a musician’s upcoming concerts in a ticketing app.

Using fields in the button’s identity inspector, you can tell URX that you want your button to surface a deep link to concerts located in a specific city (Near Filter), limit tickets to those which are available in a specific app like SeatGeek or Stubhub (Domain Filter) and only show tickets for a specific musician whose name appears in the <artist-name> label on your page (Initial Query).

You might also experiment with changing the button from one that lets users buy concert tickets to a button that lets users listen to music simply by changing the BuyAction to ListenAction (Action Filter).

With URX, you can monitor engagement with the button including clicks on the unit, resolutions into a recipient app and down-funnel events in the recipient app — such as sales or signups — resulting from traffic that originated in your app.

Behind the scenes, the URX search engine leverages a knowledge graph that sits atop more than 100 mobile services, accepting text-based queries with information like keywords, location and time, turning those queries into entities and concepts and mapping them to the most logical next step for your users.

The science is rather mind-blowing and it’s all in service of making your app more awesome and making it easier than ever for apps to partner with each other.

We hope you’ll give URX Buttons a try or create a UI of your own with the JSON-formatted data returned from our API. And please give us feedback as we work to make the process of integrating mobile services into your app as seamless as possible.

Check out the URX documentation to get started or get in touch by e-mailing us at info@urx.com.

Other Helpful Links:

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.