From all the app code generators I've seen and used, the experience is absolutely horrendous. Memory leaks, does not five you full access into the API etc... It's a lot easier to suck it up and learn Objective-C than having to deal with these tools.
I think this is a cool idea, but I think it might make sense to aim it at the Titanium platform. As a Titanium developer myself, I think this would go over extremely well in our community. I would assume that anyone who is comfortable enough in Obj-C wouldn't really want to use an app builder like this, but titanium devs are already using a "builder" of sorts since they are using the framework. Just a thought!
If you want to write iOS things, don't fool yourself into thinking there is a way around learning Objective-C and Cocoa (Touch).
Nice idea, but it seems like the only kind of apps you can build are apps that takes stuff from the web and put it inside the app.
Well done that they have been able to build it though. How do you think they are porting the html/css code to Obj-C?
Has anyone located some code generated by this system? Would love to take a look through it.
How is this any different than building the GUI using built-in Storyboards/Interface Builder?
If your app does anything more than just displaying content, it still seems like you'll have to jump into the code.
Well, so easy a caveman can do it!
Except the product will also looks like it's designed by a caveman.. :D But pretty cool for the everyday idea man out there
Just curious, how did you guys derive to this number? "Reduce iOS development cost and time by 80%"
Price is $299 PER APPLICATION? or is that a typo?
RubyMotion?
300$ (a theme) for IOS themes ?
Nice idea, but the sample code they show in the screenshot uses "FALSE" instead of NO (the Obj-C standard boolean literal).
I'm not sure how they did that (#define?) but stay far, far away. Imagine if you opened up a Ruby codebase and found out I had aliased NO to be the same as the language builtin false... yeesh.
Also, setting boolean instance variables to NO in init is silly since Obj-C objects are calloc'd, so all ivars are guaranteed to start with default values (nil/0/NO).