Posts Tagged ‘mobile in development’

« Older Entries
Newer Entries »

Building with Sticks, Connecting with Glue

Monday, March 5th, 2012

glue,sticks, and clothes pinOver the past week(s), I’ve been working on answering some simple questions to address building pitch slides for the weekly 1M/1M public discussion. There’s a signifiant need for sales/marketing help for MMM, and getting through these slides has been rewarding and frustrating. We are really missing a lot of pieces of data we should have, and other parts are defined enough that it doesn’t fit normal modes of “building and marketing a product.”

The “product” MMM sells is the knowledge and underanding of making sense out of the points which connect mobile and faith activities. That’s not something easily bottled, that is, unless its sold as glue and not as the bottle. Now, to sell glue, you have to identify what things need to be present in order for that stickiness to take place. You’ve got to be able to say on your label what surfaces it works best on, where not to put it, and probably some hazard information in case someone misuses the glue.

For us, that means we aren’t so much as building apps and services, as much as we are identifying those points where devices, services, and experiences come together for a specific environmental condition at the intersection of faith and mobile technology. Unless folks already see that these two areas collide, they won’t be able to discern how best to glue them together. That’s how we get the term mobile minsitry, we are looking at this intersection of two areas that have some common points (communications, sociologiy, etc.) and what happens when they collide and both those common and uncommon areas get challenged.

The other day, I responded on a post for a developer at LinkedIn. The post didn’t identify a specific need for the developer, but did mention much about the organization (the usual HR boilerplate stuff) and then some toolsets/skills needs for the position. I made several assumptions about what they are looking for ending with a statement that perhaps they are looking for something less oriented to building and something more like glue. Now, I was corrected, and in that correction was detailed the specific need for that position, but it still came across as looking for glue, not someone to make sticks.

When it comes to mobile ministry, part of that identifying what it is you are offering (our case) or what you are looking for (the folks we tend to attract) is making this distinction between building and sticks. Sometimes, you might solely be on the side of building, and therefore a specs sheet of programming languages accompanyed with certain products might be the key. Other times, and usually what we see more often than not, is that people are looking for the glue. How does mobile stick best with wherever they are? Whether that’s reformatting videos, adjusting to the appearance of mobile on the ministry scene, or introducing less friction to a reiteration of a product, its more about the glue (what happens in between the points), than the sticks (the points)..

I’d wager that many of you have been using sticks like glue and wondering why you haven’t seen the successes you’ve wanted. May I make the suggestion that you find the jars of glue (who connects the dots within mobile and ministry), and then refocus your energies? You might find that with less building that you enable more sticking to your ultimate goals.

 

Tags: , , , , ,
Posted in Devices and Software | No Comments »

Don’t Forget the Non-Smartphone Folks

Tuesday, February 28th, 2012

GetJar Screenshot for upcoming @mobileminmag article - Share on OviThinking about it some, yesterday’s post might have come across as if we were putting ebooks, literacy, and that neat community experiment only inside the frame of smartphones. Sure seems like it doesn’t it? Well, no. Everyone can do that, and your mobile efforts should take into account the capabilities of as many mobile devices as possible when you do those kinds of things.

And I know the refrain, many folks talking things up in mobile ministry have a working experience of what’s in their pockets – and that is often a smartphone. A random survey of just a few folks from the Mobile Ministry Forum pointed to just that. And it doesn’t mean that we are limited to knowing what’s in our pockets. Not everyone has had my experience of being a mobile device reviewer, or owning more than two mobile devices for most of their mobile life. So, There’s some forgiveness that has to be had when we do craft mobile solutions and it sounds like it only meets the needs of the most affluent amongst us.

You don’t see non-smartphones around you (I’ve heard that too)? So, whom are you around? Did you know that globally that about 30% of the mobile phones sold in the last year were smartphones – and that’s out of a total of 1.2 billion mobiles sold (Tomi Ahonen stats, Cellular News stats, Taipei Times). Or, if you are in the USA, you might say “yea, but it doesn’t look like that when I see on TV, in the cafe, etc. that so many have them.” You are right in some respect, of the mobiles sold in the USA, (I think we are just about at) 50% are smartphones (across the national carriers), and rarely are these sold with those persons that use pre-paid accounts (Nielsen). So, if you aren’t seeing them, there’s a question of context, half of the people you interact with will probably not have a smartphone. If you aren’t seeing that, you’ve got to check your associations.

And I know that those who work with/for content creators and media companies that smartphones are a much easier target. The browsers are better, there’s an app for that (grrr), and folks are willing to often flaunt that new device with a nifty case or sound. That’s no excuse though to just target them. We covered Phone Publish last month which is able to get content suitable for the smaller screened, lower-speced, non-smartphone folks, without keeping the content away from them (designing the user experience is harder, I’ll admit that much too). 

You want to push apps to everyone, check out GetJar. Get Jar is how many of us who have been doing mobile longer than the last half-decade are familiar with the concept of “app store.” You go to the site on your device, and it recognizes the device you are using and just shows the content that’s compatible with it. Simple right? If you follow the specs for the majority of devices which can download Java/Java-similar applications, then you’ve got a means to get in on those devices. There are other app stores (Nokia Store, Bada Store, etc.), but just wanted to hit on that one since it really does endeavor to hit the most devices.

Some stats are showing that – at least in some regions – that people are using mobile over PCs to get online. So, that really cool developer who wants to do something based on that pretty 22in monitor, tell them to take a few steps back. Concepts like responsive design, mobile website transcoding, etc. need to be looked at just as much as you observe that client requirement of “make it look good on my screen first.”

And if those folks aren’t able to get online, is your mobile strategy doing SMS (over 90% of mobiles are capable of doing text, nearly as many do multimedia (MMS) messages)? What about memory card swapping? Look back at that idea about a book fair, notice how we have a central librarian laptop that is able to serve those devices which might not have the ability to get content via WiFi, Bluetooth, or swapping memory cards. Your church might have gone mobile, but folks can’t go with you if they can’t get what you’ve moved forward with (Pew Internet, via Textually).

So, don’t forget folks who aren’t using what’s in your pocket. Its easy to do (trust me, personal experience like crazy here). You do your witness of the effects of the Gospel when you love on all of your brothers, not just those with the buttons and trinkets that look like you (1 Cor 1-3).

 

Tags: , , , , , , , , , , , , , ,
Posted in Devices and Software | No Comments »

Forum Oxford: Tablets as Remote Phone Controllers

Tuesday, February 21st, 2012

Am contributing to a discussion happening over at Forum Oxford asking if tablets (and therefore laptops or desktops) can serve as remote phone controllers. Neat idea, and one which could have some implications for many of the mobile projects we’ve touched on (hint, hint). Here’s a snippet of the discussion:

Where is your phone when you use a tablet?

Not too far away? In your pocket?
Then…

Why couldn’t a ‘tablet’ just be an ‘external display’ for a phone?

1.Everything that is displayed on the phone screen is seen on the tablet.

2.Touch, swipe, tap, type: on the tablet screen to control the phone.

I’m wondering if anyone knows of or has seen something in the pipeline that might fit this scenario.

Do you think there could be a market for a ‘dumb’ terminal type device that connects to a phone for that purpose and that purpose only?

How?

A/V senders and/or Bluetooth 3.0+ and/or WiFi and/or other?

Serious power issues?
In-vehicle use?

Read the rest of the discussion at Forum Oxford. To contribute, you will need an account.

 

Tags: , , , , , , , , ,
Posted in Devices and Software | No Comments »

Spatial Interfaces, Theological Literacy

Wednesday, February 15th, 2012

Tim Challies Visual Theology - Books of the Bible iPad-sizedLast week, or so, I wrote over on my personal site (Blog.AntoineRJWright) a post talking about this idea of spatial interfaces and how the concept of such a means of navigation intersects directly with the thoughts I’ve been having about theological (more specifically, biblical) literacy and what that means we should be enabling given this age of connectivity, productivty, and access to tools of publishing (re: internet). Here’s a snippet:

As I was just going through Twitter and seeing what all people have been posting about today. I came across a neat Biblical visualization from Tim Challies. Seeing this reminded me that I’ve not done much of an update here (or MMM) about the All Books Project that I’ve been working on. So, let’s talk spatial interfaces (a topic seen in a recent meetup I attended) and theological literacy – and why these merge nicely.

Read of the rest of Spatial Interfaces, Theological Literacy at Blog.AntoineRJWright

I make some bold claims in that piece (“theological literacy isn’t just reading/comprehension, but its able to (re)create the Word contextually” for example). What are your thoughts? Especially for those of you whom are teachers/pastors, can you teach to this level? And if not, are you misapplying the term literacy in light of the command in Matthew 28:18-20?

 

Tags: , , , , , , , , , , , , ,
Posted in Devices and Software | No Comments »

Lesson’s Mobify’s CEO Learned from Google

Friday, February 10th, 2012

If it seems as if we’ve been pulling from the list of contributors noted on the recent Carnival of the Mobilists, that’s only because these have been items also sitting in our periphery as notes to pay attention to as we derive some knowledge and wisdom about mobile which is applicable to mobile ministry. Sometimes, this just happens to intersect well with other’s views of what is important in mobile.

Another set of insights pulled comes from a report by Mobify’s CEO (Igor Faletski) relayed via GigaOm. These insights are important to us because MMM uses Mobify to transcode and deliver our mobile website (http://m.mobileministrymagazine.com). Where he is taking is platform, we eventually follow in some respect. So, in hearing some of the lessons he learned in a recent excursion with Google’s Mobilizing Mobile event, there just might be something we could gain as a movement going forward.

Here are the individual points (described as numbered lessons:

  1. Set the agenda
  2. Make your innovation tangible
  3. Focus, focus and focus
  4. Track the micro, decide on the macro
  5. Bringing it together

Read the details and examples of these ‘lesson points’ at the GigaOm article.

Our Reflections, Actions Forward
Its really easy to read something like this and just take it as another set of perspectives from a leader who’s gotten there and is basically setting the pace. But, we needed to go a bit futher here. How these lessons applied to MMM pushed forward some thoughts and initiatives that were already underway.

For example, one of the motions that we wanted to emphasize this year is that while we are in favor of the app movement many are prescribing towards in reference to going mobile, an app isn’t a strategy, and focusing on an app, or series of apps, would be a losing proposition with the kind of support we could push there (see how we explained about resource constraints with mobile apps/websites in a previous article. We decided therefore to decommission all of our mobile apps to an experimental status, and focus on cleaning up our use of WordPress so that we could be more readily accessible in a mobile format (see the Mobile/Web App Beta). There’s still a significant level of work needing to be done behind the scenes in terms of article categorization and dynamic page templates, but, not to the minute level of needing dedicated attention to each mobile platform out there. Will it take us longer to have a “solution?” You bet. Will we be better as a lighthouse for the extent of audiences we have here? Most definitely. That’s our focus, and the clarity we aim towards here.

Your steps might not be as drastic (then again…). What you need to decide as you are going down this path of being mobile, is that your success will hinge on the amount of planning, focus and execution that you can do or manage. If you are trying to control too much, however, you’ll find that the tentacles of mobile ministry will choke the purposes you initially had for your project, leaving you quite still in a mobile world.

 

Tags: , , , , , , , , ,
Posted in Devices and Software | No Comments »

[Experiment] Redesigning MMM

Wednesday, February 1st, 2012

[Screenshot] MMM Alternate Homepage - Share on OviFor a number of years now, we’ve been talking about redesigning MMM. This has been a much harder process than I would have thought because of changes in the general organization of site assets, as well as other tasks relating to making a living out of this endeavor. That said, things have been happening on that front and I’m ready to put forward something of a beta to what would/could be a new iteration of MMM.

View the Alternate/Redesigned MMM (for those viewing this on their mobile device, see the note at the bottom of this posting for an additional step to see this)

This is following inline with some of the 2012 resolutions we’ve posted so far (practicing what we preach). This is also an evolution in the philosophy behind MMM in being more than simply a destination towards information, but a collection of those stories presented in a way that accents the use of mobile towards addressing those questions and implications of using mobile in faith-based contexts.

Goals of the Redesign
Of the comments most heard about MMM, one of the loudest has been in the findability of information on the site. Indeed, its an issue. This site has been in existence since 2005 and there’s over 3000 posts full of content. In addition to just having those posts, there’s been several themes that have run throughout the site, making it harder still to simply use a search box to figure a direction to find things. This design seeks to make the entry point to the content better (behind the scenes, content is literally being reorganized to fit a consistent paradigm).

The other goal of this redesign is to reflect the overall user experience (UX) goal we’d have for mobile applications. There are a few mobile applications that we’ve published to date, yet none of them were able to capture exactly the kind of reading, searching, and interactive experience that we’vev been after. After careful consideration of the options (using one or more content management services, developing several native applications, etc.), it was decided that to create a single webpage that had most of the features in a mobile-first role would be the direction. This would be incomplete without redoing the entire WordPress template, so this initial design was completed in order to test the feasability of moving forward.

Issues in This Redesign
Its one thing to go mobile-first, its another to meet each mobile device that comes here with the experience that’s best for their devices. This alternate landing page doesn’t address every mobile device. Its JavaScript-heavy, and has some features which would make some of our lower-end mobile devices, without a proxy-based browser such as Opera Mini, to choke on either the size or the features. Mobify is still being used to streamline the existing WordPress template’s pages for mobile viewing therefore. A complete theme would be mobile friendly (responsive web design methods) and might not need that help to do so.

Performance is also an issue. Thankfully, its a lot better than it was in initial testing (was very happy to get this onto the production server and see signifiant page loading gains). There’s going to be an issue though since there’s a JavaScript interpreter on the page rendering the Articles section, which makes for a potential bottleneck in loading for some browsers/devices. Ideally, a full WordPress template (written in PHP) would be better able to address this.

There are some more niggles. I’ll see more as time goes on. If you spot anything, let us know via Twitter (@mobileminmag). Small items will be fixed. Bigger items will be fixed in that WordPress version.

Resources to Address Issues/Goals
What’s good about this alternate homepage is that it is providing a means to relearn some JavaScript, brush up on HTML5 and its newer abilities, and finally put into practice some lessons about working with content management systems like WordPress which require not only development, but content strategy focuses. The resources to do all of this is widely available online, and is constantly tapped.

There are a number of people/groups in the Body who deal with aspects of building this which will also come in handy along the way. Web app developers, WordPress customizers, etc. have the kinds of collective wisdom that would be utilized to make this happen. If at some point the work goes beyond the time/abilities here, its possible that such a redesign project would be farmed out.

Lastly, there’s you. For those of you visiting the site daily – thank you. You coming to the site, offering feedback, or simply hitting areas (constantly) helps to direct projects like this towards completition. The more you use the site, especially this alternate version, then the better we are able to make a resource that fits your needs.

Implicaitons of This Design
There is a good chance that we will probably stick with a web-app method for delivering content from here on out. That would mean that building and maintaining apps which also publish this site’s content would only be done as a means to explore the workings of content mangement systems and publishing experiences, rather than anything strategic towards pushing this site forward.

Another, probably more jarring, implication to this design is that we would be (finally) going back to our roots in respect to being mobile-first in everything. This could mean shorter articles, but definitely means more flexibility and versatility in the data streams that make up MMM. For example, we have a “tab” which has a link to all the places we conduct conversations online. Such an item could easily become a single page stream and RSS/XML feed for those who would rather find content in those methods.

The design is using features of CSS and HTML which are more advanced. Based on some of the stats we can gather form those visiting MMM, those features are supported by those visits. However, that’s not a 100% solution. We would like to be as close to 100% mobile compliant, and not at all desktop browser compliant. We’d like to drive the desktop browser experience to primarly search and RSS versus casual browsing.

We are also going to slowly start making the shift towards getting away from email for non-collaborative tasks, and use Twitter as a means to not just be poked about items, but also conduct the initial parts of conversations. Until we do something a but broader federated (identi.ca and/or XMPP-based stuff from our server), that would help us to best triage communications and move quickly towards managing opportunities in this space.

Or you can look at it in this simple statement: we are going even more mobile and virtual and dragging you along for the ride :)

What’s Left?
Using it, finishing the WordPress custom theme conversion, making mobile apps match its UX… ya know, the normal ;)

Just go to http://mobileministrymagazine.com/m.html and have a go at it.

Note for Those Coming from The Mobile Site
If you are reading this from the mobile site, then on clicking this link, you will have to click the link that says Full Site on that page. That’s simply because of how links from our use of Mobify behave.

 

Tags: , , , , , , , , , ,
Posted in Site News | No Comments »

[Guest Post] iBooks Author: It’s Place in an eBook Production Workflow

Friday, January 27th, 2012

This is a guest post submitted by Craig Button (@TheProdSon)

Introduction, Quick Summary

Since most of you have no idea who I am, I suppose I should introduce myself. First and foremost I am a believer and follower of Jesus Christ. After that I’m a geek. I’ve owned just about every type of computer ever made and today work on both Mac and PCs depending on what I’m doing. I use both Pages and MS Word, prefer Excel to Numbers, and either PowerPoint or Keynote depending on what I’m doing. I’m a health care provider by profession, an educator by avocation, I’ve been clergy, (church offices on weekdays weren’t what I was expecting) and am now a grad student. I’m always looking for ways to package and present information.

I was excited when Apple announced iBook 2.0 and iBooks Author. I’m in the process of producing a couple of books/ebooks and was looking for something that would make it easier. I was hoping that iBA was going to be it.

After spending a few days playing with it (and I have to be honest and admit it was playing, not a focused systematic study/evaluation of the program) There are some conclusions that I’ve come to regarding iBooks Author which might not match your needs, but hopefully shines some light towards its strengths and weaknesses at this juncture of the application.

Summarizing the Positives and Negatives

There will be projects I’ll use iBA for. However, I won’t be using it for everyday kind of work. Not because, I don’t like it, or it’s a bad program, or even because of the EULA that says you can only sell product from iBA thought Apple. I’m accustomed to a bit more control and flexibility when creating publications, and iBA doesn’t quite meet those spot on – though its not far off.

Positives about iBA: It works, it looks good, it’s easy and it produces what it says it’s going to.

Negatives about iBA: it produces HUGE files. A test file went from 800K .txt file to 27MB (~1000K = 1MB) with a couple of pictures added. The second, and in my case the biggest thing against iBA, is it only produces a product that can be viewed on iOS devices. That means not on the Kindle, not on a Nook, not on an Android phone, not on anything unless it has been made by Apple. I’m a Mac fan boy. But, I’m about communication. Therefore, limiting my target audience isn’t good for me. My first product is to be a textbook on Critical Care for Emergency Room nurses. The second book will be first aid and health for photographers. Both topics I’m pretty passionate about (hence my issues with file sizes and limited devices).

It’s About Workflow

It’s about workflow. The term workflow is one that you hear in the digital photography world. It is the term that defines the flow of data from the camera to the final print. I think the term works well for the ePub/ebook industry as well.

My Workflow: I use a program called Scrivener. This is a Mac application, (Windows and Linux also available) that I use to produce the text of my work. It’s a combination text editor and research organizer. This is probably were 80+% of my work is done. I do all my writing within Scrivener. It also produces ePub files which can be read by nearly all computing platforms. It does have some drawbacks, with one of them being that its not easy to place tables and graphics into the output. From there, I use Adobe InDesign for layout that needs formatting and graphics. I don’t own this program; I rent it as needed since I only use it maybe 1-2 months out of the year. Using InDesign I produce a ePub, witch is a zip file that includes all the information needed for the ebook reader to read your file. It only takes a little modification for it to work on any of the readers.

How could iBA fit into this workflow? Well in my next publication, it might work for me. These books I’m publishing on health care and first aid directed at travel photographers whom are likely to have iOS devices. But, in using iBooks with plans on selling it, I’m sure the iPad market will be a bit too limiting. I will however give it a try. iBA is very easy, and I’m hoping it will allow me to easily produce the product I want. However, for anything that is text-based, or contains just a few graphics, the files produced by iBA are way to big and to limiting.

The workflow I have fits my use case, and allows me the broadest target audience. While I’m a geek, and still have a copy of the original PageMaker running on a Mac Classic, I’d like to have more control than what iBA offers. On the other hand, for someone who has never produced an ebook, iBA might be the perfect tool.

Conclusions

After writing the first few paragraphs, and sleeping on it, I came up with a few other thoughts. The first is that I’ve been through this kind of transition before. I remember when PageMaker first came out and people had lots of different fonts to use. I remember when Photoshop first came out and it was affordable to anyone to buy. People produced some horrendous publications and photos. And you’ve all probably sat through some pretty long, boring PowerPoint presentations. Just because the tools are there, doesn’t mean that everyone should use them.

I’m a Tim Taylor, not a Bob Villa, when it comes to using those hammers and screwdrivers. Like any task which needs to be done, it deserves to be done right. Use the right tool, have the right people use the tool, and spread the word.

For more information and to download (free), see the iBooks Author page on the Apple website. Note: content created with iBooks Author can only be read on devices with iBooks2 on the iOS device.

Craig is @TheProdSon on Twitter.

 

Tags: , , , , , , , , , , , , , , , , ,
Posted in Devices and Software | 2 Comments »

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

Sunday, January 22nd, 2012

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.

 

Tags: , , , , , , , , , , , , , , , , , , , ,
Posted in Commentary | No Comments »

« Older Entries
Newer Entries »