voyent
mobile apps, dynamic images, sessionrenders etc.  XML
Forum Index -> Contributor's Corner
Author Message
michelle2

Joined: 14/Nov/2007 00:00:00
Messages: 449
Offline


look at this
http://web.me.com/cannonwc/Site_6/StoryBoard.html

Also see this Post.

http://www.icefaces.org/JForum/posts/list/3310.page


This book is a great reference, though dated.

Has a very big chapter on Java advanced imaging. seems out of place, but extremely interesting. The book was wrtten in 2000, but the topic seems much for suited to today's environment. Probably was noticed back then.

Special Edition Using Java™ Server Pages and Servlets
by Mark Wutka
Publisher: Que
Pub Date: October 20, 2000
Print ISBN-10: 0-7897-2441-3
Print ISBN-13: 978-0-7897-2441-0
Pages: 768
[Email]
michelle2

Joined: 14/Nov/2007 00:00:00
Messages: 449
Offline


I've posted a prelimary walkthru of the imageshare application we are working on.

http://mooncatventures.com/blogs/atlantis/archive/2009/06/11/announcing-imageshare-our-first-native-iphone-application.aspx

We realize that the majority of users in the icefaces community are not concerned with mobile development.

But

ImageShare is unique, first of all it will have a web equivalent, early on we realized that like google wave or twitter we are going to want to include non mobile users in the fold.

So imageshare is beging developed concurrently for the iphone and an icefaces rich web application.

Secondly imageshare is going to push the direct push technology in icefaces to limits I'm sure some of you did not think is possible.

Watch and see
[Email]
michelle2

Joined: 14/Nov/2007 00:00:00
Messages: 449
Offline


Here are the possible deployment configs for tagalong

The printer module can be deployed seperately or with icebridge and provides printing capability for imageShare and arshow 2.

Icebridge provides sharing and chat for imageShare , wifimedia and artShow2 .

network module can be deployed seperately or with icebridge.


http://web.me.com/cannonwc/Site_7/Welcome.html
[Email]
michelle2

Joined: 14/Nov/2007 00:00:00
Messages: 449
Offline


New site to track our native iphone projects

http://sol3.typepad.com/tagalong_developer_journa/
[Email]
mobilezealot

Joined: 25/Jun/2009 00:00:00
Messages: 1
Offline


Hi Michelle,

I have been reading your web page because I am trying to leanr more about iPhone development. I know iPhone web apps can be created using traditional web technologies.

I know that the new iPhone SDK has a lot of features. I'm just curious why tag-along framework? What advantages does it have over the SDK? Why a new framework?

Mike
http://www.mobilezealot.com
michelle2

Joined: 14/Nov/2007 00:00:00
Messages: 449
Offline


mobilezealot wrote:
Hi Michelle,

I have been reading your web page because I am trying to leanr more about iPhone development. I know iPhone web apps can be created using traditional web technologies.

I know that the new iPhone SDK has a lot of features. I'm just curious why tag-along framework? What advantages does it have over the SDK? Why a new framework?

Mike
http://www.mobilezealot.com 


Is that how its coming across. Maybe I need to clarify some of my pages.


Tag-along, and thats only a working title is just a term applying to my idea for a backend framework.

There are basically 4 kinds of iphone applications.

1) webbased - these don't use the sdk, are not client/server and use traditional web 2.0 programming components, javascript , icefaces components etc.

2) hybrid applications - These are built using the sdk, use some of the web 2.0 widgets above, mostly javascript, because icefaces components are serverside.
These apps usually connect to a backendserver or web webapp. They may or may not persist data to the device.

3) native apps that access the web, this is the traditional client/server approach , web pages may be data minded and views created from them, or operations performed via http post. These apps usually persist data to the device.

4) stand alone apps, simple calendars, address books, games, these may or may not connect to outside servers, ie. facebook, twitter, but they have no server support of there own. They almost always persist data to the phone.


Now with that in hand , lets talk about tag-along .

tag along describes a application server framework for 1,2,3 above.


1) In the simplest case you may have a native application, that access outside web sites ie. facebook, myspace but uses a simple backend server which provides for finding and using printers on your network.

For this , you could just run a simple embedded jetty server. WHICH YOUR NATIVE APP CONNECTS TO.

2) A much more complicated native app, connects to facebook , myspace etc. however connects to an icefaces application which provides among other functions, server push of updates, consolidation and mashups of all messages from each service and single user login.

In this case the user needs to have a tomcat or other server on some local area network. This also usually implies you need to provide for a proxy server or have a sticky ip address if you want to access it from outside your local subnet.


FINALLY

Its all in marketing.

If you want to target different types of users with a single application.

Then you can make the application scalable.

Take the app I just described, if the user wants to just get at their facebook and myspaces pages then all they need to do is download a free executable jar and add it to the startup script when they start their pc or mac. This allows them to print and access just there local network. Many users will do this without a single thought.

HOWEVER OPTIONALLY

The more advanced user may download a different execuatable, this one could deploy a tomcat or jetty server, with an icefaces app war and possibly set up a network proxy.

When the native app detects the "bridge" server is will ungrey or make visible the advanced feature tabs.

Its my opinion that if you don't take the above steps you either only make available simple apps or target a different user with different apps. Otherwise your going to scare your user off with too much complexity.

MEANING

LOW RATINGS, and in the app store your rating is the whole game.

I would suggest if your interested in Iphone sdk development.

1) Join the application developer program, there are a ton of resources.
2) watch the getting started videos.
3) do some of the simpler tutorials.
4) get a book on objective-c programming, your going to spend a lot of time learning that, the best way is work through a lot of examples.

Once you have a particular model for your backend than either design somekind of server, php, java, lets assume java because you use icefaces or better yet download an open source appserver (tagalong).

Kind of long winded but anyone thinking of doing this NEEDS this info.

Update: I noticed your webpage, so I think with the above you should have a pretty good understanding to make your decision.


The app I described above is called lifeshare , I'm really just getting into it, it uses some new sdk 3.0 stuff which is very , very new and mainly trial and error. Hopefull I will have it ready in to app store sometimes in august.


Tagalong , the backend for lifeshare apps is maybe 30% complete, I will deploy a fresh copy to my svn server next week, for anyone can download it and play with it. Its no where near ready. But as of night before last it now works with apple's push notification service.
[Email]
michelle2

Joined: 14/Nov/2007 00:00:00
Messages: 449
Offline


mobilezealot wrote:
Hi Michelle,

I have been reading your web page because I am trying to leanr more about iPhone development. I know iPhone web apps can be created using traditional web technologies.

I know that the new iPhone SDK has a lot of features. I'm just curious why tag-along framework? What advantages does it have over the SDK? Why a new framework?

Mike
http://www.mobilezealot.com 


For Mike, or anyone else having trouble with this topic.

Don't feel bad, I seem to be among a small minority using java as my backend server, most developers seem to perfer php because its small, lightwieght and cheaply deployed. However it lacks the security and flexibility for enterprise level apps. I think might change a bit now that there are some sdk features that require more complex servers.

I have a good example of what I was discussing, here's a test case I put together the other night to test some lifeshare functionality.

http://sol3.typepad.com/tagalong_developer_journa/2009/06/a-marriage-made-in-heaven-sessionrenderer-and-push-notification.html


use Case

The native iphone application can upload images taken with the phones camera or stored in the photo library to an icefaces web page, shown with a few images in the above picture.

Test Sequence

1) User starts app, auto logon to website
2) user snaps picture
3) user clicks upload , which initiates http post to web app
4) webapp servlet , adds new image to application scoped image list and executes a session renderer bean, session render bean sends message request to Apple push notification Service via secured ssl connection.
5) Alert to all iphones running the app "Hi, user xxx has just uploaded a new image.. Available immediately".

6) All sessions where pushed the update.


Fun stuff , isn't it???
[Email]
 
Forum Index -> Contributor's Corner
Go to:   
Powered by JForum 2.1.7ice © JForum Team