I am very curious about this topic (much like Judy Headrick!) and was just discussing something possibly like this with Frances Gilgunn. 

When you say targeting exclusively are you doing any specific activities that you could share here? Are these brand new users and your training with a mobile-first mindset? 

As a recent Iglooer, I find myself using the mobile version more often because the feed lets me consume a lot of diverse information and single out what matters to me quite quickly. I find with the website view I move to very specific areas (almost like "safe nonexploratory areas") and treat it more like a retrieval service of what I need.

We are not using the mobile app with our primary Igloo instance due to security constraints with multi-factor authentication to protect our proprietary content.

But we have a large audience that does not regularly access our primary instance due to the multi-factor authentication requirement ... because they use customer provided equipment and/or networks they either cannot or it is difficult; and a second audience that is in the field most of the time.  So, both of these audiences are more likely to use a mobile device to access our company information, if only they could ...  To accommodate this, we stood up a separate instance for non-proprietary content where we can use single-factor authentication from a mobile device. 

Our thought is that these two audiences should be able to get our company news and general employee communications from this new instance via mobile device.  There are times when this content links to our primary instance for more information or a full news story, which then requires multi-factor authentication, but we are trying to get them the bulk without that requirement.

As for email notifications, yes, that is built in, but we have taken steps to eliminate email notifications.  We are relying on My Feed and the app notifications exclusively.  Our thought is that this audience will only use the app and never access this instance from a browser.  Part of the reasoning for this is that since the app is single-factor authentication, it cannot be coupled with their company email because that requires multi-factor and the app launches the local device personal email instead.  

I get what you mean about the feed Tom.  I, too, have thought about that lack of a feed in the browser.  Maybe your Pulse page would serve that need?  It does not for me since I'm an admin and can see everything and you cannot limit it to only what you want to see there.  I find I don't use it regularly, but early on I did set up a dashboard and set the sources for the content I wanted to see in a feed.  

I'd be happy to hop on a call to talk about the mobile app if anyone is interested.  Continuing the conversation here is good too.

Thank you for going into greater detail and sharing as much as you did, this really helps me understand the dynamic going on. I love the idea of being able to surface the core company news and have tethers/lifelines for employees who are inside the walls of a customer. With the primary instance links being embedded in the mobile instance, does your mobile user base find this to be too much friction? Or have you found users go back later and consume the richer article? 

How are you measuring the value of the separate mobile setup or are you incorporating it into the complete measuring of the platform?  Is there any discussion around deepening the use of the mobile, like adding tools required to do the job or resources that won't break the compliance/privacy rules?

 I am in a similar boat to you with regard to my access and hearing all the noise with no ear muffs!  

We are in the very early stages of our pilot ... we just launched a couple of weeks ago.  In addition to tracking usage metrics, we are holding focus groups with the pilot participants to get their feedback.  Only one of those sessions has been held so far and I won't have the summary notes from those until more are held over the next few weeks.  

Let me know if you'd like to talk through your and our use cases to better understand each other.  This week is no good with the 4th of July holiday, maybe next week or later in July?