Mobile Ministry Magazine (MMM)

Posts Tagged ‘Logos’

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.

 

Splashtop Remote, Bible Library Servers, and Mobile Accessibility

Friday, January 20th, 2012


Last month, we had a post from LaRosa Johnson talking about his new Asus Transformer Android tablet computer and how he planned to use it work and Biblical studies. Of the latter, he was doing something pretty neat in that he would use the tablet to remotely log into his laptop to be able to use the desktop Bible software packages that he has there. We’ve found another example of this over at Biblical Studies and Technological Tools where instead of a tablet, we’ve got an Android smartphone, and the software being used is SplashTop Remote Desktop. Here’s a snippet of that experience:

In the past I have used Logmein for remote access to the various family computers I maintain. Even the basic free account lets me take over a computer and run programs on it. It works great and is secure. I will continue to use it for such maintenance tasks. Note that this can work the other way around, and what a program like this allows me to do is run programs that are on my home system from any other computer. As long as I have my home system on and Logmein enabled, I can remotely connect to my home system and use my installed programs like BibleWorks or Logos. I’ve also used it to grab files I’ve forgotten on my home computer when I’m at school. (I now use SugarSync to keep my systems all in sync via the cloud. It’s a wonderful thing.) It’s a little slow to use Logmein this way, but it works. What this also means is that I can use the web browser on my smartphone and see BibleWorks on my phone. I say “see,” because without the use of a mouse on my phone, I really can’t do too much. Logmein does have an Android app ($29), but I just don’t use it that much, especially on my phone, to buy it.

Read the rest of BibleWorks and Logos on Android (sort of…) at Biblical Studies and Technological Tools.

Now, this sounds like something that would be only useful in areas where wireless bandwidth is accessible and there’s some technological savy on the part of the person putting this together. But, I can’t help thinking that at some level, it would make a lot of sense to see something like Bibleworks, Logos, etc. offered in a “server package” where you purchase “seats” and those authenticate mobile devices are able to use it. This would be no different than what we see with CRM, task management, Intranet, and office productivity suites (Salesforce, Basecamp, SharePoint, and Google Apps to name a few).

A difference in the application here though would need to be that Bible software suites doing this would want to explore being usable in different streams. For example, something like having the BibleWorks install and UI sitting on a Seagate GoFlex Satellite, with anyone accessing that hard drive/access point being able to “see/read” BibleWorks on their device, but it is being served from that single point. There’d also be something like Logos’ Biblia that could be explored where a license for an organization could make available to authenticated seats some measure of the Logos library. Or, finally we could see the BibleWorks/Olive Tree/Logos/etc. move to a model of use where instead of purchasing and downloading a product, that people and organizations purchase access to a virtual desktop of sorts which would allow them (a) access to the library and (b) multiple devices which can access it per use account. Now that I’m thinking about it, it would be really neat if I could recreate the mobile web server and then host the bible project I’m working on from it… uhmmm

In whatever case, its pretty neat to see these kinds of access choices taken when it comes to Bible software. We shouldn’t limit mobile just to “what’s designed for the small screen” when its clearly possible for that small screen to access a bit more. What is worth being explored though is how we can better enable mobile to be a key to a content library, whether or not those with the devices have the financial means to access the content or not.

 

From the Perspectives of Teachers

Tuesday, November 22nd, 2011

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?

 

Raising the Bar for Bible Apps

Monday, August 1st, 2011

logos bible app screenshotWe come down pretty hard on Bible apps here at MMM. Either they aren’t focused enough, or they have so many features that people get lost in using them (a product focus issue). Nevertheless, there’s always room to talk about what they do well and what can improve from there.

What Mobile Bible Apps Do Well

Its well agreed, even when comparing leading Bible apps to other eBook readers/applications, that Bible applications are well developed for their target. From the handling of notes, to offering different views to compare content. Bible apps seem to run in the lead in respect to having the kind of user experience (UX) that is responsive to many of the needs of the Bible reader.

Footnotes, cross-references, and some even integrate image support better than you’d see on the Nook, Kindle, or other electronic reading devices. Add to that, an large body of content (usually priced appropriately), and you basically have a niche in mobile Bible apps that can pretty much sustain itself – for a little while longer at least.

And then you just have availability. Just look at our Bible apps listing – there’s at least one Bible app (and therefore several Bibles and other religious literature) available for nearly any mobile device. There are even SMS and audio-only options for those folks that would prefer something a bit more responsive to those reading and learning styles. I’ve been around mobile devices and software for a very long time, I don’t know of any genre outside of games that covers such a diverse range of devices and usage types.

What Mobile Bible Apps Don’t Do So Well

Where mobile Bible apps falter, and this is true for just about anything attached to the publishing world, is in two specific areas: access and consistency.

In respect to access, we still have the situation with Bible applications that content is locked to specific applications. Though we are getting better with this – just recently, we saw the release of Simple Bible Pro for HP webOS devices which uses Laridian’s licensed content. Instead of a situation such as a single vendor needing to making an application for (and then support) various mobile platforms, another company has made the application, and there was some cross-licensing able to be done here. This doesn’t happen enough, and therefore Bible software companies are dealing with access the hard way – building platform-centric silos. And in most cases aren’t even taking advantage of respective platform strengths when doing so.

Then there’s consistency. I’ll let Kevin Purcell from Christian Computing Magazine take it form here:

…While all of these are good apps, they have one thing in common. They lag behind their iPad/iPhone counterparts running on iOS in features and sometimes in stability. Let’s take Olive Tree Bible Reader as an example. The iOS version is rock solid and has a lot of great features. It has split screen capability and markup features like book bookmarks and notes. The most recent stable Android version only recently added some of these features, but not all of the iOS features are present yet. Logos has a good iOS app. They haven’t even re-leased an Android version yet, but do have a public beta (see link above). Their beta is little more than a book reader. You cannot compare translations, there is no Passage Guide or Word Study Guide and like the iOS version it has no note taking feature, bookmarking or highlighting. Laridian’s Android app is an alpha, not even a beta. I downloaded it and they have a great start, but it is definitely missing most of the great features of the iPhone version…

Read the rest of his July 2011 article (PDF)

Feature parity is important whether you are doing simple reading, or diving into a more in-depth study with your community. This aspect really hits folks who move to another mobile device and have gotten used ot a specific feature.

How Then to Raise the Bar

This is the part where you make the call. Being that mobile Bible apps have this base, where do they need to improve or become better in your perspective? Let’s hear what you have to say, and maybe the voices can get some of these excellent companies to consider tweaking their offerings in that direction.

 

After You’ve Gained the Knowledge, Then You…

Monday, July 25th, 2011

Image: Dual pane view of Bible+ showing KJV and ESVA recent tweet by the Folks at Audio Bible/Faith Comes by Hearing (@audiobible) got me thinking (again):

If u could carry the Bible around with u in more than 500 languages – like in your pocket – how would u use it? #Hmmmm #GreatCommission

Original tweet.

I used to carry 1, then 2, then 15, and at one time over 100 Bibles around with me on my mobile devices (thanks Bible+). At the time, I justified it because I was (a) reading/studying Scripture a ton more than I do now, and (b) I interacted with several people who “heard” the Scriptures best in the translation they most used. Being that I was also at college during this time, it felt like the right way to approach speaking spiritual matters in a clear and consistent manner (1 Cor 14:1-19).

I don’t carry as many Bibles with me these days. In fact, until recently I didn’t carry any versions on my mobile (still no app, but I’ve got a Bible), and the ones on my iPad are the same in each Bible app or website (ESV, KJV, NET, and a few others). I’ve got less a need to carry as many versions of the Word as I do the onus to live as much of the Word so that when asked, I can give the appropriate answer to my faith (1 Peter 3:15-16). That, and the consistency of being in or near connected spaces allows me to search quickly from a series of websites when needed, or just make a note for something to come back later to.

That’s not the case for all folks. Many of the frequent travelers and missionaries I’ve met would jump at the ability to have Bibles and other texts in as many languages as needed, and at a moment’s notice. Their interactions almost require it of them. And when they are able to have something that speaks right to their audiences, it makes living among mixed groups that much easier to manage. When they don’t have that content, or even the ability to get a clear translation, their relationships to people and environments suffer.

But such use speaks to that end of things – where the tweet asked “how would you use it?” Many of use have libraries of Bibles and other content in print on bookshelves (digital and otherwise), but what have we done with it besides making it decorative? Have we taught someone to read, or took the time to use those resources to tutor people who are studying those subjects we’ve collected? Have we engaged the cultures beyond the pages and held the kinds of conversations that would amplify or change our opinions of those cultures, people, and events? Or, is it just a number?

In grade school, many of us learned about the terms kinetic and potential energy. Kinetic energy is identified by its impetus to move – the energy immediately before movement happens. Potential energy, on the other hand, is energy that is stored and is usually static due to its position or configuration. You’ve got that neat Olive Tree, Logos, YouVersion, or Bible.is app with hundreds of Bibles and other materials ready to be used. Are you in the process of transferring that energy into the lives of others, or are you configured simply to display the potential of what can be?

 

A Healthy Dose of Rambling

Friday, June 3rd, 2011

N8 and Ice Cream - Share on OviHaving been on the road for the better part of the past seven days, the news queue here has been a bit on the shrinking side. We’ve been keeping things going on Twitter (@mobileminmag) and engaging in some smaller conversatoins there. Here’s our attempt to get you caught up with where MMM.

Apps and Challenges

For example, in one aspect of the past week’s trips, Brett (one of the contributors here) and I got a chance to connect and talk about how we’d like learn better cross-platform development techniques for some of the content that we own or read. We got into talking a bit not just about apps, but things like QML, HTML5, and even the mobile web server. Being on an edge of mobile use, we’re finding that its not just a matter of having access, but there’s sometimes when ownership and accountability needs to also be a part of the pie.

That goes into the Kiosk Evangelism project that MMM has been a part of and some of the challenges there. As a project, its going through a leadership transition. Some of the questions though influence practices and understandings. For example, if creating a mobile-tuned service (such as the digital library component of Kiosk Evangelism), does it make sense to go native with an app, or use the browser and possibly something like Modernizr to create a UI that plugs into several systems an scales well. Does such a UI need to also be offline-context-sensitive, and if so how?

There’s also the challenge of owner rights. Church Mag recently opined about jail breaking and it caused me to go back into the archives a bit and relook at just how free we are to customize devices or interfaces. Certainly, there’s a challenge all around if you want to do something right.

Some are better than others with challenges. I’m always impressed at the energy and execution behind Logos and YouVersion and their latest projects serve as a solid measure of encouragement. Of the many support and feature updates for the application and service, I’m impressed the most with how YouVersion is paying attention to how we hear the Word. Audio and native language features ring most relevant for a lot of folks. Logos has released Vyrso which is basically a reader that goes beyond just Bibles. Through that system, I wonder how many budding authors will take up the challenge towards creating content that empowers and reveals the impact of the Gospel? Seems like as good a channel as any to do so.

Events and Movements

On the other side of happenings, there are several events and movements happening that all have something to do with how we approach (or at least view from our perspectives) mobile ministry.

The Uplinq Conference recently concluded. We attended this last year and had a great time as a part of the WIPJam Panel talking about opportunities and challenges for mobile developers. This year, the conversations started on mobile and there was a lot of innovations presented in mobile and blended reality computing.

Due to scheduling, we cannot attend this year’s Muther Hackathon, but we certainly want you (or your dev team) to get out there to it. If you would like passes, shoot us a message or tweet as we have a few free ones to give away.

MMM will be at the ICCM conference in Indiana in a few weeks. We’ll be speaking on a session about mobile ministry, actually breaking down that sketchnote that we’d posted here last week. We’d love to connect with you if you are going to be there.

And don’t forget about the Carnival of the Mobilists. Though its now on a once-per-month posting queue, the selection of articles that makes it to each Carnival seems to get better and better. This month No. 249 is being hosted over at Francisco Kattan’s site. Now that I’m not in my car or in front of folks for a few hours, its definitely something that will enter my rested reading time.

MMM Team and Role

Personally, I’m having fun with a new mobile (the Nokia N8) and some of the challenges around using it with my personal approach to mobile. That part has been fun, but its also led to finding some nuggets that would be valuable here.

Our team has taken some heavy shots personally and spiritually lately. Its been an honor to keep them lifted in prayer, but having been sick last week definitely showed me just how fragile all of us can be.

What is MMM’s role? We point to what’s happening. Unfortunately, we’re also finding that people sometimes need help with finishing what they started or just telling their message in a manner that’s able to be heard. To some extent, we are a media initiative, and to another, we’re just some hands and feet to some parts of the Body that want to move forward with a pure and honest depiction of the Gospel in their contexts.

That makes for a wide and deep role for us. And honestly, one that a single person has trouble with, let alone a small team. If you’ve been interested in getting involved with helping us share the stories of faith and technology, get in contact with us. If your heart is in other areas, and you’d just like to know how we can be supported, get in contact with us.

We’ve got some house-cleaning to do on some of the pages here we know – and we’ll get to those items in time. In the meantime, there’s a Body using this tech that’s asking for the road that isn’t techie or overly theological. We’re helping to cut a trail, rambling on about what we find as we do ;)

 

Addition of Ink Makes Tablet a Better Bible?

Wednesday, May 25th, 2011

HTC Flyer screenshot of Bible app with ink, via Mobile GadgeteerThis past weekend, Matt Miller opined that the new HTC Flyer Tablet might make for the right approach to being a digital bible replacement because of it’s inking ability. During this specific look at the HTC Flyer, Matt notes just how well the ability to ink on the screen adds to the experience that many Bible reading applications already offer.

Spending much of my reading time on a tablet, I can relate to how well this can work within many application environments and communities. And as Matt also shows, using a service like Evernote along with is could also pull some of those behaviors that some are used to (writing in margins, etc.) into a digital domain to take advantage of some of the capabilities that paper just wouldn’t have.

This is a use case more centric to tablet (and even laptop) use. And so we should be careful not extrapolating it to every mobile device that can handle ink. Inking, specifically as we are looking at it here, takes advantage of the larger screen spaces tablets offer, and could also blend some spatial interfaces not used as well on small mobiles.

If inking could work, what are some ways that you could see the exploration of Scripture draw someone into a better understanding of it, or even help a small community better understand how to study the bible together (a community sketchnote if you will)?

 

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

Mobify