Tag Archives: Android

Galaxy Nexus & Nexus 7 First Thoughts

This review was also published at Urban Scholar

I’m an Android purist. Nearly every device I’ve owned has used a vanilla install of the Android operating system. I started off with the original Android phone, the G1. Upon upgrading that phone, I opted to move to the G2, the G1′s successor. I later purchased an ASUS Transformer (with keyboard) from a fellow techie & friend (which I talked about here last December). While not a vanilla install, it was as near to stock as it could be. It was a great device, but ended up giving it to a friend as a means of “investing” into their business efforts & making them a bit more mobile.

This summer I felt that I was in the market for a new phone and wanted another Android tablet, so I started looking at devices. Being with T-Mobile at the time, I could have simply waited & gotten a new phone on contract in September, but I was also tired of paying $120 a month for my cell phone service & looking to move to pre-paid. With that in mind, I wanted to make sure that the phone I purchased would be able to work on a pre-paid carrier’s network (in my case Simple Mobile). My initial thought was to get my hands on an imported ASUS Padfone, but that would have cost me nearly $1,000 for all of the pieces I would have required (phone, tablet dock, and keyboard). I ruled that out due to expense. With that ruled out, I started to look at the unlocked Galaxy Nexus HSPA+ from Google. Quite frankly, I couldn’t beat the price for an unlocked phone that was also a Nexus device. Then Google announces the Nexus 7, and I was sold. I already owned a full-sized tablet (iPad 2, courtesy of my employer) and wanted something with a smaller form factor to be used primarily as a reading device. The Nexus 7 fit the bill perfectly, especially with its price & vanilla Android install. At the end of July, I purchased both the Galaxy Nexus HSPA+ & the Nexus 7 (the 8GB version, also with the case).

Having had the devices for a few weeks now, these are my first thoughts on both devices.

Galaxy Nexus HSPA+

Since I’ve been an Android user since their inception, I knew that I would have no problem with this device. Although, there were a few things that I took into consideration when buying the phone. With the G1 I loved having the full QWERTY keyboard, which influenced my decision in purchasing the G2 when it came time to upgrade. With Swype installed on the G2, I rarely used the slide-out keyboard. Keeping this in mind, I knew that I could opt for a phone without the keyboard, which would give me a much slimmer form factor. Having used those two models of phone, I felt comfortable with the screen size & thought it was perfect for a phone; so, I wasn’t sure how I was going to feel about having a phone with larger screen real estate. To state it simply, I’m enjoying the larger screen size, almost to the point of wondering how I operated without it. It was also to my benefit that the phone came with the latest version of Android (Jelly Bean) and I can be assured that I’ll get the latest updates direct from Google. That is a huge plus.

The only real downside that I’ve found to the phone is the storage. In my G2 I had been using a 32GB microSD card, which was primarily used for housing my music offline. The Galaxy Nexus has no expandable storage & only comes with 16GB of storage. This was the only thing that gave me pause in purchasing this device. I was able to get past this quite quickly though. With my entire music collection being in the cloud via Google Music, I felt comfortable enough to know that I could stream all of my music at any time (especially since in most places I have Wi-Fi for streaming). For those times that I need music offline, I still have plenty of room to download a playlist or two that has the albums that I’m feeling at any given time. This is exactly what I did when I had to take a trip to Nashville for work a couple of weeks ago.

In terms of my usage of the device, it really hasn’t been any different than how I used my previous Android phones. For me, my phone primarily serves as a messaging & communication device, as well as my music player. With that in mind, I’m a heavy SMS, Twitter, Facebook, Google Talk & Google+ user. Music is handled primarily by Google Music, with DoggCatcher for podcasting and Spotify & Pandora for “radio” streaming. Aside from that, it’s used for the occasional game (Words & Hanging with Friends), and of course as a Bible in my pocket (Logos, Olive Tree & YouVersion).

I’m quite pleased with the phone and think it was a great purchase. The build quality is solid and it is by far the best phone I’ve ever owned & would recommend it to anyone that wants a solid Android phone that they can take anywhere in the world.

Nexus 7 Tablet

As I stated above, I had owned an Android tablet before & had been wanting another one since giving my other one away. I also knew that I wanted a tablet that had a smaller form factor so that I could use it as an e-reader. Yes, I have an iPad that can do all of these things; but, when it comes to reading (especially in bed or one-handed) the iPad can become heavy very quickly, which makes reading for extended periods a chore. Thus, a smaller & lighter tablet would be great for doing extended reading, which is something that I’ve been trying to spend more time doing. All of these things taken together, along with my love for vanilla Android devices, made the Nexus 7 the perfect device for my needs. I wanted to get the 16GB version, but opted for the 8GB model since it was in stock & I convinced myself that I could live primarily in the cloud and would be working in conjunction with my phone.

The easiest way that I can sum up my use of the Nexus 7 is to say that it has easily replaced my iPad as my everyday tablet. Since owning the Nexus 7, I have rarely had need to pull out my iPad, which was primarily for work purposes. Everything that I used my iPad for I have been able to do on my Nexus 7, even without being hindered by the 7-inch screen size. For example, this was written entirely on my Nexus 7 (in Evernote, using my Apple wireless keyboard).

With only 8GB of storage on my Nexus 7 it has forced me to be creative with how I use the device. This means that I am making sure that I am primarily using this device for what I purchased it for, which is reading. The majority of the apps that are installed are for reading and/or productivity. Very few games are installed, and primarily are games that look & work better on a larger screen, or ones that are very light on space (like Sudoku).

My reading apps consist of the following: Google Play Books, Nook, Kindle, Google Reader, Logos Bible Software, OliveTree, YouVersion, Marvel Comics, and Comixology. This combination allows me to read books from just about anywhere. The Nexus 7 has also become my primary Bible, as I can read & study the Bible very easily (while only downloading resources locally that I use everyday or am presently reading). Using Logos, everything I do (notes, reading position, etc.) syncs with my desktop install of the software. Plus, I can get my comic book fix quite easily (again, only downloading the comics that I’m reading at the time, leaving the others in the cloud until needed).

Other apps that I use frequently include: Play Music (streaming only), Evernote, Chrome browser, WordPress, Google Drive, Dropbox, andYouTube. This allows me to access my files when I need them and create new ones that I can access from anywhere.

All in all, the Nexus 7 has been a great device and I’ve really enjoyed my time with it. Being such an avid Android user who is steeped deeply in the Google universe, this tablet has been perfect for me. The form factor is great for long periods of reading, and it is still large enough to serve as a productivity tool while on the go. It is definitely a worthy replacement for my iPad, which I rarely use anymore.

Final Thoughts/Looking Forward

To say that I’m pleased with the Nexus 7 & Galaxy Nexus would be an understatement. These are both very solid devices & work beautifully for someone who is always connected and doesn’t mind living in the cloud. The Galaxy Nexus is a wonderful phone and you can’t expect to find such a powerful phone that is unlocked and able to go nearly anywhere for such a low price. Seriously, $350 is a steal. The Nexus 7 is a steal too. For the hardware that gets packed into this device, you cannot go wrong in spending $200 on this tablet, even given it’s 7-inch size. It’s a worthy upgrade to spend the $50 more & get the 16GB version (which I may do down the road).

I look forward to using these devices for quite some time and fitting the needs that I have in my life, both personally and professionally.

Both the Galaxy Nexus (349 USD) and Nexus 7 (199/249 USD) devices can be purchased from the Google Play Store.

Screen Sharing

Screenshot of Antoine's iPad w/artwork
I didn’t have this one prepared beforehand. You see, I have been trying to answer a question about screen sharing from my iPad over the web to other devices. If you will, a reverse Skype or WebEx experience. However, I keep running into the limitation not so much of there not being an app, but that technically, it’s a problem that can’t be solved on the iPad (conventionally; this is probably possible by jailbreaking). It is the kind of thing that gets me thinking again about the way that we use technologies of the screen, and then how we adjust to them or they adjust to us.

Now, in the past, issues with connectivity or media could be solved with adding some software or even a hardware accessory. Need to game, get a better mouse. Need to present, get a web cam and some recording software. Usually speaking, how we go about connecting to one another is a case of taking some base that is close to perfect, and then adding onto it whatever else is needed. I know though that at some point, that approach changed for me. If the device couldn’t do it with minimal changes to the physical space or my behavior, then it was probably acting a bit outside of its design, and I would become more the administrator rather than the user/creator.

So I go back to this question of screen sharing. Now, I could potentially do something where I use the native screen shot taking ability of the iPad to snap screens (press the home button, then the power button at the same time and wait for the photo click) and use Dropbox and a shared URL to a photo gallery to share screens. There wouldn’t be much live interaction happening, but it would pass the screen’s content along. If in the same room as the audience, I could use software like Idea Flight or Mobile Presenter Pro, or even just the native sharing abilities of iOS in AirPlay, to so the screen shot sharing. Again doable, but a lot more steps. Or, I could move to an Android or BlackBerry tablet, where this software might exist and I would just have to deal with any bandwidth or security concerns once I use the screen sharing software.

Living mobile-only, and having moments where by mobile I am looking to solve issues of training, support, and mobile-enablement, these are the kinds of problems that come up and are worth experimenting and investigating to be solved. Then again, it’s only a matter of sharing a screen. Perhaps there is something better than can be done to transfer the message.

Conversations or Challenges

Doodle God screens, via Symbian Tweet
One of the points that we’ve raised at many points here is the aspect of seeing more than just another Bible reader or devotional application developed when it comes to exploring the ways in which immersive digital experiences can instigate spiritual transformations. An idea that we’ve had in this has to do with looking at putting us in God’s shoes towards creating, making decisions on justice and judgement – situations that mirror the lessons that we get offline but aren’t always given from the perspective of letting us learn from a first-person point of view.

This weekend, when doing some nominal reading around the web, there was a game that’s been recently made available for Nokia Symbian and MeeGo devices called Doodle God (it was already available for iOS and Android mobiles). The premise of the game is that you get various elements and need to create something new from it. Very much like the days 2 through 6 in Genesis 1 where God uses the elements and environmnet around to create what we’ve come to see as this earth heavens, you get elements and have to create new creatures.

Now, on Twitter, I put the question out there about this game (and similar), is simimply, does a game like this (or the SIMS, or Black and White, etc.) challenge rightly or wrongly the conversations that we do or don’t have about this aspect of the faith conversation. Yes, we are created in the image and likeness of God, but when we talk about having and skillfully using that likeness to create and destroy, are we teaching it from the 3rd person (“a good person recycles,” “do your part and conserve,” etc.)? Or, are some of those lessons coming from building out simulations using this digital tech that puts us in a view that is similar to God’s when He created the heavens and earth to these specificiations?

I just wonder, and not just because we don’t see these kinds of games more in the mix of how we teach this aspect of likeness and stewardship, but because we don’t see developers and organizations taking this digital canvas and creating these lesson moments… are we skillful enough to have this conversation? Or, like those who would not include Enoch into the cannon in part because of how it would open a challenge towards conversations of wealth, power, and intelligence, are we afraid of the challenge to faith? In either respect, life and faith are more than a game, shouldn’t the digital immersive experience enable that?

Taking a Look At A Few Bible Apps

YouVersion English - Today ViewIts honestly kind of interesting looking at Bible software on mobiles these days. There’s not as much movement happening in terms of new features, but there is a good bit of attention being paid to the overall experience that speaks towards a sense of maturity in terms of the projects. Here are some pointers to recent (and not so recent) updates from a few Bible apps we like:

YouVersion

…here’s what’s new to love on the Bible App for Android:

Slide Out Menu. Get instant access to all of the Bible App’s features, now just one tap away. On any Bible App screen on your Android phone, touch the menu icon at the top to see the full Bible App menu: Reader, Plans, Bookmarks, Notes, Share…and more!

Available Actions Popup. Wherever you are, when you tap a verse, a handy context-sensitive menu now pops up, with icons for everything you could do with that verse. Tap the verse, then tap what you want to do. It’s fast and easy.

Today View. At the top of the slide out menu, you’ll find the “Today” view option, brand new to Android phones. Today displays the Verse of the Day (ready to share), along with one-tap access to a list of other common tasks: the last passage you were reading, today’s readings for all your active Plans, and the last passage you bookmarked. Taking you immediately to the things that matter to you the most, in this release of the Bible App for Android, the Today view is the new default home screen. (You can change this in your Settings at any time, of course.)

Cleaner Interface. We’ve tried to make your entire YouVersion experience on your Android phone more pleasant all around, with subtle tweaks that make it not just easier to use, but even nicer to look at. When you tap a verse, it displays with a dotted underline to show what you’ve selected. The icons for switching chapters are cleaner and more simplified, as are the audio player icons. While we’ve long offered settings like font, text size, and brightness adjustment to make your reading easier, now you can get to them directly from the Bible reader…

Read the rest of this article at the YouVersion Blog; you can download YouVersion for iOS, Android, Symbian, BlackBerry, Windows Phone, and a few other mobile device platforms.

PocketBible

…Are you still using the first version of PocketBible on your iPhone, iPad or iPod touch? If so, we highly recommend moving to PocketBible 2 so you can apply program updates as they are released; we won’t be updating PocketBible 1.4.7 further.

Before we explain how to make the move, check your version number in PocketBible by tapping on the Menu button and selecting About PocketBible. If it says anything less than PocketBible 2.0.X, keep reading…

Read the rest of this article at Laridian’s PocketBible blog; you can download PocketBible for PalmOS, Blackberry, Android, iOS, and Windows Mobile devices.

Logos

…Sync your reading plans from your PC or Mac to your Android phone or tablet! Take your daily readings with you—wherever you go. Get caught up on your reading in the waiting room, at the DMV, or anywhere else you have internet access.

Choose one of the reading plan templates inLogos 4 or create a custom Bible reading plan to suit your needs. You can start right away, since Logos 4 lets you set the beginning and end dates for every plan—no matter when you start.

You can follow along with daily reminders on your Logos 4 homepage or on your Android device…

Read the rest of this article at the Logos blog; and don’t forget that you can download Logos for your iOS and Android devices.

OliveTree

If you’re like many of our users, you really like taking notes, highlighting and adding bookmarks in your books and Bibles. Maybe you have even accumulated more notes than you can scroll through.  Adding categories can be a helpful way to sort through all of those gems you have in your Olive Tree Bible app. Here’s how to add categories:

Adding Categories to Highlights and Bookmarks

Open the “My Stuff” folder by tapping on the suitcase icon. Select “Highlighters” or “Bookmarks” and find the one you’d like to add to a category. Tap on the blue arrow next to the note or highlight you’d like to categorize and select “Change Category.” The default category is called “Annotations.” To add a new category to the list tap on “Create New Category” at the bottom of the pop-up menu.

Name your category and tap the “Create” button on the top right. Notice that you can also select a different parent category, meaning once you’ve created a category, you can nest other categories within it.  For example, if you added the category “New Testament Highlights” you could then select it as the parent category and create more categories within “New Testament Highlights” for the gospels, Pauline epistles, etc.

Other Bible Apps?

These are only a few of the Bible apps that are available for mobile devices. You can take a look at a selection of these on our Bible Apps page, or do a search on the application store on your mobile device.

If you’ve got an update that’s recently happened to a Bible app that you like or develop, do respond in the comments with what’s new. Or, if you are really bold and going about building your own Bible reader, let us know on your progress towards it.

Roll Call Mobile CheckIn

Press Release: Mobilize Your Children’s Check In Routine Using iPad®, Tablets, and Smartphones with Roll Call Mobile CheckIn

BYRON, IL., July 26, 2012– Keeping children secure through the use of a computerized children’s check in system is a prerequisite for nearly all children’s ministries. By the Book has taken children’s check in a step further to provide churches with ultimate flexibility by offering Roll Call Mobile Check In, which allows churches to use iPads, tablets, and smartphones for kid’s check in procedures.

“We feel the mobile check in option will give the church the ultimate in flexibility in how they do children’s check in,” says Kim Conley, co-owner of By the Book, software for churches and nonprofits. “Roll Call Mobile CheckIn allows the church to deploy volunteers throughout their facility to check families into classes or even worship services.”

Imagine a church that offers a bus ministry: Armed with an iPad that has 3G capability, the volunteer could check in kids as soon as they arrive on the bus and have name tags printed and waiting for them upon arrival at church.

The Roll Call dashboard will give ministry workers real time headcounts so the children’s ministry leader will know right away if any classes are getting too full or if they need to enlist more volunteers.

“They’ll also be able to check in visitors right from the mobile device and even walk them to the appropriate classroom if they’d like,” adds Conley.

“This children’s check in system has been the easiest out of any I have used. I love the ability to grow with more computers, tablets, or key cards as our ministry expands,” comments Angela C. from Summit Ridge Church.

Children’s Check In/Out Process

The child check in system in Roll Call allows users to check students into their classes, record attendance, and print nametags and security labels. With Mobile CheckIn, volunteers can check students in using a mobile device by looking up last name or last four digits of their phone number, then print labels at a centralized print station. To check students out simply compare the security code on the child’s name tag with the security code on the parent tag.

Technology Specifications

In order to run Roll Call Mobile CheckIn, churches will need to have Roll Call church management software installed on at least one computer. This computer must be running Windows Pentium 4 (minimum) or Mac (Intel) OSX 5.8 or greater. More details on technical specifications can be found here.

Churches will also need a mobile device such as an iPad, tablet, or smartphone that can connect wirelessly to their local network. If using the mobile device outside of local network, that device must be able to access the internet through a 3G or 4G network. If churches will be checking students in from outside the church’s local area network, they will need a fixed IP address for the Roll Call Server machine.

About By the Book

Founded in 2002, By the Book (http://www.bythebook.com) offers robust desktop and internet accessible church and nonprofit management software. Roll Call Church Management Software meets the needs of churches from small to large through membership management, attendance monitoring, visitor follow up, contribution tracking, and background check management. Roll Call Child CheckIn and Mobile CheckIn add on solutions offer churches peace of mind by securing children through PCs or mobile devices. Honor Roll Fundraising Software offers nonprofits complete donor management tools, pledge tracking, and contact management. Free trials are available of all of By the Book’s software offerings. Email, call, or sign up today: info@bythebook.com or 1-800-554-9116.

Press release submitted by Church Tech Today

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.

Splashtop Remote, Bible Library Servers, and Mobile Accessibility


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.