Posts Tagged ‘context’

Always On

Wednesday, February 8th, 2012
A brand-new iPad!

A few days ago my friend Elmo (no, not the one one From Sesame Street) posted this article on Facebook about the power of Introversion.  It’s a thought-provoking piece and, coming from the Philippines, one which spoke to my friend about the nature of Western Civilization (particularly the USA).  The scales in this culture are set up for Extroverts to thrive, and Introverts to adapt.  It’s an astute point.  In fact the article actually quotes a pastor who believes that God isn’t pleased with him because he “likes spending time alone.”  That’s just twisted.

Read of the rest of Always On at Painfully Hopeful

 

No Longer the Age of Bible Apps, Now the Age of Bible As Applied

Monday, November 21st, 2011

A friend and I were talking about a project he and his company were working on and while it was great that they were working on it, I had to be direct and ask him, “why are you building another Bible applicaiton?” According to he and his team, having a Bible application would put them on equal footing with other companies in this space who have applications and have (apparently) made the successful transition from a PC-based product model to a mobile/web-based one.

I shook my head at his flawed logic. “You don’t run to where the puck is, you run to where it would be,” I told him (quoting Wayne Gretzky). The problem with their approach, and many within this mobile ministry (#mobmin) space who are looking for their innovative solution to take the religious world/church/tech world by storm, is that they keep looking to copying current products in order to make a dent or shift in perception. That’s just not how this works.

For this group, I asked why didn’t they go the route that other Bible applicaiton companies haven’t gone, but that very few secular companies would dare go: the Boston Globe/Boston responsive web, subscription web approach (several articles talked about this)? He looked at me with disdain, as he heard some about that project, but didn’t know how far reaching that it went. You see, their team is savy enough to build something like that, but their company isn’t visionary enough to figure out why that works.

Hence the title of this article: the age of bible applications is over; it is now the age of bible as applied in digital spaces.

Am I saying that there is no need for any company to create, recreate, or innovate on top of the paradigm of reading, searching, bookmarking, and collections with Bible apps? No. But, I am saying that if you are a content publisher who bases your content on any of those Bible app paradigms, then you are better off pushing your energies towards developing a product somewhere else besides “let start with a Bible app.”

Antoine: you aren’t even a developer, how can you say such things?

Easy actually. Go have a conversation with someone. Tell me, did you start in the Bible or was the conversation dipping in and out of the Bible at various points with other contexts as the backbone to the conversation? I’ll address a recent conversation from a coffeeshop. The pastor/missionary and I started talking because I asked about his wide-margin NASB that he was carrying. The conversation went into church history quickly from that, then into cultural perspectives of various regions of the USA. Would a Bible app have helped there, or an application that was able to search on topics related to church history which also referenced Bible verses, noted authors, theological paradigms, and denominational statements of faith that added context to the situation. Of course, innovation here would be turning on said app while in the conversation and as it “listened” it would pull a Google/Britiannica/Wikipedia/Wolfgram Alpha and search then display all of the relevant content streams, statistics, and opinions available online or in accessible scholarly collections. If you will a Shazamm for Biblical conversations.

It prbably makes sense why I can say that you can bend beyond Bible applications when I phrase the context like that right? But that’s called research and analysis, specifically, anlaysis of cultural behaviors of communication that rarely go into the development of these kinds of applications (this is how reports like Mobile Lens 2011 were framed). And that’s why we end up with a situation such as what I described with my friend at the start of this article. If you want your product(s) to be of earthly good, then you have to move beyond the age of simply offering just the text. Develop an app that engages the application of Biblical (religious) knowledge first, and then grounds the user in a growing (maturing) understanding of Scripture, church history, and culture as they grow in faith and knowledge.

Anyone want to bet on “Bible as Applied” being the space in which faith-based/religious apps show the most potential for growth in the coming years against simply offering the text in increasingly siloed services?

 

How to Determine Your Audience for a Mobile App, Website, or Service

Thursday, November 10th, 2011

Ok, so you have decided that you will take the jump and build a mobile application or website. And in your analysis, you’ve pretty much established that you already know what kind of content it is that you will serve. So what’s left? Well, deciding who exactly to target your mobile efforts towards is one item. Take a look at this graphic recently produced by Asymco which speaks to the published information about global shipments of mobiles

From this graphic (not to mention the data that went into it) we can get an idea of some potential targets for an application or a website on a global scale. For example, we can see from the blue in the graphic that there’s a considerably larger percentage of persons who don’t use smartphones, though this number seems to be getting smaller on a consistent basis (you won’t hear doomsday analysis of the feature phone market here, the numbers bear this as standing strong for the foreseeable mobile futur – i.e., 3yrs easily).

Coming Down from a Global View to A Regional One

Now, this graphic only helps if you are thinking of rolling out something on a mobile global-reaching basis. For many of you, the reach is considerably more regional, and so information like that which Asymco has provided looks best when put against other data, for example, this information from the IDC:

…In Asia/Pacific (excluding Japan) (APeJ), feature phones recovered in the third quarter on the back of Nokia’s resolved inventory channel issues in China combined with the strong showing of its dual-SIM handsets across emerging markets like India and Southeast Asia. With Nokia fighting back at the Chinese low-end competitors, the proliferation of these smaller brands has slowed as margins hit razor-thin levels. APeJ smartphone growth last quarter was driven primarily by Samsung and HTC, as well as ZTE in China. In Japan,the market rebounded sharply after two quarters of either low single-digit growth or outright market decline following the natural disasters of this spring.

The Western European phone market declined as a result of lower demand for both feature phones and smartphones. The smartphone device type growth was mainly driven by mid-tier Android devices. High-end smartphone growth was negatively impacted by Apple’s fourth-quarter iPhone 4S launch, which caused consumers to delay purchases. Meanwhile, Nokia’s transition from the Symbian to the Windows Phone operating system as its primary smartphone platform led to a transition. Feature phones declined as consumers that replaced their devices upgraded to smartphones while others held on to their devices for longer periods of time. Overall the Central Europe, Middle East and Africa (CEMA) markets showed strong growth due in large part to Nokia’s rebound in the regions. Bucking its global troubles, Nokia had a very strong 3Q11 due to feature phone growth. Its smartphone decline continued, however, but it remained the market leader in the region. Among the niche smartphone brands, HTC did particularly well in some markets, including Russia. RIM continues to make progress in the Middle East and Africa, but fared less well in Central and Eastern Europe…

Read the entire Q3 2011 IDC Press release

Now, this information from the IDC is a snapshot of what’s happening with the entire mobile industry (like Asymco’s data), however gives a more detailed snapshot of what’s happening in Q3 of this year compared to next year, and also considering regional and manufacturer differences. This is solid information, and allows an effort to craft a mobile website or application to center onto cultural and distribution details that are a bit easier to manage (languages, platform focusing, etc).

Identifying Opportunities, Tools, and Your Users

What’s left after this is to look a bit more into what it will take to actually build the mobile application or website. For that information, we have to take a look at a few facts: (a) where are the opportunities, (b) where are the tools, and (c) where are the users.

What are some of the opportunities for faith-based mobile apps, websites, and services?

  • Games
  • Funding (not just fundraising)
  • Group Communication
  • Education
  • Health and Wellness
  • News and Information

Or, what are the categories that see the most application downloads (this information is hard to come by, for example just Apple App Store data here; pulling this together requires some effort)?

Where then can we find some of the tools to take advantage of those opportunities?

Specifically Design for Your Specific User

And finally, we’ve got to define where the users are for our application. Not the mythical user. Not the “if we put an app out there, it will be used because they have a mobile” user. The hard numbers. Who in your communities, areas of influence, have expressed such interest in a mobile solution from you that it has effected the ability of your current media offerings to grow? Or, how has the success of mobile for your competitors/partners driven your customers and stakeholders to question your mobile strategy?

It is here that you will want to start researching your user base (or prospective user base) towards whatever mobile experience it is that you intend to craft. That doesn’t mean that you are designing something to please them (part of the effect of mobile is that you surprise and delight because you offer something people didn’t know they wanted), but it does mean that you have a pulse on what they use, what works, what doesn’t work, and where potential consumers of your mobile lie.

Analyzing your user base might mean digging into information that you already have (website visitor data, attendance data, response data from polls/surveys, etc.). And it also might mean that you need to generate means to learn more about your community (surveys, focus groups, feedback forms for events, etc.). But, you have to identify exactly who it is that will be using your applicaiton. Try creating personas for these specific users and then (before developing anything) testing the ideas that you have against them. Then, when you get to the point of testing and looking for feedback to your application, you have some benchmark against which to determine where you proceed with your mobile activity.

Of course, you don’t have to do this work of figuring out your audience. You could very well be the next Steve Jobs and literally have a intuition towards what will work. You also have to have the discipline to make sure that it does work.

Resources, Encouragement
We have some resources that should help you through this process here. But, as we noted above with looking at your users, much of what you need to know about making a successful mobile applicaiton, website, or service is already within the people you serve. Know them, and you know what works.

 

The Finer Points (and Kerning, and Leading) of Mobile Design

Wednesday, November 2nd, 2011

Font sketch diagram of Nokia Pure font

A large sheet showing the Arabic alphabet is completed with hundreds of Koranic markers. A pair of annotated brackets signify a quote or reference to the Koran, and a series of characters grouped together spells out the salutation – Peace be upon him.   

Nokia Pure has been specifically designed to accommodate the Koran in Arabic, and the Torah in Hebrew, reflecting the fact that in many parts of the world mobile devices have become an important religious resource.  

Now with the first phase of the project near completion, Bruno Maag is looking ahead to the next set of languages. He has started working on Armenian. “Not many people speak it,” he says dryly. 

The result of all their efforts, Nokia Pure, is a humanist sans face font – without serifs but with different weights and thickness on the strokes. Maag points out the small details that make the font unique:

Read the rest of Typographer Bruno Maag on Nokia Pure: Exclusive Interview at Nokia Conversations

This is a lot more than most want to know about fonts; but speaks to just how intricate the mobile environment is. You have to include context in every measure, especially in the case of fonts where you are ascribing literacy to the experience.

 

Siine Writer and UI Design for Mixed Media Resources

Sunday, October 16th, 2011

For a number of years, we’ve been talking about how Bible applications need to do a better job of addressing the non-pastorial perspective for their applications. We’ve talked about both content and the over all user experience, but rarely have we been able to do more than just instigate more chrome, rounded corners, or a faster search. Almost non of the Bible applications currently available take into consideration the fact that there are more people who own and use mobile devices than those that can read (by stat: the Orality Network speaks that about 60% of the world is or chooses to be illerate; there are nearly 55% of the world’s population that has a mobile phone* (hardware, not account) – overlap, not symmetry).

When looking at Siine Writer and its approach to creating a keyboard that’s based around iconography, I smiled because there seemed to be some develoeprs/UI designers who get it – on a mobile device, context-tuned entry is more powerful the less the user has to do to invent the context they are inputting.

So here’s your challenge. You have a library of resources, and don’t have the time to go about creating read-first interfaces that respect every language you are trying to reach. Can you create instead an icon (and color pallete) driven approach that is better able to lead towards that expected experince that person should have towards your application? Do you know the context of those whom you are building this solution for to do this? Or, does your mobile ministry approach need to start more with analysis of the people group, leaving you less time to make mistakes or do extra work?

If you are looking to build or deploy updates to your Bible/Bible-related applications for more than just the 120 or so trade languages, I’d encourage you to take a look at Siine Writer, accessibility best practices (for example, IBM’s listing), and even conversations that designers and others have about icongraphy and culture. Speaking from experience, its very hard to create interfaces that convey meaning when you are used to letters, words, and phrases to do so. However, the Bible, and specifically its application into how it is applied today, endears us to have to consider context just as much as we’d consider content.

For those of you already thinking and working down this path, here’s a recent tweet with some links to icons, icon galleries, and icon design practices that should add to your efforts:

Khoi Vinh (@khoi) – Helpful replies to my earlier tweet about icons: iconfinder.com, iconspedia.com and a post at Owltastic. Thanks everyone.

~ Siine Writer found via Ubergizmo & Techcrunch

*Update: got a question via email about the 55% number. That data is in the ITU datasets. However, it was also published by Tomi Ahonen in Feb 2011.

 

Retweets of the Week (Jan 30 – Feb 5)

Sunday, February 6th, 2011

Once again our Retweets of the Week feature highlighting some of the items we’ve retweeted in the past week.

If you’ve got something you deem worth sharing, be sure to point it out to us (@mobileminmag) or use the #mobminhashtag if its directly related to mobile ministry efforts.