Posts Tagged ‘nokia’

May Videocast

Monday, May 9th, 2011

I know that last month that we talked about doing a monthly podcast, but you wouldn’t believe how hard it can sometimes be to get schedules and technologies to work together. Nevertheless, there’s not a lot that’s impossible with mobile these days, and so I recorded a video cast while in between meetings using Qik and my Nokia N97. Lord willing, this looks good, because we don’t edit while on the go… at least not yet ;)

View the MMM May Videocast via Qik.

 

Open Source as Ecosystem not Just Platform

Wednesday, February 16th, 2011

Thanks to the announcement of the Nokia-Microsoft partnership, I’m getting another one of those chances to think about open source and closed (curated) platforms and ecosystems. There’s always rumblings in the digital faith space about open source and how it can play a role as the/a answer to issues and reach, but too often, I’m hearing open source pitched as a platform solution, when the issues with evangelism, missions, etc. have more to do with ecosystem impacts than just platforms.

It is my opinion that the shift that the Nokia/MS partnership heralds is this acknowledgement that ecosystems are the next playing field for mobile, not platforms. Not that platforms (and the developers that come with them) aren’t important, but that their role isn’t any more important that issues of access, logistics, and flexibility to response.

When it comes to digital faith, we have several platforms (electronic bibles and music to name a few), but very few real ecosystems (the function and nature of Bible societies, and to some extent publishing companies, fills this view nicely). Centering just in on Bible societies for example, it isn’t just the distribution of Bibles, but the curation of faith through social programs, translation services, assistances to for- and non-profits, policy management/lobbying, and (hopefully) the sharing and maturing of believers who define faith first by belief in Jesus Christ. In a sense, they are a hub of several types of activities – so just advocating “go open source” doesn’t meet how they can respond.

Going open source with the disemenation and distribution of Bible texts could be part of their solution – when the matter of network assets, logistics, printing, and analytics has been answered. Going open source where the text (video and audio) can be structured and openly built up can be a solution – when the matter of monetizing the work so that those translating and making those structures can feed their families has been answered. Going open source with the hope of participation isn’t the same as already having community involvement in other aspects of fellowship (digital or otherwise) and opening up a further work doesn’t stress community threads. If you will, open source anything doesn’t matter – its how going open (shared duty, accountability, and responsibility) effects the other spokes of the wheel.

As I tweeted recently, “mobile open source initiatives need to not just answer the platform questions, but ecosystem relevance (whether tied to others or on it’s own).” In respect to digital faith initiatives, we’ve not only got to be able to say “go open source,” but identify the impacts that doing so will endear to current ecosystems. It might be the case that going open source for a platform in the chain will disrupt the entire sea – knowing this, and then helping individuals, ministries, and organizations navigate life afterwards is not just a mobile opportunity, but a key to displaying service as technology’s fingerprint to ministry intiatives.

 

Carnival of the Mobilists #242 at Blog.AntoineRJWright

Wednesday, November 3rd, 2010

Carnival of the Mobilists (logo)It is always a good thing when the Carnival of the Mobilists (CoM) is published. A collection of the past week’s writings on mobile, the CoM is a chance to spread some of the wealth of thought and application occurring in the mobile space.

This week’s CoM is hosted over at Blog.AntoineRJWright and features pieces on recent stats, user interface/experience with tablets, and several things happening with platforms and carriers.

There’s always room for new contributors – so if you are doing anything related to mobile ministry, here’s a platform to get the word out about another influential area of mobile. Read the submission details and post schedule over at the Carnival of the Mobilists website.

 

Announcing: New MMM Mobile App*

Friday, October 15th, 2010

Download MMM Mobile App from Nokia's Ovi StoreWe talked last week about how in making an application that goes alongside MMM that it would have to be something that adds value to how you interact with the vision and content of this site, and we’ve got a new application that will help you do just that.

The new MMM Mobile App was created with Nokia’s Ovi App Wizard and includes the RSS feed of the site, in addition to linking to our social streams on Google Buzz and Twitter.

This is a free application and a great way to get a piece of MMM on the road with you if you are using a Nokia Symbian device.

*Our other contributor, Brett, is actually looking into doing a similar (but better) app for other mobile platforms. Look forward to those posts and how that will unfold from this endeavor.

Download the free MMM Mobile App and tell your friends about it. The story of what happens in this mobile lens is also crafted by you now :)

 

Opportunities with Mobile TV

Thursday, September 9th, 2010

Change that’s been caused by mobile can sometimes be very swift and loud, or something that happens quietly, starting at first slowly, and then there’s a watershed moment. This has been the case in respect to the cellular subscriptions (in the hundreds of thousands 15 years ago, nearing 5 Billion at this moment), SMS use, mobile internet use, and even mobiles replacing digital cameras.

In the case of these mobile disruptions, there’s always been ripe opportunity for enterprising persons to take what we knew, and then mix in the new, and create something new. I wonder what some of those opportunities would look like in respect to mobile TV?

Why mobile TV? Well, look at the announcement that Nokia made today in respect to a new mobile TV accessory. Given their projections towards the devices they will sell that would be compatible with this device (tens of millions per year), this could have a profound effect on our concept of TV.

We’d do best not to ignore some context here. The digital TV standard being used with the accessory (DVB-H) isn’t widely deployed all over the world – there are about a dozen or so regions that have it up and running now, and not too many of them seem to be advertising it as much. So, opportunity isn’t as obvious, but it is there for those areas where DVB-H is in play.

That being said, those who move first usually get the benefit of making (or breaking) the best impressions to the general public. Given what we know that’s happening around digital media, visual storytelling, and YouTube/Hulu’s redefinition of broadcast TV, what are some of the opportunities that lie out there for ministries who can use mobile TV as part of their communications and outreach strategies?

And if the opportunities are there, are you moving with them, or waiting until something else comes along validating your venture into another mobile disruption?

 

Of Applications and Motivations

Friday, September 3rd, 2010

Been thinking a bit about some of the statements made in that Future of Bible Software piece. Sometimes, a bro can be a bit far-reaching, and other times, I simply expect more out of us all than what’s probably realistic.

I mention this because I’m thinking about my primary mobile device (a Nokia N97 running the Symbian^1 operating system) and why I no longer have a Bible reader application on it. Part of the reason is becasue I’ve found it better in many of the gatherings that I attend to simply listen to what’s being said, using my mobile to note important points. Other times, I’m in a setting where the larger screen and UX of the iPad plays a better role for things.

I wonder though about going back to having something more than a link to preferred Biblical resources on my device. Something that isn’t a Bible reader, but does give me some of the benefits of a quick and targeted search. I don’t (necessarly) need to even bookmark the passage, but I do need to possibly copy it (or tweet it) so that I can recall it later.

And so, I thought some about the Biblia API project started by Logos, and how simply their releasing of this API releases them from an expectation of having to create an application [for me] – but it puts the onus on me to learn how to use that pipe for the kind of content experince that I desire. I’m in favor of such a move, because it is indirectly causing some aspects of the user-base of Bible applications to become fishers of content themselves, and creators of more personal solutions.

However, I’ve not started to crack open the book(s) on learning this API, nor how best it could be used in my kind of a scenario. In some passing conversations with Brett (MMM’s latest team member), his expressed desire to learn to develop for various platforms has rubbed off on me. I want to learn how to use that API, and do it in such a way that adds value to my Biblical needs, not just scratches an itch for information at my fingertips.

What I have been doing is planning my approach. For example, I know that I want something that’s not a native application – it needs to be a web runtime (WRT) widget. The widget would need to have two panels: the static one on my homescreen would just display an icon to the left and the Scripture references to the last two or three items I searched for (there’s no room for more than that). Clicking on the widget would take me to an expanded view where I see a listing of my latest searches (5-7 perhaps) and a search box at the bottom where I could put into it any measure of references, boolean operators, and phrases, which would then spit back to me on a similar screen the results of the search. Clicking on a search result would automatically add it to my “history,” open the browser to the biblia.com website to that reference, and on the widget there’d be a button at the bottom to go back to my search results screen. Because this is a widget, it wouldn’t need to save anything, so when I close it, the only things really saved are my history of the references I went to, not the search queries.

In my mind, on my mobile device, this is something that’s very possible. I don’t necessarly need an app anymore than I can develop one myself. The pipes are there, and I can do with the content what I can based on legal and ethical agreements.

It has me thinking hard about the future of applications as a whole, but also how we are motivated towards creating our own experiences or doors into searching and valuing the availability of Scriptural content. I can’t say that at this moment that I’ve moved forward past what I’ve said here, but I am thinking that something like this should happen nearer than in the future.

 

Why There Are No Books on My iPad

Tuesday, June 22nd, 2010

I will chime in again with just about everyone else who’s used an iPad for any amount of time – its a very good device for consumption-based reading/browsing, and the battery life is phenomenal. Thing is, its not so great when you want to read certain types of content – mainly because, some things just aren’t available anywhere but in a browser (hence the title of this post).

When I purchased the iPad, I knew that there was a smattering of (e)books that could be downloaded to it. And I was very excited and intrigued about any perodicals which would use the Bonner’s Mag+ Concept as I knew that for such a device, making the content fit into a unique immersive reading experience was very key to enjoying the device.

What I didn’t expect was that I’d have to grapple with vendor lock-in and a lack of being able to port content easily.

It’s an Apple device. There’s not Windows, webOS, Symbian, MeeGo, or any other mobile platform coming out that can skillfully run on this hardware (without a ton of hacking). It’s not meant to be open or opened, and that keeps some things in a positive light – until you want to do something more and not go through iTunes or the AppStore to do it. I wish that in the respect to other software platforms, other tablets would use platforms as a means to enhance the consumer experience, not just tie them down.

The major beef for me though has to do with porting content from the iPad to my N97 (or whatever the mobile of the week is). Outside of those things that appear within a browser, I’m generally having to make the decision to either download on the mobile and put in a email draft folder to share with the iPad, or put it on one device and ignore the fact that I switch between devices frequently, but want to keep my content wherever.

And therefore, I’ve only downloaded samples of books. I can’t handle the idea of reading something on an iPad to be locked there, and then between Apple and the publishers to not have access to content that I purchased on any other mobile device that I own.

Saddest of these is that I’ve not really liked the Bible experience on the iPad. I’ve been looking at YouVersion for a few weeks now and it comes closest to the functionality that I get from Google Reader – I can read and note on any device, and both the native and web-based applications keep my information accessible no matter which device I’m using. There aren’t too many apps – or content streams – which do this in the PC world, let alone the mobile world.

Ideally, I’d love to be able to simply purchase the licenses to a (e)book and then be able to read/consume/share that content accordingly. But, right now, this has to happen more on the side of the Bible software developer to account for the user and the licenses, not so much on the side of the publisher. And with such the niche that Biblical software is, some items just are better left not purchased unless you can make the time investment into the device they are targeting.

So I’m left reading samples of some items, and sharpening my search and research skills for other items. I refuse to get into the game of jailbreaking (hacking) my iPad just to share content easier; and definitley don’t walk the line into piracy – the men and women who take the time to create, test, and market this software deserve to be compensated fairly for their labors. I just wish that it were easier to abstract the content from specific platforms, so that it would make for a better value proposition for me the consumer of the content.

Maybe if that happens, I can stop looking to paper books as models of truely mobile content.