Show HN: Bootstrap for Native iOS Apps

How far are you planning to go in your support for css properties ? css animations/transitions ? Positionning (top, left, right) ? There are a lot of similarities, but by going very far you may end up rewriting a lot of the storyboard xml in a css format... Then maybe later on, you'll want a WYSIWYG css editor on top of it, and i'm a bit wondering whether you won't have ended up rewriting absolutely everything.<p>From my personal opinion, CSS is nice the first 10 minutes, or whenever you only have a few element to style, but styling a complete app along with animations between states makes you really want to stay away from it as far as possible for mobile apps (and especially ios where resolutions are quite standard)...

This is a great product.<p>First there was the native client era on desktops that involved twiddling around with swt, gtk, qt and windows programming.<p>Then came the advent of webapps with more uniform abstractions of client side js frameworks and css3 and dozens of toolkits and decorators around these.<p>Then came the mobile era with a new breed of native v/s web applications. Nowadays, the general opinion I hear is that no one really likes webapps on mobiles. But we as a community actively are trying to port over the abstractions of css/js frameworks to native mobile so that developers can continue being comfortable while programming devices that function at the whim of Apple and Google.<p>I wish there were a timeline of sorts of all the paradigm shifts that programming user experiences has undergone over the last decade.

Trying to turn native apps into template-styled web apps is just backwards; you're discarding the fine attention to detail, typography, pixel-positioning, scaling animations, etc, that can make native apps so great.

Quite a few things confuse me here:<p>How is a system based on CSS stylesheet native?<p>Why is it 1500 dollars per day to do what seems to be templated app development -- many other companies offer this at far far lower rates (think 50 dollars or less for a complete app).<p>Why only iOS? The purpose of templated distribution is to reach a wider audience, not a narrower one.

Is it just me or is it a bit ironic that an iOS related website doesn't work well on iPhone? All the screenshots o out of the screen, and you can't zoom out or pan to see them.

Any performance benchmarks of Pixate vs procedural code or vs similar DSLs, e.g. Teacup, Formation in Rubymotion?

I'm not a developer (or user) on iOS, but does it not have a similar design scheme for apps to Android (since ICS at least)? Would an app that looks like bootstrap fit in at all, and indeed would Apple even allow an app that resembles Bootstrap instead of its own design guidelines?

I still think CSS is one step away from making something awesome for developers of all flavors (from not developing at all to extremely competent in other languages) to make native apps even easier to code. I'm working on a more natural language version for iOS right now.

[Stripped-Down Non-Free Version of] Bootsrap for Native iOS Apps.