Bradypodion.js

The mobile web app framework with a vision

The post-platform vision

Doesn't seem like these app's only difference is that on Android the header is left aligned, while on iOS it's centered, does it? There is much more thought to be put in post-platform than just dynamically adding a few CSS classes here and there.

Most Frameworks out there claim to be cross-platform. What that means is, they take technical differences of the platforms into consideration and ship something, that somehow works, to each of them. That working thing isn't necessarily the most beautiful or even usable at all, because platforms are not only differentiated by their browsers capabilities, but by fundamental user interface concepts. Ignoring this simple fact made cross-platform a synonym for bad user experience – and that's why we had to come up with a new term post-platform.

On the shoulders of giants

Bradypodion doesn't reinvent the wheel. Much rather it connects and applies existing tools and community conventions intelligently on a high-level. You'll have a strong and trusted foundation you can build amazing apps with – in no time.

angular's logo jquery's logo grunt's logo bower's logo github's logo travis's logo

Modular CSS Architecture

CSS preprocessors, mixins, variables and stuff, nothing new here, right? Turns out the more CSS you put in the mobile browser, the fancier you design your selectors, the slower your apps gets. That's why we focus 100% on the output and therefore performance of our CSS. We don't have a cool and colorfull demo page where you can see 8 pre-built themes, but we have the right tools so you can easily build exactly the CSS modules and themes you need – and nothing more.

Intelligent defaults & conventions

We strongly believe that a framework should offer defaults to the developer. This means Bradypodion takes the context of the current operation and tries to do the right thing – out of the box. This way, following our conventions, most of the work will be done for you. The only thing you have left is focusing on the parts that make your app truly unique.

Accessibility built in

Even though we think configurability and modularity are good things accessibility is one of the features you won't we able to disable. It's built right into the core of every component. Being a web framework does not only mean using HTML, CSS & JS – it means making your content accessible for everyone. The way AngularJS works we're touching HTML elements anyways, so ARIA attributes you wouldn't care about (sorry) are automatically applied – without an extra thought, or cluttered templates.

Yet another mobile framework?

Bradypodion is something we wished had existed back in 2010, when we started working on mobile web applications. Over the years it became pretty clear that nothing out there will meet our requirements – maybe ever. So this is nothing we wanted to create, or even maintain, but it's born out of necessity.

Hard problems first

Bradypodion is built by a team of two, so we focused on the hard problems first. This has two implications.

Read more on our blog

Stop talking about the web as the future
We shipped iOS 7 UI only 7 days after its announcement

Bradypodion is
MIT licensed and
open for everyone <3