On Wed, Apr 11, 2012 at 12:55 AM, Ricky Clarkson
wrote:
> And a pretty negative perspective on at least some of those:
>
> http://java.dzone.com/articles/multi-platform-frameworks-0
>
> Still, nothing conceptually against the concept of a multi-platform
> framework that holds water. They don't ac
On Wed, 11 Apr 2012 06:55:30 +0200, Ricky Clarkson
wrote:
And a pretty negative perspective on at least some of those:
http://java.dzone.com/articles/multi-platform-frameworks-0
Still, nothing conceptually against the concept of a multi-platform
framework that holds water. They don't actua
And a pretty negative perspective on at least some of those:
http://java.dzone.com/articles/multi-platform-frameworks-0
Still, nothing conceptually against the concept of a multi-platform
framework that holds water. They don't actually *have* to cater to the
lowest common denominator, even thoug
A few more cross platform solutions:
http://www.madewithmarmalade.com/marmalade
http://www.anscamobile.com/corona/
http://www.adobe.com/products/air.html (mentioned again for completeness in
this message)
Two solutions that use Java to cross compile to Android and iOS (but have
very large turnarou
I see your point, but for a small developer it is a royal pain. I don't
have time and money to develop 2 full applications. I would rather develop
1 application and have it run on both phones. This doubles my time and cost
since I have to build and test on 2 platforms. My users don't really care
ab
They probably don't care at the moment because PhoneGap is marginal, but if
they start seeing an increasing number of applications written with
PhoneGap that look very similar on Android and iOS, I certainly wouldn't
exclude the possibility of them excluding apps written with it. It doesn't
have to
Agreed. I doubt they would flip flop again on it.
On the web framework side, you have Sencha and jQueryMobile. PhoneGap will
work with either. With Sencha you get a lot of hand holding and you are
back to coding most everything instead of doing markup.
I'm doing a mobile app using HTML5, CSS, and
I would be stunned if they did that. The reason they changed their
mind was all the push-back from developers.
2012/4/9 Cédric Beust ♔ :
> I've heard good things about phonegap in general but I would be very nervous
> writing my apps with it because Apple could once again change their mind
> abo
I don't know if it's faster to build 2 or use a framework like
PhoneGap. One thing about Android/iOS is there are thriving
communities providing support/libraries/tools. PhoneGap is a niche
(although I think it's Adobe's future in mobile apps, so maybe it
won't stay niche).
One things about mobi
I've heard good things about phonegap in general but I would be very
nervous writing my apps with it because Apple could once again change their
mind about accepting applications that were not written natively with XCode.
--
Cédric
On Mon, Apr 9, 2012 at 2:53 AM, Steven Siebert wrote:
> Thi
I wouldn't want to invest time in learning at dead-end technology.
Flash/air/actionscript is on the way to oblivion IMO. Even Adobe
seems to know it as they are de-emphasizing flash in favor of HTML5.
On Mon, Apr 9, 2012 at 4:19 PM, Sam Reid wrote:
> I recently did some prototyping with Flash/Fl
I recently did some prototyping with Flash/Flex/AIR, and it seemed like it
worked well when I tested the same codebase on iOS and Android, and I was
able to develop and test on all my devices (iOS and Android) from Windows.
And it provided a decent emulator for quick turnaround time.
Sam
On Mon,
It definitely is not about padding my CV!!!
>From the answers, I can see its not easy to choose a path.
Keep the suggestions coming though.
Rakesh
On 9 April 2012 22:07, Robert Casto wrote:
> There are more considerations than a resume builder or making sure the
> application is a perfect fit
There are more considerations than a resume builder or making sure the
application is a perfect fit for the platform. Sometimes you need speed to
market and want to target both platforms, or you want something that works
consistently so you can support it easily and document it for users easily.
Th
If one of your goals is building your resume, I wouldn't mess with
these 3 party frameworks that "wrap" mobile dev. Also, the results
aren't as nice and the idioms are different on each platform, so these
apps become "least common denominator" apps that look amateurish IMO.
Even when you wrap it,
I agree with Steven, Phonegap is a good alternative if your strength is on
JavaScript and HTML. You must need to make some adjustments mainly in the
display, but using phonegap + one or two javascript framework (jquery
mobile, sencha mobile, etc...) would do the trick for u.
I use both approaches
This might be worth a look http://phonegap.com/
Probably should check out the capabilities and limitations of the framework
in regards to both your function and non-functional requirements you listed
before going forward with design.
S
On Mon, Apr 9, 2012 at 5:48 AM, Rakesh wrote:
> Hi guys,
Hi guys,
I know next to nothing about creating IOS/Android apps except that
things change constantly so I wanted to get the group's advice on
something I am considering developing soon.
The requirements are initially quite modest:
1. Ability to look up ingredients and show related content.
2. Se
18 matches
Mail list logo
