Thanks David. I took a look at big5apps. I dont see a difference between what they are doing and phonegap. If you, or anyone else, does have an opinion on which is "better", then I am all ears.
Many thanks for your answers. On Nov 3, 1:37 pm, davidroe <[EMAIL PROTECTED]> wrote: > not quite sure of your question, but languages used are Obj-C, HTML, > Javascript, CSS (using GWT to create the Javascript). I wrote my code > prior to learning about PhoneGap. I have also since found big5apps but > have not really looked at it - it might be of interest to you. > > On Nov 3, 9:05 am, mike7 <[EMAIL PROTECTED]> wrote: > > > Thanks Dave. I did not know about the 25k limit on the iphone. That > > does propose some challenges for GWT. > > > Out of curiosity, what languages are you using inside of your obj-C > > wrapper? Did you use PhoneGap as your starting place for this? > > > Any hints / opinions on lessons learned thus far on the approach you > > are using? > > > Many thanks. > > > On Oct 29, 11:26 am, davidroe <[EMAIL PROTECTED]> wrote: > > > > GWT is a processor-intensive way of building an interface and > > > therefore not ideally suited to the iPhone's low power CPU. this made > > > development harder than it should have been. an example is rendering a > > > list of items using GWT to build panels and widgets where items may > > > take 0.2s to render, leading to an application that lags for 2 seconds > > > just to build a list of 10 items. you end up keeping widget objects > > > and the DOM at a distance, which is obviously not ideal. > > > > as a pure web app, you also need to consider client side caching, and > > > the iPhone will only cache objects under 25K. as the generated GWT > > > code all resides in one big file, this results in a scenario where the > > > device refuses to cache and always requests a new copy from the web. > > > this in itself is a good reason to deploy the code locally, wrapped in > > > a binary. > > > > I'm not a huge Obj-C fan, although I like it more now that I've picked > > > it up and written some code. Nevertheless, I still prefer web > > > technologies as they are cross-platform and generally more flexible. I > > > therefore would choose embedded web apps in the future over pure > > > native clients, but that is just the nature of the projects I am > > > working on. WRT tohttp://riflethru.com/Ihadwritten code to > > > investigate what was possible, but the project overall is still not > > > feature complete. I need to enable bidding on the application before > > > it will get released to the App Store. > > > > /dave > > > > On Oct 29, 6:50 am, mike7 <[EMAIL PROTECTED]> wrote: > > > > > Thanks Dave, > > > > This is interesting. I presume you built the riflethru app? I would > > > > like to hear a little more about this development method. Can you > > > > give me some highlights? For example, how long did it take? Any > > > > unexpected hiccups? I looked for it in the app store and did not > > > > find it... was it not published? > > > > > Many thanks, > > > > Mike > > > > > On Oct 28, 6:19 pm, davidroe <[EMAIL PROTECTED]> wrote: > > > > > > I think that being in the app store is likely to attract more users to > > > > > your application as this is where people tend to look. Additionally, > > > > > not all apps in the store cost money, so why not use it to organise > > > > > web apps? That said, I think that the user expects to find > > > > > applications that will run natively, rather than something that will > > > > > just launch an instance of Safari pointing at your web app. > > > > > > If you are following PhoneGap, you will see that some developers are > > > > > releasing hybrid applications that are written using web app > > > > > techniques but have access to the phone's native functionality. This > > > > > is done using UIWebView and a wrapper around your web app. As far as I > > > > > am aware, such applications will not fail the Apple review process > > > > > just because they were developed using this approach. There are > > > > > definitely advantages to this approach, especially if you are a web > > > > > developer with no experience using Obj-C. > > > > > > I played with something similar a while ago forhttp://riflethru.com/ > > > > > to see what is possible. I ended up with a native application with > > > > > embedded GWT, so all the HTML/CSS/JS sit as resources inside the > > > > > binary and are loaded locally rather than over the wire. > > > > > > /dave > > > > > > On Oct 27, 11:55 am, John <[EMAIL PROTECTED]> wrote: > > > > > > > > Can anyone list some iphone apps that were written in GWT and > > > > > > > have > > > > > > > been published in the app store? > > > > > > > Maybe I'm being thick but... my first impression when I read this > > > > > > question was... why/how would want to sell it through the App Store? > > > > > > > Since the GWT app is really just a 'web site' that works with the > > > > > > iPhone, there's no executable to sell. It could be that the obvious > > > > > > answer is that you want to sell your app on the App Store is to make > > > > > > money. But since your GWT app is just a web app, wouldn't it be > > > > > > better > > > > > > to just make sure your target audience knows about your GWT app and > > > > > > maybe you could charge for use of the app by forcing an > > > > > > authenticated > > > > > > login that was just restricted to 'paid' users. > > > > > > > Maybe it's the jet lag kicking in but I'd never even thought about > > > > > > wanting to sell a 'web app' from the App Store. > > > > > > > Am I missing something you're trying to accomplish? > > > > > > > - John - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" 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/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
