Mobile Ministry Magazine (MMM)

Posts Tagged ‘cross-platform development’

PearlVault and A Potential Solution to Notes and Electronic Bibles.

Monday, March 12th, 2012

Last week, we were contacted by Aaron Frey, who has begin a Kickstarter project called PearlVault asking to help get the word out about this project. We’ve not talked about some of the struggles with notes and electronic Bibles in a long time (something from 2008, and another something from 2006), and so getting this note about PearlVault reopens that conversation alongside the other collaborative features many have asked for in the Bible software domain.

About PearlVault
From the Kickstarter page:

…This project will create a web portal where you can take your Bible study notes so that they are searchable, taggable and indexed according to Bible references. It will also allow you to attach notes to words from a particular Bible translation–or even words from the original Greek or Hebrew. It will be optimized for the easy discovery of past notes whenever you study that same passage/word/topic again. It will also be optimized for use on mobile devices so that, even when you are away from your desktop, you are never away from your Bible notes. And PearlVault, should this project succeed, will be available for the rest of your life, independent of whatever study environment you use otherwise.

Essentially, your Bible reader of choice will utilize PearlVault as the syncing-linchpin for your notes content between Bible apps. Not a bad idea, and definitely down the road towards how we’ve supported similar-featured projects in the past in regards to being able to have more liberty with the content you create or own.

[Click here if unable to see the video embedded above]

The Challenge for PearlVault
The challenge for PearlVault is getting enough buy-in and interest from Bible publishers and software companies to support this effort. Hence, the Kickstarter project. Your notes would be stored outside of the application, so that in the case you’d decide to move to another Bible software suite, that you’d not lose the content you’ve already created. As it stands right now, of the Bible software programs which have a notes functionality, many times this is a feature within the application and you usually need an additional piece of software (or in some cases a full PC) to take the notes from the application and put it into a more generic format.

The other challenge actually comes from the users of Bible software. Much like with versions of the Bible, software can become an issue of comfort and attachment. And unless circumstances dictate otherwise, many people will stick with the same Bible software family for many years. Now, when they do change, there’s some general flow towards how they evolve with Bible software:

  • Many start with a free, gifted, or low-cost package; as they become more skilled in using the software, they may opt for the paid content or a paid Bible app with a similar user interface (UI);
  • Some start with a recommendation of personable apps such as Olive Tree, Pocket Bible, YouVersion, Logos, etc.; sometimes with the encouragement to try a few of these before settling on one; in the meantime, notes and other content is being generated that won’t transfer to the app they settle to
  • The last step forks one of two ways: either the person is such the student of the text (w/pastorial responsibility) that Logos and their deep library is the only option, or they are a mild-academic in terms of the text, looking to some of the lighter Logos packages, or the wares of Olive Tree, Accordance, or eSword (depending on content needs); the latter group is likely to use more than one Bible software package

Having said this, the challenge is actually quite apparent. Even if a person moves up and through several leagues of Bible software, they will have some (not major) difficulity in keeping their notes attached (programatically) to the text. Now, do know that we are talking about a specific set of Bible software users here, its not the normal course for non-pastor/teacher types to go through several iterations of software – folks just aren’t that patient. Those who are, and who have a genuine joy for searching the Scriptures so that this issue of notes between apps comes into play, just have different needs that’s not been met as of yet which PearlVault seeks to do.

More Information, Supporting PearlVault
PearlVault is using Kickstarter in order to raise the funds needed to support the building and maintaining of the service which will be hosting these linked notes. It is also in place to log the interest of people for such functionality. By placing your donation into the project, you help Frey’s discussion with Bible publishers and software developers who sometimes don’t want to look outside of their products, but do know that the user at times will.

Some additional information about PearVault and Aaron Frey’s motivations for the project have been detailed in an interview over at Christiandroid. Definitely check that out as it goes into a bit more than the Kickstarter page towards the project’s vision and aims.

And finally, support Aaron. Having been on the side of trying to just make Bibles available between platforms, I admire and affirm Aaron Frey’s project and what it aims to do for everyone who gets value out of storing, rereading, and sharing Biblical notes.

 

WIP/VDCC Recap: Cross-Platform Conversations

Friday, September 24th, 2010

This week, MMM participated with WIP at the Verizon Developer Conference. We were invited by WIP to annotate the UnPanel session on day two, but ended up contributing towards one of the session conversations on cross-platform development.

As many developers find out quickly, and some users have figured out as they have gotten into Google Android-powered mobile devices, or have moved from one mobile platform to another, there are times when applications or content just doesn’t work so well. We kind of think about data as being something that is easy to transfer from one platform to another, but such doings are ripe with challenges and opportunities. At the Verizon Developer Conference (VDCC), we participated in facilitating a few panel discussions on cross-platform development and some of the challenges. The following three items came up the most in these conversations.

Fragmentation
The number one issue that developers said that they faced when trying to take an application, or apply a service across several mobile devices, is this issue of fragmentation. Fragmentation is basically when you have a single platform (for example Google Android), but there are variances in how that platform is implemented across devices. These variances can include input mechanisms (touch, keyboard, etc.), application program interfaces (APIs) which talk to hardware or services, and even carrier-specific functionality which doesn’t line up across the same device on different carriers (for example, cell ID information).

What happens is that when a new update to a platform comes out, or an offshoot of a current platform is produced, developers have to code their applications and/or services to account for these changes. And especially in the case of non-Apple iOS devices (where things are commonly similar across all of these devices), this causes the developer to have to spend more time acquiring the resources to test and approve their software across these variant platforms.

One of the things that frequently came to mind is the challenge that many of the developers of Bible software have towards this issue. I wonder how many of you deal with fragmentation, and whether you share the opinion that this isn’t something that’s going away, but might be solved with better tools?

Communication
Another impact to cross-platform development that was talked about in these sessions was that of communication with the carrier. For example, while fragmentation is an issue, developers who are proactive would like to hear from the carrier something towards devices, APIs, etc. which might not be support or might change when platforms are updated so that they can be faster able to adapt their products to those new devices.

On the carrier side, its difficult to respond to everyone individually, and so carrier involvement in developer networks, standards bodies, and a general attention to being open in communication is something that Verizon and others are doing a lot more of. The challenge for them (of course) is to be open without impacting their abilities to continue to offer differentiated products and services.

To you who are developers, or even users, what kinds of communication strategies would you like to see from developers, carriers, and other service providers to better allow you to make the move from one platform to another? Or, does this even matter, do you just need things to work?

Up-to-Date Market Information
Of the many issues that developers can have in making sure that they have a solid application or service, one of their challenges is making sure that they have up-to-date market information about platforms. Verizon’s Developer Center has some upcoming things in this area, as do some other developer networks. But, this is still the challenge.

As a resource and analyst, one of the challenges is always to promote the statistics and the information that allows developers to make sound decisions towards where they can make solid applications. For example, you will never hear MMM tell you that Symbian isn’t a good platform to develop for, unless your target audience for your content is in an area where Symbian is not a primary focus for the carrier/user base. In the same accord, as a developer, you have to broaden your research and analysis horizons beyond just those persons who are “louder” about what positions they have, and make sure that you are seeing those folks who are holding a contrary viewpoint.

That being said, it is difficult for many people to both develop an application/service, and keep on top of market trends. What would you like to see more of in terms of getting up-to-date market information for your respective target audiences? Where do you go for information now, and are those areas sufficient?

Conclusion
During the time at the Verizon Developer Conference, I was exposed to a subset of some of the general opinions that I hear developers go through. Much of MMM’s viewpoints are formed and spoken of in global contexts – this was a chance to center in on a specific US (only) carrier and what issues matter to them.

Stay tuned as in a future post we’ll talk some about these specific challenges and opportunities. And what you can do as developers and as a notable target market (re: faith-based organizations) to make your applications more visible and profitable both spiritually and economically.

 

Mobify empowers marketers and developers to create amazing mobile web experiences. Tap to learn more

Mobify