Showing posts with label mobile development. Show all posts
Showing posts with label mobile development. Show all posts

Friday, April 15, 2011

Extending the PhoneGap API – Third-Party Plugins (ChildBrowser)

As we are preparing for Emerging Technologies for the Enterprise, I did not want to forget the rest of the series on PhoneGap API that Hiedi Utley has been penning.  Here is part 4.


Extending the PhoneGap API – Third-Party Plugins (ChildBrowser)


So the last post was all about editing PhoneGap classes to add a little something extra, today it’s about using a third-party plugin that you may have downloaded from somewhere or gotten from someone.
The plugins that we will be using today are from Jesse MacFayden (aka @purplecabbage on twitter). The original source code for the plugins can be downloaded from github here: https://github.com/purplecabbage/phonegap-plugins.git
You can also get the entire source for my sample project “HelloPhoneGap” from github here: https://github.com/hutley/HelloPhoneGap.git


Read more..

Friday, April 8, 2011

Extending the PhoneGap API

 Here is the third installment of Hiedi Utley's series on PhoneGap.  We hope you are finding this series helpful as you learn more about developing for mobile applications.

Extending the PhoneGap API
If you’ve had a chance to play with PhoneGap a bit, chances are you have wanted it to do something that it doesn’t already do. Alas, don’t worry! You don’t have to put in a ticket and hope that the PhoneGap developers agree with you and implement it in some future release, if you can write a little Objective-C then you can do it yourself and use it in your own iOS project.
The topic at hand is all about extending the PhoneGap API whether it’s by editing existing PhoneGap classes, downloading a third-party plugin from somewhere, or by writing your own plugin from scratch. For this post I will concentrate on editing the PhoneGap classes, in later posts I’ll give step-by-step instructions on using a third-party plugin and how to create your own plugin.
If you haven’t already had a chance to read my earlier posts on PhoneGap internals and using the PhoneGap API – you may want to peruse them before reading on.


Read more...


Thursday, March 31, 2011

Using the PhoneGap API

 

We are a little behind in posting Hiedi Utley's PhoneGap Tutorial Series.  Or she is a very fast writer.
In this post, Hiedi discusses the features of PhoneGap API.



Using the PhoneGap API

Welcome to the second installment of my PhoneGap Tutorial Series! This post is a continuation of PhoneGap Project Structure and Internals so if you haven’t already, you may want to peruse that post before continuing on.
We already know that PhoneGap is an open source framework for writing applications using typical web technologies like HTML, CSS, and JavaScript and that the PhoneGap architecture supplies JavaScript wrappers to access native phone features. What you may NOT know is how extensive those features really are or how to actually use them.
This article is all about getting familiar with the current features of the PhoneGap API and how to use them with the iPhone iOS.


Read more..

Monday, March 7, 2011

Mobile Design Part 3

 The next installment of Kevin Griffin's blog on Mobile Design.

Cognitive Effort.

In this installment of my thoughts on mobile design, I thought we would take a look at the concept of ‘cognitive effort’. I think I first heard that term used in reference to design from William Van Hecke (@fetjuel) when he spoke at Voices that Matter in Philly. When a guy from The OmniGroup talks to be about making great apps, I tend to shut up and listen.
We have all thought about cognitive effort at some point:
  • “Does this screen look too busy?”
  • “We should move this functionality out of this screen” are signs you thinking about it.
What increases cognitive effort?
Every question, action, dialog, gesture, tap, shake, voice communiqué we ask the user ultimately ends in some kind of effort be it physical, cognitive or verbal. Sometimes we intentionally make these things progressively harder, games for example. Sometimes we unintentionally make these things progressively harder, continually adding functionality to a screen.

Read more...

Friday, February 4, 2011

Philly ETE 2011 mobile line up!


 This post is via Kevin Griffin, Chariot Architect and committee chair of the Mobile tract for ETE:

 Philly ETE 2011 mobile line up!

Just thought I would post an update on the current lineup for Philly ETE.
I've been involved in helping get the mobile track lineup sorted out and so far we have confirmed the following:
  • Josh Clark - my favorite 'Tapworthy' author.
  • Johnathon Stark - He literally wrote the books on making mobile apps with HTML, CSS and JavaScript.
  • Ted Neward - If you are lazy, and want to write Android apps, he has the talk for you!
  • Jay McGavren - If you want to write Android apps, in Ruby (Oh yeah!) This is the talk for you (personally, I can't wait for this one!).
  • Terry Ryan - Philly Evangelist from Adobe who will use Air, to build Playbook apps. Magic!
  • David Kaneda - Although technically on the Frameworks track. Go build your mobile apps in Sencha Touch, seriously go now! That way you can thank him at ETE!
With one super secret invite still pending :D

Tuesday, February 1, 2011

Executing JavaScript from Objective-C in an iOS App

New blog post from Steve Smith, one of the Chariot architects working in our mobile practice.  Steve is currently working on updating the mobile app for our Emerging Technologies conference and will be posting articles from time to time as he finds challenges or discoveries.

Here is an excerpt:

The other day, I found the need to execute some JavaScript from a native iOS application.  After doing a little research, I discovered that the UIWebView has a stringByEvaluatingJavaScriptFromString method.  So I decided to create a quick little proof-of-concept to see how to invoke some JavaScript using this. I am not going to walk through all the details of creating a project, etc. and will cut right to the important aspects of making the JavaScript call from the objective-c code.
We are going to need a JavaScript function to call and a UIWebView to evaluate the JavaScript. It would be nice if the JavaScript function took a parameter as well, so we could also prove out the passing of values.  Here is the JavaScript function that I will use:
1var area = function(diameter) {
2     var radius = diameter/2,
3     area = Math.PI * radius * radius;
4     return Math.round(area*100)/100;
5};


Read more

Monday, January 10, 2011

An Introduction to Mobile Device Detection

One of our architects, Steve Smith, recently posted this on his blog:

These days, there are many ways to browse the internet.  There are desktop browsers, mobile phone browsers, tablets, tablet/phones (e.g. Dell Streak), etc. all with different screen sizes, resolution, and capabilities.  How do you render an appropriate view optimized for the device accessing your site?  The answer is device detection.
The two main approaches for device detection are server-side detection and client side detection.  Server side detection involves determining the device at the time of the request and then presenting the appropriate view.  Client side detection involves manipulating the view after the content has been sent to the browser.

Read the full post..



Wednesday, November 10, 2010

Post Presentation Thoughts from our Mobile Seminar

Kevin Griffin was one of the presenters at our first Mobile Seminar Breakfast. Below is a recap of his thoughts after he finished his presentation.


Yesterday I presented at the first in a series of events for Chariot Solutions, the topic was 'Mobile Design Concepts'.

My goal was to try present things that I had learned/seen/been shown/done over the last couple of years, and try to get the audience out of the 'desktop browser' mind set when developing for mobile.

I drew from a lot of people that I have seen/meet including Luke Wroblewski (@LukeW), Josh Clark/Tapworthy (@globalmoxie), Mike Lee (@bmf) William Van Hecke (@fetjuel) and Brian Fling's book 'Mobile Design and Development' which I still think is the first book anyone planning on a mobile project should read. I was probably influenced by many more folks than that, but they are the obvious ones to me at the time of writing.

Cont. reading..

Thursday, July 1, 2010

Mobile Musings from June

June has been a busy month for mobile, primarily because of Apple's launch of iOS4 and the new iPhone (antenna woes and all). However, presenting an update on that would be too easy; here are a few things you might have missed in all the hubbub.

CNET reported that merely weeks after Microsoft launch of Kin, they would be stopping development, and focusing on Windows Phone 7. 1

Android released 2.2 to developers with the notable additions being:
  • Improved performance
  • Use as a portable hotspot (certain devices)
  • Exchange support
  • Multiple keyboard languages 2
Rhodes 2.0 was launched under its new MIT license allowing developers far more flexibility and a broader scope to use Rhodes in developing applications. RhoSync remained under Rhomobile commercial license. The launch of Rhodes 2.0 brought with it some new features, primarily the metadata framework, which I have yet to get my teeth into.3

MeeGo, the joint venture between Intel's Moblin and Nokia's Meamo announced its "Handset Project Day 1" complete with video (http://www.youtube.com/watch?v=EW5wpg5epMs), which I thought looked pretty darn slick. 4

I'll be keeping a closer eye on MeeGo as its growth continues, and looking out for new Intel Atom-based devices, until then though; I'll just have to hope Santa comes early with a new Aava smartphone for me :)

Tuesday, March 9, 2010

Rapid Mobile Application Prototyping with PhoneGap

There is no doubt that carving out a mobile presence is a priority for many companies offering any type of product or service, or for start ups looking to gain rapid exposure. The Apple App Store has over 100,000 apps on it, and the Android platform is gaining ground. Those are just the cool kids – let's not forget the grandfather of mobile technology, Blackberry. Others in the class include Palm, Symbian and of course, Windows.

Multiple Platforms
With so many platforms available there is a risk of losing focus on developing and producing applications as resources are expended on supporting multiple platforms – a necessary evil as each presents different development environments and eccentricities.
This is why PhoneGap really stands out at the moment as four [1] of the aforementioned platforms share a common factor – a WebKit-based browser. This doesn't include BlackBerry's announcement [2] of their new WebKit based browser to come in late 2010, which takes us to five out of the six platforms.

Enter PhoneGap
Where does PhoneGap sit in this picture? Well, it jumps off the canvas and sits in your lap! PhoneGap allows you to develop applications using HTML, CSS and JavaScript and provides a JavaScript API which enables you to interact with a device's native functionality [3]. In addition to this simple application architecture, PhoneGap comes with build scripts/plugins (PhoneGap extension for XCode) which bundle up your pages into a deployable application.
The packaging and deployment to device for iPhone, Android and Palm was trivial; I can only speculate that the remaining platforms are equally easy to deploy. In light of recent Apple 'crackdowns', as of October 7th [4], 2009, it is worth noting that PhoneGap (version 0.8.0 and higher) is Apple approved.

The JavaScript advantage?
Anyone who has used a JavaScript library, Prototype, jQuery, MooTools etc, knows how powerful they can be. Anyone who has not used them can easily pick up JavaScript basics. The guys over at PhoneGap recommend using XUIJS[5] with PhoneGap as it does not contain a lot of cross-browser compatibility overhead and weighs in at < 10kb compared with jQuery at 24kb – although for simple functionality you may want to avoid using a extra library at all.
Due to the fact that we are ultimately aiming to work inside one browser implementation (WebKit), we are not held hostage by the browser compatibility issues that have haunted JavaScript for so many years. That's not to say that fragmentation in the mobile world is not an issue [6].

Now, I am not going to try to argue that these HTML/JavaScript apps offer greater performance or a better user experience over their native counterparts. However, I will say that PhoneGap will allow the rapid development of an application for multiple platforms, using a single code base [7]. This is ideal for prototyping or for apps that will have a limited life span and do not warrant the time and investment of producing native apps.Considering all of this in combination with developments coming down the pipeline, most specifically HTML5 (which includes WebSockets and Client-side database storage), the potential for these types of mobile applications is vast and genuinely exciting.[1] Android, iPhone (safari), Palm (WebOS) Symbian/S60(WRT) http://en.wikipedia.org/wiki/List_of_web_browsers#WebKit-based_browsers

[2]http://devblog.blackberry.com/2010/02/blackberry-webkit-browser-preview-at-mobile-world-congress/

[3]http://nachbaur.com/blog/phonegap-officially-permitted-on-the-app-store

[4]Checkout the road map for specifics: http://phonegap.pbworks.com/Roadmap

[5]http://code.google.com/p/xui-js/

[6]http://techcrunch.com/2010/03/04/mobile-fragmentation-forever/

[7]ok, you are going to have to tweak it for BlackBerry.

Wednesday, February 17, 2010

Mobile Platforms - Interview with Roy Rosin and Rick Rasansky

I am a little behind on editing a backlog of videos. As I continue to learn how to edit and not become frustrated with iMovie (why is it Apple can create so many great, intuitive products, yet this one is difficult to use! That will be another blog post for another time!)

This interview took place a few weeks ago, but it seems to be more relevant now with the release of Windows Mobile. I sat down with Rick Rasansky and Roy Rosin at their offices to discuss why it is important to be paying attention to mobile development. Since both of these gentleman have been in the mobile space since early on, they have a lot of experience to draw on.



Rick and Roy will be part of a panel at the Emerging Technologies for the Enterprise Conference (www.phillyemergingtech.com) on April 8th. They are part of a management track which is addressing different Buzz word topics (cloud, social media, mobile). The goal is to help managers have good, non-vendor driven information in their arsenal to guide their choices in 2010.

Sunday, January 24, 2010

Mobile development and your team

Throughout the next several weeks, we will be conducting interviews with speakers who will be speaking at the Emerging Technologies for the Enterprise conference (www.phillyemergingtech.com). These interviews will give you some idea of the material we will be covering.

The first interview is with Mark Spence of Transmogrify and Rick Rasansky of Yorn. Rick and Mark will be on a panel discussion in the management track discussing why it is important to pay attention to mobile development for you company.

We tackle a different issue here. Helping your development team get up and running in this newer space.

(As a note, I am trying to get better with editing. Continue to bear with me while I learn "on the job". Please note, I finally purchased a tripod for a steadier picture!)



Here are the links Mark mentions in our interview:

http://cocoawithlove.com/ (cocoa + iphone dev blog)

http://akosma.com/ (iphone dev blog)

http://github.com/facebook/three20 (three20 on github)

http://iphonedevelopment.blogspot.com/ (Jeff LaMarche's iPhone Dev blog)

http://blog.iphone-dev.org/

http://blogs.msdn.com/windowsmobile/ (WinMo dev blog)

http://www.christec.co.nz/blog (Chris Fairbairn's mobile dev blog)
From a design point of view, we like to look at these sites for inspiration:

http://tapfancy.com/

http://www.appsafari.com/

http://wirelessdesignmag.com/

Other useful sites for keeping an eye on everything mobile:

http://gizmodo.com/

http://www.eweek.com/c/s/Mobile-and-Wireless/