Ever since we launched CurdBee, one feature request kept hitting the top of the list quite often: CurdBee on mobile. Among the requesters the majority were iPhone users, followed by Android, with Blackberry, Nokia and others also making their presence felt.

CurdBee mobile was always on the plan, but it was on the back burner as we had to focus on other essential improvements. However, there came a time when a mobile version became that essential need. The first major call we had to make was whether we should go for native mobile application(s) or make a web optimised application or even both. We took our time to analyze all the pros and cons with these approaches and finally came to a conclusion on the path we should take.

We built a couple of prototypes using different platforms such as Sencha, jQtouch and jQuery Mobile during our initial experiments before finally settling with jQuery Mobile. The main reason for picking jQuery mobile was its compatibility across different mobile platforms. It took us a while to put together, and today we are releasing our first take on the CurdBee mobile experience.

At present, CurdBee Mobile is optimized for Time and Expense Tracking, as those are the features which most of our users will need on the go. Invoices and estimates can be viewed as well, with support for creating and sending them coming soon.

Try CurdBee on the go and let us know how you like it!

Image thanks to Rethinking the Mobile Web by Bryan Rieger.

Apps and the web have always had an uneasy relationship. While the application remained supreme for years, the Web 2.0 pundits promised us a future where the web would rise and take its place and users would only need a browser to do everything.

We’re still waiting for that day, and not only have applications remained, but they are now more popular than ever, and not just on the desktop. What happened?

The smartphone happened.

iOS or Android, Angry Birds or the NY Times, pick your poison, because they’re here to stay. Billions of downloads, hundreds of thousands of native apps and thousands of ways to make fart noises. Our world has changed forever. With the personal computer now sharing space with many other devices, we’re constantly being asked to look beyond the browser and focus on developing applications for those platforms.

But we won’t (and yet we will), and here’s why.

Inclusiveness

While there certainly are applications that cannot easily be duplicated in the browser of today because of platform (3D games) and connectivity (offline reading) limitations, there area a lot of native apps that are actually just front ends for websites. In fact, most websites these days have an iOS app, an Android app, and if you’re lucky, a Blackberry app.

That’s great (if you’re happy developing for less than 10% of mobile users)!

Nokia, the manufacturer with the largest worldwide market share as of Q1 2010 runs Symbian on its high end phones, and Symbian is by most accounts a dead or dying platform in terms of native apps. But people buy these phones, and people use them. We could develop native apps for iOS, Android, Blackberry, Symbian and Windows Mobile, but that would still leave out non-smartphone users. So we’d need to put together a mobile site as well. But why as well? Why not just go with a mobile site?

Of course, not having smartphone specific apps means social media experts will like us less and we wont be able to provide brand ambassadors with compelling conversation hooks to enter into communities and fuel advocacy. We will however be able to focus heavily on creating a compelling mobile experience for all our users.

We’re going to strip the Bee down to its basics and then wrap it in different paper for different platforms, browsers and screen resolutions. We want to make sure that your favourite online invoicing experience is maintained across all your platforms. We’re going to use lots of jquery goodness, plenty of great UX design and yes, we’ll be generous with the sprinkles too. It’s going to be totally yummy.

Simplicity

Developing a gateway that caters to every major mobile OS and browser combination out there isn’t going to be easy, but there’s going to be one major advantage when we’re done.

It’ll be the same web application.

When we push an update you’ll get it with your next refresh. When we fix a bug it’ll disappear from everyone’s install at the same time. When we send you OMG plz Upgrade to PRO now thx! notifications, everyone will see them simultaneously.

At CurdBee we’ve always prided ourselves on evolving constantly and being responsive to our users’ needs, and having a mobile version that is just a variant of our real web app makes it a lot easier to make things happen fast. We’ve followed this model all along with CurdBee and there’s no reason we’d give it up during the development of CurdBee Mobile.

Finally, we don’t like the concept of app stores. Our development process is entirely user-centred and in the end what we want to do is spend less time making sure we pass app store guidelines and spend more time developing software that users love to use.

Ultimately, all this also means that the entire process is simpler for us and will allow us to focus on what we like doing best – making CurdBee more awesome.

Openness

The web is cool because not only can you find quick fixes for work problems you’re stuck with, but you can also spend an entire morning reading Twitter and looking at Lolcats. Indeed, choice is the essence of the web and having a solid mobile gateway to CurdBee means that you have choice, and then some.

No app specific bugs or crashes, and many, many options to access your content with. Whether you use a Webkit browser or prefer Opera’s outsourced rendering, whether you’re invoicing from your iPad or logging in from your old Nokia handset, the CurdBee experience will remain (more or less) the same.

When it comes to accessing your account, we want you to have as many options as possible.

So in essence, yes we are developing applications for iOS and Android and Blackberry and Symbian and Windows Mobile. We’re just developing web applications for those platforms (it turns out we’re in good company), and we’re developing them for everyone. We are a web app, we’re going to be a mobile web app soon and yes, we’re pretty excited.

What CurdBee Mobile will look like on your friendly neighbourhood iPhone.

Of course, with our API, we’re sure that there will soon be platform specific solutions that turn up, and as always, we will always help and encourage users who want to get more out of CurdBee. As for us though, it’s the wonderful, wonderful web all the way. Stay tuned for more CurdBee Mobile news in the weeks ahead. Until then, tweet, mail or leave a comment below and let us know what you think!

As the modern web trends go, jQuery has become the front runner in bringing the client side Javascript to a common platform. But will it be able to bring the same level of success when it comes to mobile where there’s a gaping gap for a common platform ? As a bunch of developers interested in mobile apps we certainly do hope so.

jQuery mobile framework takes the “write less, do more” mantra to the next level: Instead of writing unique apps for each mobile device or OS, the jQuery mobile framework will allow you to design a single highly branded and customized web application that will work on all popular smartphone and tablet platforms.

http://jquerymobile.com/2010/08/announcing-the-jquery-mobile-project

One of the major aspects of HTML5 is its potential to replace native mobile apps and bridging barriers between various mobile platforms. This could very well be developed into the ultimate portable technology for mobile devices and provide the developer with more time for better implementation rather than worrying about bridging cross platforms. Sencha Touch – the first HTML5 mobile framework is an exciting step in this direction.

Here are some of the more impressive features of the framework.

• HTML5 Geolocation
• Sench Touch icon set
• JSONP Proxy
• YQL Data Proxy
• Momentum scrolling
• Scroll touch event
• Pop-up Overlays
• Mobile form elements
• CSS3 Gradients
• CSS3 Transitions
• Multi-Card Layout
• Tab Panel Component
• Scrollable list view
• Swappable headers

Web has moved from PC to mobile. So now the question comes…does your site work in all mobile platforms ? Here are some tools that can help you there.

As the number of people using mobile devices increases, so too does the pressure to ensure that our websites look good and are legible on a mobile device. The ideal, and unrealistic situation, would be to test on real handsets, but obviously this would be impossible for most designers. Fortunately, there are number of tools available online, allowing you to put your site through its mobile paces.

Six Tools For Testing Designs On Mobile Devices

Bitstream has entered the mobile browser market with Bolt browser which is currently
in closed beta. They say its super efficient and lightning fast compared
to its competition.