MoSync Blog

Today is a good day at MoSync we got the news that we came all the way to the final at Mobile Premier Awards in Barcelona February 15, 2010!

An international jury of the most recognized mobile industry experts has given us the opportunity to pitch MoSync at the Petit Palau of Palau de la Musica in  Barcelona.

Is there a better way to start of a blog post then using a title which is completely out of context? Probably, but this time it is not entirely out of context. Because the MoSync team are a union of evil geniuses all working together to improve the mobile world. Or something along that line...

So more interestingly, what have we been up to? On my own part, there isn't much new happening other then trying to stabilize the Moblin runtime during the next couple of weeks.

For the time being, every one at Mobile Sorcery is hard at work. We're getting closer and closer to the stable release which is scheduled for the middle of February and have a feature freeze at the end of this week. So I'd thought I' take a break from development and write more in depth about how MoSync really works.

As you might know (or not know), MoSync has had Moblin v2 support for a while now. Unfortunately, I have been the only one that had access to it. But I am glad to announce that the next stable release which is to be released quite soon, is going to have support for Moblin v2 devices. The reason that it hadn't been released earlier was that I did not have a good way of creating Moblin packages (deb and rpm) on windows and my thought was that there has to be a simpler way to creating Linux packages on windows then writing code for it yourself.

Let me begin with introducing myself, my name is Ali Mosavian, I am Software Engineer at Mobile Sorcery and head of Linux platforms. I've been into software development seriously for around 11 years now and done pretty much everything in this field. I started out in QBasic and learnt to program by using the "online" (as in, in-editor) help. That was a wonderful language/tool, but the problem was that you couldn't actually create compiled executables. So when I discovered QuickBasic 4.5, which could actually compile code, all my programming problems were solved, or so I thought.

After our previous blog post about programming being about having fun and us encouraging a new generation of mobile app enthusiasts..we decided to walk the talk. I am proud to unveil the MoSync Code Challenge 2010. This competition is open to all students of tertiary institutions all over the world.
All you need to do is download the latest release of MoSync and then translate your idea into an application.

Recently I was asked to take part in a survey. It was a collection of questions designed to delve into my deepest thoughts and extract the hidden meaning out of my answers; the fact that I just go on clicking randomly at options seems not to discourage them from sending these surveys to chumps like me.
But then again, even though my answers were always random, I did read the questions. Why you might ask? Dunno I would answer...so don't ask.

MoSync is a tool to fight the unwanted effects of fragmentation. A problem that in the long term and short term tends to cripple the mobile industry as a whole. The whole world (or at least everyone wearing Star Trek t-shirts) were immensely happy when Android phones hit markets around the world.

The MoSync dream is to have all possible functionalities on nearly all makes of phones. We are inching closer and closer to that goal and would love to have you as partners in our efforts. A lot of times, people are not sure if their phone is supported on MoSync or not. Best thing to do is to download the product and run our examples on your phone. Its a cinch and if you need some guidance we have some guiding screencasts to give you the initial nudge.

One of the best ways to communicate your feature requests and bug reports in a succinct manner is our Issue Tracker. The Issue Tracker is hosted by Google and is available at http://code.google.com/p/mosync/issues/. It lets you keep track of the bugs you have reported and their status. Labeling of the issue helps everyone view the state and nature of the issue.