51–60 of 79 posts
I just want an Internet mobile device that provides the full net experience in the palm of my hands; FLASH & VoiP access!
Earlier quoted context omitted.
"He doesn't really mention in his post the fun fact that you've got to pay a fee so Apple can review/reject your app. Definitely not feeling warm and fuzzy about the investment so far." You'd rather they get flooded with an absolute ton of crap? The fee isn't _that_ much and it separates the boys from the men, so to speak.
Nah, I'm not opposed to that, really. Ideally they'd have enough reviewers to handle that, though. A somewhat-non-profit like Mozilla handles it for Firefox extensions. For us, the annoyance is just that we have to wait on them for multiple steps in the process when there's no guarantee they'll even post a produced app to the store. We'll hedge our bets, though, and make a slightly useful app to see how annoying the…
Android FTW?
Has anyone here played with an OpenMoko ? I have examined one, but have so far avoided putting out the cash to buy one. I have always disliked the cultist and elitist aspects of Job's company. I see Apple as no better, and possibly worse, than Gate's company. I think, that if you are trying to make money to live the next 3 years comfortably, writing iPhone apps may be the way to go; but if you want there to be a worl…
Earlier quoted context omitted.
In simple words. There is no standard in the mobile industry for application developers. You have to tackle iphone and bb differetnly. You have to tackle ATT and Verizon differently. My point is not that Apple is more open than others. That still does not make it standard. Yes you can build apps that polls a server etc..., but again when building apps, there is no standard. Iphone apps do not work on Symbian phones.…
That's kinda like complaining that there is no standard in the desktop software industry, because you know.. UNIX developers and Windows developers don't have the same API. That's rather silly. Quite simply, there are two tiers in the mobile industry now: smartphones and feature phones. On the feature phone tier, having to jump through bullshit hoops was and still is standard - getting certificates from the carrier,…
Saying it is simple shows me that you do not have much experience creating mobile applications.
If you develop for windows I assume it will work in every country, for every machine that runs windows, regardless of the machine manufacturer and the insternet service provider. Write once deploy nearly everywhere. Try that with mobile apps.
If you develop for Symbian phones, although one app may work on T-mobile UK networks, it may not work for T-mobile in the US.
It is anything and everything but simple.
EDIT: I am saying this after tools we had built using Twitter SMS API, NMS SMS API, Kannel, 41411 SMS API,as well as working on Mobile IM for Symbian, Call Interceptor for Brew, CallBack for all platforms including an Iphone web app, Backup application, Mobile Device Management Servers for Symbian and Brew, Infinite number of mobile games etc....All products being deployed in every continent save Australia. In every single case clients find it to be a pain. I wish writing and deploying mobile apps were as easy as it is for desktop apps.
Earlier quoted context omitted.
A friend who played with the new Android device say that there's no way it's comparable to the iPhone... but yes, this one device isn't what Android is about.
I played with both. Android looks like a serious threat. The big question is how will google treat the Android developers. Phone vendors don't like developers massing around with their devices, users do like it. The vendor that will reach the finish line first will be the one that will produce a stable product with a solid API where 3rd party software won't damage the phone performance. If my theory is correct at the…
Well, Apple has already gotten some of our money. We purchased some Macs solely to develop an iPhone application for one of our endeavors. Now, though-- given the lag with even getting approval (so we can get to the stage of installing a test app on test phones), we're rapidly losing excitement about investing in the project. And then there's this kicker-- once our team spends time developing it, there's a chance it…
"He doesn't really mention in his post the fun fact that you've got to pay a fee so Apple can review/reject your app. Definitely not feeling warm and fuzzy about the investment so far." You'd rather they get flooded with an absolute ton of crap? The fee isn't _that_ much and it separates the boys from the men, so to speak.
Earlier quoted context omitted.
Android FTF. I used it, and it was pretty terrible. If you think the iPhone is slow...
Maybe we should give it a chance to launch and iterate a bit.
Earlier quoted context omitted.
Maybe we should give it a chance to launch and iterate a bit.
Yeah, of course. But it was very slow. And the interface wasn't nearly as polished as the iPhone's. I don't know how much iteration will help them.
Earlier quoted context omitted.
I played with both. Android looks like a serious threat. The big question is how will google treat the Android developers. Phone vendors don't like developers massing around with their devices, users do like it. The vendor that will reach the finish line first will be the one that will produce a stable product with a solid API where 3rd party software won't damage the phone performance. If my theory is correct at the…
What happened with Palm, then?
Seems like Palm did the software part great, and failed majorly on keeping the hardware up to date (they missed the boat or were late to the party on flash memory cards, color screens, and wireless, that I can remember anyway).