On Jan 10, 10:23 am, awaybbl <[email protected]> wrote:
> I think Roger missed the point of this entire group.
LOL. Seems lately it is to complain about "Roger."
>
> The original intent of iPhoneWebDev, was to support WEB developers who
> were trying to make their sites more iPhone friendly, not to supplant
> native apps. In fact the group was started prior to the existance of
I think you missed most (if not all) of what Roger was talking about.
> any API/SDK for building native apps.
>
> I do agree with Roger that trying to "fool the users and/or the Apple
> Store into seeing a Web app as a native app is clearly folly",
> however, it is not folly to try to improve the usability of existing
> web content and being able to render a better user experience for the
> iPhone users who would browse those sites.
Agreed. But iUI is a big step in the wrong direction.
>
> Native apps clearly have an advantage over web apps since they can
> make better use of the underlying native hardware at native speeds,
> whereas web apps must rely on the interpretation and emulation of code
> from within the browser. Using tools such as big5 and phonegap does
> help a little towards building "native-like" web apps within a native
> app shell, but still can't match the performance of an app built
> entirely in native code. I personally have used big5/phonegap and have
> successfully submitted 20 apps to the appstore, with one of the titles
> actually in the top 100. I wasn't proud of the performance, but it got
> the job done, and after all, at the end of the day that's what's
> important.
You might do better if you pay attention to what JS developers (like
Roger) post.
>
> Frameworks like iUI served their purpose, they allowed the early
What purpose?
> developers of iPhone Web Apps to build list based apps that had a
Lists are HTML.
> somewhat similar look-and-feel of native apple apps. Did it match the
That's CSS.
> performance? NO. Did it get the job done? YES. Could it be improved?
Done in what way? Anything built on top of iUI is junk by association
(same for any Website built on jQuery, Prototype or the like.) See
how history repeats itself?
> YES. Kudos to Joe Hewitt for his contribution to the iPhone community
Stop shouting. And it would have been better if he kept his demo to
himself. I am sure he didn't envision it being recommended as a
"framework" years later.
> during those early days. Even bigger Kudos to the hundreds of active
> participants in this forum who've helped others improve their
Nope. Boo to most of the "contributors." This group sets mobile Web
development back a decade (and the party's over.)
> understanding of how to develop for the iPhone. While I've only used
> iUI in one web app, the discussions in this group helped immensely
One too many.
> during my repurposing of my own websites so that they could be viewed
> better on an iPhone. Over the past 2 years, I've been able to
> "iPhonify" almost 100 of my web apps, with lots of help from the
> information gained on here and other groups.
Mostly on other groups I suspect. The mantra here seems to be "pick a
framework" (never mind if they are all junk.) Sound familiar?
>
> I will always be a proponent of the community approach to solving
Same here.
> problems, and iPhoneWebDev was/is a great place to work out those
> problems related to building functioning web sites tailored to iPhone
> users.
Not so much (up until recently!)
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"iPhoneWebDev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/iphonewebdev?hl=en
-~----------~----~----~----~------~----~------~--~---
