Explore deep linking between multiple mobile apps such that they can be used in the context of a singular ministry experience
Mobile deep linking is the ability to provide a URI (Uniform Resource Identifier) that can access a screen or resource inside a native mobile app. This challenge is an invitation to explore deep linking between multiple mobile apps such that they can be used in the context of a singular ministry experience. We are interested in how you might improve the user experience using deep linking concepts for ministry applications.
Links help users find and share content online. Unlike most of the information on the internet, content within apps may not be easily accessible since normal links don’t work well on mobile device. This lack of access and hindrance to sharing is more than an inconvenience. It creates poor user experiences and ultimately limits the ability to connect with your community. The end result is a lack of penetration of promising apps and the result is that content goes unnoticed.
In the context of the World Wide Web, deep linking is the use of a hyperlink that links to a specific, generally searchable or indexed, piece of web content on a website (e.g., “http://example.com/path/page”), rather than the website’s home page (e.g., “http://example.com/”).
We are interested in how you might improve the user experience using deep linking concepts for ministry applications. Some potential benefits of deep linking between Cru apps include:
Better discovery of other “family” apps to the user.
Convenient transitions from one app to a specific location in another app.
Allows content to be shared that is contained within a native app.
Allows content to be consumed within the native mobile experience that was designed for it.
Increased opportunity for personalization across apps.
For “peripheral” apps, it may provide an easier, cost effective way to connect users to “core” ministry content and functionality.
Allows each app to be focused on a single purpose (and thus a better design), then call on another app, if needed, for the separate purpose the 2nd app was designed for.
We encourage you to develop an app that takes advantage of the modern deep-linking approach.
A potential example
We would like the mobile app, “Jesus Film Project”, to seamlessly allow the user to go from watching the Jesus Film in a particular language to sharing the Gospel via the mobile app, “God Tools” with the click of a button. Ideally, it would go directly to God Tools in the same language and jump to the first page of “Knowing God Personally”. Designing the user experience with various compatibility issues would be helpful. Creating a test app that would simulate the jumping seamlessly to God Tools would be a great proof of concept. Here are links to the God Tools source code:
iOS (Objective-C): https://github.com/CruGlobal/godtools-ios/
iOS (Swift 3.0): https://github.com/CruGlobal/godtools-swift/
Other possible mobile apps that could be used in this Deep Link App challenge – linking to or from “Soularium” or “Perspective Cards”.
Data, APIs or Resources
What is deep linking? (branch.io)
Deep Linking Definition (Wikipedia)
Why you should care about Deep Linking (branch.io)
Additional Articles Related to Deep Linking (American Library Association)
“Deep Linking” in the World Wide Web (w3.org)
The Mobile Deeplinking project (high-quality source of documentation, sample code, and SDKs)
iOS Deep Linking Library (github)
Android Deep Linking Library (github)
Welcome to the Indigitous Community! We are pumped you want to be part of whats going on in here. Join so you can list projects, make comments, submit posts and connect with other members in the community groups. Get involved in something bigger!