Monthly Archives: July 2012

Sharing a Profile in the Connections Mobile App

Here’s a cool feature you can use with the Connections app for Android. If you need to exchange business card information with another mobile phone user, you can share contact info in 2 ways:
1. Send a Vcard through email, sms, etc. through the Android Share intent.
2. Create a QR code that could be scanned by the user on their phone.

Here’s how you do it:
Open someone’s profile via search or in your list of network contacts. Press the hard menu button and choose the Share item.
Image:Sharing a Profile in the Connections Mobile App

The next menu popup is when you choose how to share. Choosing Share brings up the standard list of Android app options.
Image:Sharing a Profile in the Connections Mobile App

Choose Scan contact info to generate a QR Code.
Image:Sharing a Profile in the Connections Mobile App

Now, another mobile phone can use a QR code scanner to read the information and add it to the local contacts.

(On iOS, the option to share the vcard is there, but not to generate the QR Code.)


Chris Reckling

Chris Reckling | 24 July 2012 04:30:00 PM ET |

Custom URLs in IBM Connections Mobile Apps

UPDATE: See this technote for a complete, up to date list of the urls.

Connections mobile apps for iOS and Android include ‘custom urls’ in the app. Custom URL schemes are like a little command API into the app. Basically, your app creates a namespace that it registers with the OS so when the URL is called on the device, it knows to execute the command. These work on both iOS and Android. 

Use Case 1. Deployment scenario. Since Connections is typically deployed on your own servers, with their own unique urls, this is a place where users can immediately fail, either by not knowing the correct Connections server URL or their user name/password. Now you can provide specific instructions to your users in a custom HTML page they can access from their mobile devices. And to make things even easier, all they have to do is tap on the custom url that you provide to properly configure the device. Here’s the custom URL format:


ibmscp:// is the base URL that will open the app with optional parameters that will create the account with the specified information, if it doesn’t already exist.

For example, you could include in your deployment HTML page a link to the app store, to download and install the app along with a custom URL to configure it. The following URL launches the app and creates an account named “Renovations Connect” to the server named “ and fills in the user name field with the string “”.


Then the user simply has to complete their name and enter their password to log in to Connections from the device. We have been using this internally because we install new builds of the apps every day and this makes it much easier to do. 

Use Case 2. App integration. The second scenario has to do with opening a specific Connections service in the app. Here are the custom URLs for you can use to call into the Connections app. There are some interesting things you can do with these. I’ll look forward to hearing about it. For example, if you have an app with people’s names in it, you could link over to their profile in the Connections app.

Launch the Connections app to My Communities page.

Open Connections to a specific communities by uuid for the last logged in account.

Specify a particular account if more than one on the device.

Launch the Connections app and show profiles.

Launch the Connections app and show profiles on an existing account.

Launch the Connections app and show a specific profile for the last logged in account.
or if you know the email address of the user.

Launch the Connections app and show a specific profile for an existing account.

All of this information will be in the Connections Wiki soon, but I thought I would get it out there now.

Chris Reckling</accountserver=encoded_url&accountuser=encoded_username></accountname=encoded_account_name>

Chris Reckling | 13 July 2012 03:00:00 PM ET |