I offer a thumbs up to the idea of html5 instead of "native" for mobile.
I wrote a short app which demonstrates connecting iPhone to your
hosted sugarCRM account.
Shortly after that, sugarCRM changed a few things on their back-end
and that broke my demo app.
But I still have some code there, a comprehensive description of the
code, and some screen shots.
Here you go:
If you want to talk with me about this in person, chat me up at the next Meetup:
Also remember that at this Meetup we will have: PIZZA!
On 7/16/10, Phillip Jain <[address removed]> wrote:
> Since I have been doing "too much" Web2 & Social Network apps for some
> time. I recently looked at the issue of what next programming skill to
> acquire/sharpen and decided to dip toes into Rails 3 but instead invest
> time into Java/Android for now.
> I don't want to start a big flame language war - but would like this
> knowledgeable group to help answer my doubts on
> a. "*What about mobile*" (and convergence technologies e.g.
> widgets,SaaS/Cloud) and RoR - this is the main question for me.
> b. Check my assumptions/stark statements below .. and add their comments.
> c. I think HTML5 and RoR3 is the way to go for Rails 3 guys into 2011.
> Anyone got experience with HTML5 and RoR3.
> --- Phillip Jain
> Why I Decided NOT to do RoR3 for now .. and wait for HTML5/RoR3
> plugins/learning curve first.*_
> *Bottom Line Decision*: HTML5 is immature yet will drastically change
> converged technologies. It is better to wait for others to clarify the
> bleeding edge first.
> While I had done some quick web prototyping for RoR 2, some time ago,
> the opportunity to really USE it in a production large app never arose.
> Now that Rails 3 is a great thing for scaling, I was highly tempted and
> even got my college going kids interested going for the meetup but then
> the question of "what about mobile" came up, and we did not do so.
> Basically RoR development is too much like other Web2 for my tastes - in
> its scope & applications.
> 1. Microsoft Tools (.Net, C#, SQL Server, Silverlight) are proprietary &
> *behind the curve* and unless you are FORCED to use them, there is no
> particular reason to do so. I am told, that there is a chance that
> Microsoft has realized developer resentment and may be trying to
> deemphasize .Net as the only thing, now that it is so well integrated
> into actual deployments (i.e. Win7) that it doesn't need to be pushed
> any more.
> 2. *SaaS/Cloud*. Another problem with Microsoft is even their cloud
> stuff "Azure" is so so proprietary, it basically requires rewriting
> apps. This is true of Google AppEngine & Amazon as well which basically
> for MOST things require drinking their Koolaid. RoR seems to have a huge
> advantage here - *can someone comment on whether the Active
> Record/Scaling Database Layering is very effective in cloud Rails 3
> apps*? Can you simply prototype on a desktop and simply scale up on AWS
> - what kind of problems is one looking at? I know that it is a real pain
> for other languages.
> 3. "*What about mobile*". For a while there was hope for cross-platform
> development e.g. RhoMobile but then it was shot down by Mr Jobs for
> Apple's own evil anti-SDK slant. Android has a new Scripting Environment
> (ASE) that is trying to put php, etc. on android similar to Jython.
> Anyone think RoR is at all relevant to mobile at the client side - not
> just web backend?
> 4. *Step Back to Java/Android*. I think it is significant that Google
> pushed Java on Linux for Handset alliance not Python, etc. - to the
> extent of pissing off Nokia/Symbian and fragmenting the J2ME developers.
> But now it has 100,000+ apps and growing fast. So, for now, I decided to
> "reactivate" my Messaging OLTP/J2EE/JSP background at the same time
> while doing the Java Android thing as a learning project.
> 5. *HTML5*. However, I am emphasizing the HTML5 slant i.e. embedded
> WebKit with local storage can have significant parts in pure HTML5 and
> mostly the wrapper is native app. I think that with IE9 the game will
> tilt very hard and fast to HTML5 to the extent you can forget about
> traditional Web2 programming and take a quantum leap to cross-platform
> converged programming. Should be a piece of cake for Rails 3 plugins/