×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Actually, I'm pretty solidly opposed to writing native applications for iOS.
That may be an OK in a non-commercial environment, but whether you and I like it or not, we're seeing customers demanding native device apps that they can roll out into the field.
iPhone/iPad is still the semantic king in the field although Android is closing the gap.
Personally I prefer writing browser apps that work on any device, but that's not always accepted.
PhoneGap looks promising because it still allows access to the hardware level gadgets from my understanding.
The store thing is definitely irritating though. Especially the part where they want 30% of every app sold.
Regards,
Richard Schoen
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site:
http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT
----------------------------------------------------------------------
message: 1
date: Mon, 02 Jan 2012 10:59:34 -0600
from: Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>
subject: Re: [WEB400] Android Development for the IBM i
Actually, I'm pretty solidly opposed to writing native applications for iOS. If an application requires cross-platform support, I'll stick with a browser-based technique (like the PhoneGap technology Henrik spoke of). But if I need to take advantage of the native hardware, I'll write it for Android. I personally don't want to waste any time on jumping through Apple's hoops. That's MY New Year's Resolution :).
Joe
midrange.com
