Continuing on Resolution #4: Raising the Bar on Mobile UX Standards

MMM on the N8 - Share on OviA few articles ago, we went a bit on a extended talk about the All Books Bible Reader that I’m developing for personal use. After talking through the technical features and goals, we wrapped up with a statement talking about clarifying the goals and features for your mobile(-first) endeavors, and being mindful of the specific UX needs mobile presents:

Mobile-Friendly and Personalization As Core to User Experience
The takeaway from this project is that there have been several methods to engaging Bible/document reading, social/offline networking, funddraising, and other initiatives in mobile ministry. However, even if you nail the features, at some point in the maturing of that person using the service or the company offering it, doing something that fits the mobile context and that’s personalized will come forth. It might not be the aims of your projects initially, but do know that eventually, they all point to these goals needing to be met.

With that starting point, we want to highlight a bit more about Mobile (UX) Standards and in referencing that All Books Project, and some of the items to keep in mind whiile moving forward in your mobile initiatives this year and beyond.

Mobile UX Standards
It is assumed that the idea of what makes for a great mobile user experience is pretty easy – just grab yourself an Apple iPhone and use it for a week or two, then switch to another platform for the same amount of time and note how often you frown, toss the device, or find yourself limited in some fashion. And while we can agree that Apple’s iOS platform does make for some suitable claims towards what makes a good mobile experience (consistency, quality, variety of applications, etc.), its not the only mobile experience, nor does it answer every question anyone developing, selling, or using mobility will ask towards.

Over at UX Mag, an excellent article talking about mobile standards beyond the styleguides, frameworks, and guidelines that would usually reference as we develop apps makes an excellent point:

…Apple, Android, and Blackberry all do a great job of sharing standards with their developer communities. They share detailed guidelines on standard UI elements, the associated terminology, and their behaviors, and give usage examples for the UI. However, what they don’t do is string them all together into patterns.

  • What happens after you click this button?
  • How should these messages change in context of the task?
  • If you’re opening a document online, should it open in a new window or in the current window?
  • When and where do error messages appear in a form?
  • Is that different or the same in a wizard or series of forms?

These are the questions that designers and developers spend most of their time toiling over—the little things that pull UI elements together into a full interaction. And these are also the questions that the OS standards do not cover. This is a key gap in standards for designers and developers that can be filled by a new custom set of guidelines, which further save money and time in development efforts and add value to the existing, basic OS standards.

*List formattting added

Beyond simply saying “we want to go mobile” or “let’s use this or that to go mobile,” you really have to ask core questions about the interaction and steer adamantly towards those goals. What happens when you don’t steer specifically towards the goal, understanding these kinds of questions throughout, is that you end up with a glut of features, conflicting brand messages, dis-engaged users, and missed opportunities to deliever the depth of the Gospel that you/your group intends that application or service to portray.

Start With A Picture, Ask Until the Ink Dries
With the All Books Project, I started with an idea in my head (more efficient Bible reading on my personal mobile device that wasn’t limited to closed-licensed texts), and started scraping together what was needed and what wasn’t in order to make that happen. I boiled things down to two features: reading and searching. And then I took to one of my favorite apps on my iPad (Tactilis) to sketch some reasonable ideas towards how I would get there.

UX Flow for All Books Personal Bible Reader - Share on Ovi

This UX flow document is my gage of whether I’m meeting my goals. If I am, then the lines here continue to make sense. If not, then I go back to this document towards what I (originally or later modified) thought and ask whether my thinking should continue down the path I’m or, or get back on course to what was drawn.

One of the pieces of interaction that I’m aiming for with All Books is a sliding popup for when I click on those verses with footnotes. The feature is harder to implement than its drawn. But, because I’m clear towards what I want to do when the popup is envoked, how its interacted with, and how it is dismissed, I can keep my programming focused and timelines (generally) well kept.

A Good Mobile UX Is Also Your Feedback Loop’s Process
In designing an effective mobile user experience (UX), you also need to take into account the development/design of your support infrastructure. As we talked about once before when developing mobile web apps, you need to have in place the resources not just to build the app, but to support, maintain, and maybe even update it.

Build, Get It Out There
After I was able to figure out my issue relating to displaying content within All Books, I needed to start using it. It didn’t matter that there was (noted) performance issues or the inability to see the footnotes as I’d like. Getting it into my normal use allows me to catch things that I’d not considered in my initial development and design, and then adjust on the fly without effecting other pieces of the project. For example, I realized that for all the work I did with makng this a spatially-orienting design, I still felt lost when navigating. The insertion of colored indicators on the section that I was within helped this considerably, and it was a few lines of code to add to do this (1 CSS class and 1 JS statement).

With that: do you have your mobile UX resolution refined now. Its the middle of January, don’t let too much longer go by.

Being Acquainted with the Challenges of Mobile as Ministry

Screenshot of PocketBible from ChurchMagIt probably doesn’t need to be stated because its often felt. But, I do think that in the race to use this technology for casues that forward faith, we sometimes lose sight of the fact that there are very few specalisists, fewer folks implementing, and even fewer folks that can communicate their story as they walk through this. In fact, its a common refrain in many calls/meetings about mobile ministry that you just won’t find best practices and case studies. There just aren’t enough people doing it that are able to compose best practices and cases studies. And that’s a shame. The current state of affairs invalidates the approach of mobile in ministry (or mobile as a ministry tool) in the minds of some because of the lack of this information; even though context dictates a different perspective should be adopted until those experiences and materials are grounded.

Having said such, when you are able to hear the successes and challenges present, its best to hightlight them. As community of technologists and believers see these stories, then we can start talking about solutions and making things more eficient for all. For example, in this snippet, we hear very clearly the challenges presented to one of the veterans in this space, Craig Raridian of Laridian Bible Software:

…Mobile software development is a challenge for small shops like ours. There are no good solutions. Consider the fact that when we started Laridian there were two dominant platforms: Windows CE and Palm OS. Both were programmed using the C++ programming language that we already knew from our prior experience programming for Windows PCs. Today the two dominant platforms are iPhone and Android. iPhone uses Objective-C and supports non-user-interface objects created in C++. Its operating system is based on the familiar Mac OS X. Android uses the Java programming language and has a proprietary operating system that is still evolving. And if we throw Windows Phone into the mix, it uses C# as its programming language. The result is that we can’t be like diplomats who have to learn the language of their host country, but rather we have to be like a representative to the United Nations whose headset is broken so he has to understand every language being spoken by all the other delegates…

Read the rest of this article (which talks about the progress of Android development of PocketBible).

These challenges aren’t unfamiliar, nor isolated. In the history of craft and creative fields. Having a capacity across several simlar or disparate fields is normal. It is very common for people engaged within these fields to be going at it alone, or in resource constrained fields. I’ve certainly felt this in full since branching out to do MMM full-time. There’s essentially this challenge of not just producing what you are gifted to do, but making sure that you can relate that creation/creative event to the social, financial, and spiritual needs that are also present.

This is one of the reasons why in our recommendations for building a mobile website or application, we specifically state that there should be a small team of people dedicated to prayer (and emotional/mental) support for the effort. You just can’t take on an effort that has technological and spiritual components and expect it to go on passion alone (speaking from experience here, have been totally burnt out from doing MMM, often).

You have that resources challenge. Are there enough people, finances, skills, or even just materials, around you to create/sustain what you are working towards? Many times, you might start with sufficient resources, but unforeseen circumstances push those reserves to an empty point. That’s a tough place to be – especially when you’ve not made a shipping product yet. I won’t even go into the resource challenges when you are marketing/selling skills and experience. So let’s be a bit more realistic, and discerning of the pressures we are putting on technologists and ministers when ascribing our energies and attention towards this very new field called mobile ministry. There are challenges that just can’t be swept away, or waited for others to do. The folks out here doing this are cutting the ground. Their challenges are as real as the opportunities.

Where’s My Advent App/Calendar?

Screenshot of Waiting in Joyful Hope Advent calendar appOne of the kinks that you tend to run into when you have a Sunday schedule like ours (i.e., visiting many churches/fellowships per month), is that of the holiday season. You have some groups which do a great job of trying to center their communities on the “holy” part of the holidays. Then, you have others who seem like they are doing everything they can to get rid of that materialistic mentality all-to-common for this time of year. IMO, if every church simply observed Advent, that might not be so hard to do.

So, one of the many items that I’ve kept my ears to the ground for in non-Catholic/Orthodox/Lutherian churches is how they go about Advent. Unfortunately, there’s not much of a mention of it. So, how about we help that out a bit?

Here are a few that I’ve found:

Now, you could simply just be publishing an Advent calendar via Google Calendar (hint, hint) and showing your community how to add this to their mobile devices, but these apps might make it a bit easier.

What are some of the applications or calendars that you folks are using for Advent to keep Christ’s evenutal coming in the front of the eyes of your communities?

From the Perspectives of Teachers

A few years back, SBL Bible Software Shootout was taken for a very different direction when it was realized how well Bible software on mobile devices had evolved. This came across as a strange “finding” from our perspective seeing how long we’d been speaking of the virtues of using mobile devices for Bible studies considering the ease of access to content, the efficiency of the UI, and generally speaking, the cost of the products.

Yet OliveTree and others showed very well that while they might not always be the preferred tool for creating sermons and studies, they were no less capable than “full” software packages commonly found on pastor’s desktops and laptops. This year’s SBL Bible Software Shootout reintroduces the mobile component – especially because of the popularity of the iPad – and gets an additional curveball in some responses towards using this software not from a company’s perspective, but from an instructor’s perspective.

From this year’s SBL Bible Software Shootout 2: Revenge of the Teachers, Biblical Studies and Technological Tools offers some commentary towards these presentations:

Logos: Two professors from Calvin College, Dean Deppe and Carl Bosma, presented on their use of Logos in their classrooms. Calvin College has a 2 week gateway course that is a required part of the curriculum to introduce Logos to the students. An important aspect of the instruction is both learning how to use the program and to start the process of using it to take notes.

  • A 1 hour introduction
  • Four 2 hour sessions explaining features with MDiv students
  • Three 3 hours sessions with MA students.

Deppe showed examples of how he has used Logos. (Cf. Deppe’s All Roads Lead to the Text: Eight Methods of Inquiry into the Bible for his work on using Logos for exegetical examples. I have now acquired the book and will provide a review here, hopefully before the new year.) He demonstrated how he thinks in terms of various lenses for viewing the texts using various Logos tools: Personal Book Builder to collect notes, Collections for searching, Passage Analysis, highlighting, layouts, visual filters including sympathetic highlighting, tools that can be used for students who don’t know Greek or Hebrew, etc. He showed an interesting example of highlighting of verb tenses in Romans 7 along with quite a number of layouts he has created for working with grammatical, exegetical, background, related texts (e.g., DSS, Josephus, Pseudepigrapha).

Bosma showed how he used Logos for notetaking and linking to local and web resources.

Again, there’s nothing radically new here, unless you look a bit deeper into what’s happening. The SBL Shootout is usually composed of companies skilled to develop towards the tnedencies of academics, not necessarly the most mobile-friendly audiences, and definitley one with a different paradigm towards teaching emthods. There was a heavier emphasis on the presenters here to be led towards applying the text of Scripture, but also demonstrating their methods towards dissecting and interpreting the meaning of the text based on what’s worked in instructor-led settings (languages, cultures, etc.). If you will, you are getting an opinion out of the actual use of the product, not simply the features that the developer wants to most demonstrate (biased towards their marketing/compitence). When you get the presentation of the capability of the software from the perspective of the teacher, you begin to see a bit more how this is used in such settings (wealth and warts) and can start to discern a bit more contexually the strengths of the software versus the stregths of the teacher.

What’s not clear from the commentary is how the reception was from students who engaged instructors that prepared these materials. Were the classes better managed? Or, where there additional challenges getting (some/most) students information in a manner that didn’t just work best for teaching the concepts, but also their devices? Clearly, the software is in a better place. And now hearing the academicly-tuned Biblical/religious community share their lessons-learned is great. The question is how can these persectives be rolled up into something of a working document for best practices for others who wish to have some insight or clarity towards instructing to this depth from a mobile device, connected software, and theological perspective.

I like some of the discussion here about the utilization of Apple’s iCloud. In some conversations with ministers recently, iCloud has come up as something they very much liked because it meant that they were better able to take what they needed from a laptop setting and have that on their mobile or tablet as they went. Again, this isn’t a radical change from what we’ve demonstrated and talked about here (its really syncing, though more than just calendar/contact data as many of you have done via Exchange, PalmSync, etc., without the fun of pushing a button to say so), but the acceptance of the behavior to prepare and be ready to teach a lesson is something to note. On our end, products such as Dropbox and Idea Flight have been quite useful towards instructor-led engagements. Though, simply putting your items on a server and then provoking interaction from that point has also been quite demonstrative.

Read the rest of the commentary about the SBL Shootout 2 from Biblical Studies and Technological Tools and then consider how you are leveraging these technologies to teach clearer or better. It might be that you create something similar to a traditional lecture-based course, or, that you might make something more along the lines of the Cybermission’s Mobile Ministry Training Course which goes towards a different direction of technical competence for instructors. In either respect, going mobile isn’t an excuse for not being able to handle teaching a lesson – the tools are there, are your teaching chops and students up for the rest?

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

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?

Siine Writer and UI Design for Mixed Media Resources

http://www.youtube.com/watch?v=Ae4_e0bRsHQ

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.

Looking at the Perspective Amazon’s Kindle Gives

When I am at a coffeeshop, I usually have my mobile to the side of me and my iPad in front of me -occasionally with my wireless keyboard. At times, at least when I’m typing on the keyboard, I’m stopped to ask if I like my iPad, or how I get along with the keyboard. On one particular day, a woman asked me my opinions on the iPad as she was considering one. It just so happened that less than an hour before she asked me that, Amazon announced its new slate of Kindle reading devices (Kindle, Kindle Touch, Kindle Touch 3G, and the (color/Android) Kindle Fire). I mentioned to her that she might want to consider the Kindle – and it was apparent that she had. And then showed her the image seen on this post – her expression and the conversation that ensued afterwards got me thinking about how leaders, technologists, and then everyone else tends to consider technologies like what is exposed with Amazon Kindle.

For instance, the woman asked me what it is that I do with my iPad (reading, drawing, then everything else was my response). I showed her my artwork, and then the notes that I’d written at a recent church visit. The notes impressed not just because they were handwritten, but because she could see the point in not just having an electronic bible, but an ability to write notes, highlight, and then have those available on any computing device she owned. It sounds almost normal to many of us, but the perception that you can disconnect content from the devices you read it on is still a new idea to many.

She asked about saving the data on my iPad and how much space it takes. I explained to her how I don’t save a lot on the device itself as I use the entire Internet as my hard drive. We talked about how Amazon, Dropbox, Microsoft, and others essnentially give you their servers to use as the hard drive. In that case, its not always a limitation of the space that you worry about, but how you are able to control access, security, and what you are comfortable with storing on another company’s hard drives (servers). She noticed that on the pages for the new Kindles that there was no mention of the size of the internal storage and asked why that could be. I told her how Amazon is positioning their servers to be your hard drive – essentially making the Internet your hard drive. Her expression again amazed at not considering before that you could take what seems to be a normal computer function and turn it on its head.

So what becomes of how we talk and demonstrate Biblical texts? Could we have moments where instead of simply telling people to turn to such and such a passage that we could have shared that bookmark via YouVersion or another Biblical service. Or, maybe as a minister who is an aspiring author, do we learn and utilize services like Amazon Kindle Direct Publishing and Lulu to disseminate our locally-created materials instead of or in addition to the traditional publisher route? Obciously, there isn’t a need to do these kinds of things all the time, but devices like the Kindle will mean that we do have to consider that our use of the technologies available will endorse the purcahsees that many are already making.

Or, we can choose to not see efforts like the Kindle as being useful or beneficial for our respective audiences. Which is ok. But, if you are in the business of content creation or teaching, what kind of perspective will that lend to those whom you say you lead?

~ picture via Gizmodo