Mobile phone development

At the end of October last year, I attended a day-long workshop on Quickbase. The sessions at this “Tech Fest” were led by real world developers who had come up with unique solutions in their own deployments of the Quickbase product. Now, I have blogged previously about the intricacies of the productivity problems we’re trying to solve with our own Quickbase solution, and I believe we’re getting closer to implementing some real solutions that will make everyone’s job in the office easier (thanks in NO SMALL PART to the efforts of our database guru Jeanette Condo). The Tech Fest really got me thinking on a grander scale about what possibilities there are not only with Quickbase but with other ed-tech related projects as well. Two sessions in particular that really inspired me to run with it were a session on jQuery and one on using jQtouch for iPhone development.

I’ve recently upgraded to a paid personal account on Safari since Penn State’s access only includes a subset of the full Safari library, and not a lot of recent works. I’m learning jQuery fast and finding that I really love it. Just like css, jQuery allows you to keep your HTML pages clean and uncluttered. Unlike css, which controls the styles on and appearance of your pages, jQuery adds dynamic and interactive effects. It’s pretty slick and easy to learn. It helps to know some javaScript, but luckily I’m not too rusty from my days coding javaScript in the 90’s. Back then, a lot of javascript actions were inserted directly into the HTML, as was any element styling or document layout coding (read: HTML tables for layout). I’m most familiar and comfortable with client-side scripting, which is how jQuery primarily works, so this is all a piece of cake!
Here are the books I have on my Safari shelf for learning jQuery (with links to their Amazon pages):
Now to return to the title and the original purpose of this post. Knowing jQuery is a good foundation for becoming familiar with jQTouch, which is the library of javascript methods used by the iPhone and other mobile devices (so I’m told, but only real-world testing will tell). Supposedly too there are utilities for turning your jQTouch-based mobile apps into native iPhone apps (negating the need to learn much Objective C). Mobile apps for productivity purposes in the workplace sound intriguing to me. Time tracking or project management while on the go? Would potentially eliminate some of the inevitable “catching up” time on these necessary evils when returning from a conference or offsite meeting. Maybe I am just dreaming, but I think it would be fun to try. Besides, in a more mission-focused sense, if we are to pay attention to the needs of our learners, mobile learning is really looking like the next big thing. Perhaps it is better to rephrase “mobile learning” as “reaching our learners where they are” because I think that is really what we are looking at enabling with mobile phone development. The 2010 Horizon Report lists mobile computing (their term) as a technology for educators to adopt in one year or less. We are here now, folks!
In that vein, I plan to read about mobile phone development from a strategic and planning standpoint by reading this:
This book seems to touch on the actual details of mobile app development but does not delve much into it. For the real nitty-gritty, I plan to read this:
One more thing on the jQuery front. I have some ideas, based on the exercises I’ve done, for ways to improve the usability and interactivity of our course content pages that I plan to share with the Evolution programming team.
That’s all. If you have any thoughts on any of this, please leave a comment. In particular, if you know of any good resources or books on jQuery, jQTouch, or mobile development that I haven’t listed, please let me know.

The project management puzzle

I am currently leading a team at my workplace that’s evaluating our use of the project management software Quickbase. Quickbase is essentially an online database that manages data points such as (in our case) people, courses, programs and tasks. The tool was originally intended to facilitate collaboration and project management, enabling the use of templates to generate task lists and notifications for courses running on a repeat basis. It was also intended as a platform for designers to manage the development of new courses; pulling all their team members and resources together on one timeline. Managers have a stake too; using Quickbase they are able to easily assess at any time the status of courses or programs.

Our Quickbase use has fizzled a bit (or a lot).
One reason for this is likely due to the interface: It’s very database-y:
QB.png
Our workplace consists of instructional designers and assistants who may not be accustomed to a database interface, and honestly are not expected to be power database users as part of their skill set.
My charge, along with the team joining me in this journey, is to find what might actually work to achieve our ends. We know that the software is very good at managing data, tables and relationships. We also know that our users are drawing a blank when attempting to use it. So the question is: how do we build an interface that our users instinctively know how to use and serves the purpose of keeping team members honest and on track? There is yet another layer of complication here. The team interacts on a nearly daily basis with various data housing systems outside of Quickbase – systems that store more detailed course information, manage time tracking, store course multimedia, etc. Here in fact is a snapshot of the whiteboard from our last meeting where we were discussing all these systems:
QBwhiteboard.jpg
You can see how tangled this problem is. Many of the systems are out of our control and will probably still have to be interfaced with manually, but for the in-house solutions, there is great potential for integration, saving time and duplication of effort for everyone who uses them.
Luckily, we have Jeanette Condo on our team, a programmer with database and API experience. (yay for us!) With her help, we may come up with a win-win solution that puts Quickbase in the background while fully taking advantage of its powerful database capabilities.
Our next team meeting is next Monday. We are still in the discussion and exploration stage and have not begun any nitty-gritty development or testing yet, so the question I think I want to ask is, if we were to design a system for managing our work from the ground up, without consideration for existing systems, what would it look like?