Interested in interaction or web design? Building complex 3D animation engines? Creating rich web interfaces with functional programming? Scaling realtime, distributed server infrastructures? Extending the internals of low-level iOS and Android frameworks? Let's talk.
Our team is breaking new ground in mobile design and solving real problems for an eager community. If you want to be part of this talented team of engineers and designers, send us an email to [email protected] telling us why you’d be a good fit. We have immediate need for experienced iOS and JavaScript engineers. We'll consider remote if you are exceptional.
We hear you on the list performance. There are significant performance improvements we've made in version 2.0, over the previous version. We’ve also identified more ways to make Pixate faster, especially for CollectionView and TableView, and will roll them out as soon as we can. Performance is our #1 priority, so expect it to continue to improve.
In addition to that, how you use Pixate and what CSS selectors and properties you use can have a big impact on performance, just like with CSS on the web. We’ll be making those kinds of issues clearer for developers through "best practices" posts, as we continue to build our product.
Bootstrap is totally configurable, we're just showing the default styling. In terms of Apple allowing alternate designs, I think they encourage it, just look at Garage Band ;-).
One real-life example (told to us by a customer): imagine you have a "spring sale" that you want to promote to your customers. You want to customize the look of the app, perhaps rearrange a few things, change the look, etc. You want to do this for a period of time, and perhaps even for a certain geographic or demographic area. With Pixate, you could push new CSS and assets as needed, then revert when the sale is over. You could even push different looks to different users, etc. Effectively, Pixate is the flexibility of web with the power of native.
Storyboards aren't dynamic. Our CSS implementation not only lets you style your app, including animation and transition, but it can be changed at run time, either locally or remotely -- just like the web. Think of storyboards/xibs as a layout mechanism, and ours as a dynamic styling mechanism.
This isn't an all-or-none situation. You lose none of the fidelity of native development, it's just an abstraction of code to markup. It's all natively executed using native APIs. Typography, absolute pixel postions, animation, and much more is all there.
Pixate Engine is a native framework for iOS (and Android soon) for styling your native controls using the CSS syntax. There's no web here other than the shared syntax of CSS. For example, to style a native UIButton:
Pixate is not an all-or-nothing solution. You can just style what you want via CSS, and do the rest in code. Do it all in code and just inline some CSS if you like. This isn't a "use UIKit or us" type of decision, but more of a "how can I write a lot less code and more dynamically style my apps". Lastly, at the Enterprise level, we offer source code escrow.
We believe that taking something complex and adding a familiar, declarative syntax, while keeping it all 100% native, will appeal to both developers and designers. We believe so because we've asked many of them.
- the raw video is 58 seconds
- at 24 frames per second, that’s 1,392 frames
- on a single, high-end GPU, it takes 168 minutes to render a single frame (we render on 8-GPU systems)
- that’s a total of about 3,900 hours of render/compute time