Early on in the project we decided to go for “mobile first” approach. We firmly believe that the easiest and right way to do it is through a Web App.

Recently (~1 year) many mobile web dev platforms have emerged. jQueryMobile, Lungojs, Sencha Touch, jqTouch, iUI are the most prominent ones. We tried them all when we first started and all of them are “ok”. But we cannot settle for that We eliminated some of them due to visual and technology concerns and ended up selecting the fastest (back then) and most supported with a large community (even in the alpha/beta stages): jQueryMobile

The structure of it simply fantastic. You can create UI elements and pages really fast. We decided to build a complete UI with it and let JS with API calls handle all the data transactions with our back-end (built on Django/Python — will follow up with a different post on that).

After 2 months of part-time development we finally had something on test more widely on different platforms. Basic pages with basic functionality in jQueryMobile communicating with basic API calls with the back-end. All the testing while developing in early stages happened on Android 3.1 (Galaxy Tab), and we have to admit that it felt kinda slow (both in Firefox Mobile and in Native Browser). Transitions are jumpy and control elements not as snappy as you would expect on a native app. Then one day we got an iPad 2 in our hands and tested it also there. Huge difference. It is like jQueryMobile is made for this thing! Smooth transitions, responsive controls nice loadings This is kinda weird as on jqm website about platform support, both platforms are rated A+. We are going to follow up on this with jQueryMobile team to figure out what is happening. In the meantime, disabling transitions and effects seems like a viable solution to get something close-to-smooth in Android.

We would love to hear any feedback about Mobile Web Frameworks (jQueryMobile in specific) and speed on those platforms. It is understood that we are living on edge here (always on nightly builds on all frameworks), but hey it would not be fun if it wasn’t for bleeding edge!

/we back to testing

Giorgos & Pierros

cc-by-sa photo by Brian Lai

Exciting times in Verese team

Last month was super productive, heads down, hard coding month for Verese.

First and foremost Verese had been accepted in WebFWD the new Innovation Accelerator from Mozilla! This is huge for our project, as it gives us the opportunity to work closely with the best Web programers and engineers, passionate about the Open Web and exchange valuable ideas with other cool projects that are already part of WebFWD. For more info about the program check out WebFWD website. We will be posting our experiences within the program, as we go.

On development side, we deployed our new Virtual Machine for Development purposes, kindly sponsored by MediaTemple (thanks!) and streamlined the deployment process. Also we are deep into mocking up UI for Verese (after the initial testing one), so expect updates soon on this too.

In the meanwhile, make sure to follow us at @vereseproject and our mailing list for latest news and announcements of the project.

ps. We have new Universal Subtitles enabled video! Help us translate it!

Here is a video explanation of the basic functionality of Verese. Enjoy!

As the web keeps covering more and more aspects of our daily life, it has become crucial for the open web initiatives to step up and be major players in forming this new scene. Many new web standards originate from community efforts and that’s what has been keeping the web growth healthy so far.

But, there are still things to be done. Financial transactions seems to be one of the few things open web initiatives has not touched yet. The situation in the web on that front is not good. Proprietary platforms and protocols are ruling the place and users have no authority to trust. Data handling is done in secrecy and centralized services are the rule of thumb. Several unsuccessful attempts have been made to counteract (Bitcoin, Ripple Project etc) but all of them do not take advantage of the open web technologies and are failing to address all points (Open Source, Open Web, Decentralized, Federated, Community cultivated).

Verese
Verese project is willing to built community around open web financial transactions. In order to do that we need a viable product. Verese.net is going to be deployed as a micro-payment micro-credit system and will be our primary focus. Standardization of financial transactions on the web will be the next step after verese. In parallel we are going to examine all possibilities for decentralized architectures.

Why micro-* ?
The vast majority of our day to day transactions are done on the micro level. You give small amounts of money here and there, within your trust circle. Addressing micro-* is the ideal test for verese, as it force us to be scalable, easily understood and personalized. Challenge accepted!

Next Steps
Verese is under active deployment. Join our mailing list and let’s start forming the future of financial transactions on the web!

More updates to come.. so stay tuned!

Giorgos & Pierros