Mango Gets the Basics

At MIX Microsoft is giving us the scoop on the next version of Windows Phone 7, code named Mango. It really is adding some of the important features that were missing from the current release. Mango is adding support for Silverlight 4, TCP Sockets, XNA integration, and access to the Camera APIs.

 

Silverlight 4

Windows Phone 7 is current running Silverlight 3, while Microsoft is already announcing the beta for Silverlight 5. This makes it difficult to move applications between the desktop and the phone. Mango will support Silverlight 4 include implicit Styles, RichTextBox, along with all its added support for TCP Sockets, and XNA integration.

 

TCP Sockets

 Missing from the current version of Windows Phone 7 is access to the low level TCP socket APIs. While this is not critical for Web integrated applications, it does make it hard to provide real time services such as Skype. Mango will provide full access to these APIs, so expect to see support for real time VoIP and media applications.

 

XNA Integration

Currently, applications on Windows Phone 7 can support either XNA or Silverlight. This means that it is not possible to mix 3D modeling into your Silverlight based application. Mango will provide programmers with access to the XNA APIs from Silverlight allowing applications to support both 2D based controls and 3D based models.

 

Camera APIs

The only way to access the camera in the current version of Windows Phone 7 is to launch the camera application and let the user manually capture an image. This is not useful for capturing QR and Bar Codes, and video capture for Video conferencing.  Mango will provide access to the camera APIs allow the application to use the camera as an in application capture device. This will enable the important video conferencing features require by applications such as Skype.

There are many more new features in Windows Phone, but the addition of these features will bring Windows Phone 7 to parity with the capabilities currently available and expected in the current Symbian phones.

This is really good news to application developers.

 

QUI application shares GPS location via SMS/Email

Via Biskero, a new application in the OVI Store, QUI and QUI Pro. "Basically it gets your GPS location and you can share it via SMS/Email with your friend. You friend will receive a SMS/Email containing a link to a mobile site which will display a map with your locatio. The map uses OVI Maps API. If your friend has a Nokia device, he/she can start OVI Maps client to location you."

QUI and QUI Pro
allow you to share via SMS/Email your location to a friend. Use your GPS to
get your location and share it by sending an SMS. Your friend will
receive a link to a mobile web page with your location on a map"

 

The QUI application supports the following GPS enabled Nokia touch devices, including the Nokia X7:

  • Nokia C7 Astound
  • Nokia C5-03
  • Nokia C6-01
  • Nokia C7-00
  • Nokia E7-00
  • Nokia N8-00
  • Nokia X7
  • Nokia C6-00
  • Nokia 5230 Nuron
  • Nokia 5235 Ovi Music Unlimited
  • Nokia N97 mini
  • Nokia X6-00
  • Nokia 5230
  • Nokia N97
  • Nokia 5800 XpressMusic

Download QUI in Ovi Store now.

 

QUI in OVI Maps

 

 

 Download QUI and QUI Pro !!

Alessandro

QUI application shares GPS location via SMS/Email

Via Biskero, a new application in the OVI Store, QUI and QUI Pro. "Basically it gets your GPS location and you can share it via SMS/Email with your friend. You friend will receive a SMS/Email containing a link to a mobile site which will display a map with your locatio. The map uses OVI Maps API. If your friend has a Nokia device, he/she can start OVI Maps client to location you."

QUI and QUI Pro
allow you to share via SMS/Email your location to a friend. Use your GPS to
get your location and share it by sending an SMS. Your friend will
receive a link to a mobile web page with your location on a map"

 

The QUI application supports the following GPS enabled Nokia touch devices, including the Nokia X7:

  • Nokia C7 Astound
  • Nokia C5-03
  • Nokia C6-01
  • Nokia C7-00
  • Nokia E7-00
  • Nokia N8-00
  • Nokia X7
  • Nokia C6-00
  • Nokia 5230 Nuron
  • Nokia 5235 Ovi Music Unlimited
  • Nokia N97 mini
  • Nokia X6-00
  • Nokia 5230
  • Nokia N97
  • Nokia 5800 XpressMusic

Download QUI in Ovi Store now.

 

QUI in OVI Maps

 

 

 Download QUI and QUI Pro !!

Alessandro

MIXing it up

With Nokia’s new strategy in full force, I decided to buy a Windows Phone and attend the MIX conference in Las Vegas. This is a great meeting place for Nokia and Microsoft developers to come together and learn about the developer tools.

Programming the Window’s phone is not a big leap from using Qt and QML. The programming model for Windows phone uses a Declarative XML Language called XAML that uses tags and attributes in the way the QML defines elements and properties. XAML is part of Silverlight and is available on both the phone and desktop. XAML also includes the idea of binding between tags and binding C# classes to XAML tags. XAML includes all of the concepts of QML including models, positioners, views, and delegates, but with different names. For instance, a QML delegate maps into a XAML templated item. Models and views are implemented in XAML and C# using the Silverlight MVVM (model – vew – viewmodel) framework. This is roughly equivalent of using delegate components with different views.

The tools for Windows phone developers include Visual Studio and Expression Blender. Many Qt developers have been using Visual Studio for Qt development so many of us understand the power and flexibility of this tool. Expression Blender is similar to QML Designer and provides the tools to style, manage, and animate declarative elements specified with XAML tags.

The main differences between QML and XAML is that QML includes javascript as an expression language, whereas XAML interfaces with C# to implement expressions. This means that there is usually a one to one mapping between a C# class and a element declared as a tag in XAML.

I plan to provide more indepth information on Windows Phone development in this blog. In particular, I want to focus on developing Apps for both QML and Windows Phone. This will help developers maximize their coverage on both Nokia Symbian and Windows Phones.

A good place to get started with Windows Phone development is the App Hub Getting Started Page .

 

eSign for Nokia S60 5th & Symbian 3 handsets

In only 3 of the 190 countries supported by The Nokia Ovi Store, there are more than 20 million people living with a hearing disability.
South Africa has more than 1.5million deaf citizens, in the USA the number is closer to 9million and in the UK it’s around 8.9million.
With such a high number of deaf people globaly surely there should be an easy way for regular hearing folks to learn even the most basic of Sign Language to help narrow the gap in communication between the hearing and the deaf.
In June 2010 AppCRAFT launched a series of free HandSign applications aimed at helping this community learn the Sign Language Alphabet. Since going live over 17000+ friends have tuned in to learn Sign Language from home.  With this in mind,
I am happy to announce that a new low cost mobile tool is now available to help both hearing and non hearing Nokia users learn the Sign Language Alphabet. Introduing eSign
eSign is built on top of our award winning eLiteracy framework and contains fun flash card style educational games for the whole family. The aim of this new guide is to make learning the sign language alphabet more fun and interactive. As with all languages, starting with the ABC’s is best. We hope to also soon release more advanced features, teaching words, and sentences etc.
eSign is now available exclusivly in the Nokia Ovi Store and is free to download for a limited time period. Get it while it’s FREE!
Currently available in
Note:
We are still ironing out a few small audio issues on Symbian 3 devices and these will be addressed in the next version going live in a few days time. Since AppCRAFT is still a very small startup, We thought best to share the app with the community even before fixing all the small bugs, this way we can get user feedback and see how best to adapt the guide in future versions. Your feedback is much appriciated and will go along way in making sure we deliver better and better products.

Startup Lessons from Africa

“I received some unfortunate news that my new startup would not be part of the latest i/o ventures class. We made it to the very last round but did not get over the hump. Given over 350 companies applied, making it to the last round is something to be proud of.” @

Like @Geoffclapp quoted above, I also received the unfortunate news this week that even though AppCRAFT had made it to the final round of the i.o ventures VC program, we would not be part of the final 5 companies who would travel to San Francisco to be mentored by i/o ventures.

You can imagine my disappointment at getting the news. My heart sank into my shoe’s as questions raced through my mind. What happened? How could we make it so far and then fail during the final round of in depth due diligence?

“Due diligence” is a term used for a number of concepts involving either an investigation of a business or person prior to signing a contract, or an act with a certain standard of care. It can be a legal obligation, but the term will more commonly apply to voluntary investigations. A common example of due diligence in various industries is the process through which a potential acquirer evaluates a target company or its assets for acquisition.” Wikipedia

Little did I know but AppCRAFT was not the only firm under “investigation”.

To quell my thought’s I dropped one of the i/o venture partners an email to find out where we had gone wrong. His responce…  ”You came across strong technically and with solid and relevant experience.” … “The biggest thing is that my partners weren’t super excited about the Nokia platform.”… “even though Nokia is the largest platform it is dying on the vine and its marketplace is know to be weak.”

So in other words, Nokia failed the last round of in depth due diligence and I failed because AppCRAFT develops apps for the Nokia platform. Did I miss something?

Nokia is the largest mobile platform on earth: 955 Million handsets in 190 countries, currently clocking over 4 million downloads a day and growing daily.  “Weak marketplace” and dying on the vine”? wow ok, Obviously we do not have the same view of Nokia! What am I missing?

Here’s what makes this news so disappointing.

AppCRAFT is an award winning mobile development startup based in South Africa. In less than 18 months we have risen from the African soil, taking top development awards both locally and internationally. We have proven that we have what it takes to deliver world class award winning content, within tight deadlines. With an early investment of only R2000 we successfully brought our applications to market during a serious global economic recession and managed to keep our heads above water for 18months.

Given the correct mentoring and finances, we could easily port these and other award winning idea’s to many other platforms and this is exactly why we were looking to secure VC and mentoring.

The fact that we were dropped from a VC round because “my partners weren’t super excited about the Nokia platform”, is hard to swallow to say the least.  Either we, being AppCRAFT are “strong technically” or we are not, either we have “solid and relevant experience” or we do not.

No matter how hard it is to accept this disappointing news though, we fully respect the decision i/o ventures made, I mean hey it’s their time and money, they need to make sure they get the best ROI. I also need to echo the words of @geoffclapp “I honestly can’t say a bad thing about the i/o venture process or Paul Bragiel” and now we move on to new pastures.

So moving forward, how can we learn from this? What lessons did we pick up and how can we improve?

LESSONS:

1. Proving that you have what it takes by winning multiple awards means nothing. You can’t win them all!
2. Developing for only one platform is a dying game, go big or go home.
3. No matter how large you are, there will always be people who view you as dying and weak.
4. If you are a small time startup, don’t waste time looking for VC, focus on what you do best.
5. Share your experiences so others can learn from your mistakes.

Remember that no matter how hard you try, there will always be reasons to fail. All you need to remember is that no matter how many times you fail, once you have fallen get back up, dust yourself off and try again.

HOW CAN WE IMPROVE?

AppCRAFT will in future continue to develop award winning mobile applications. We will focus on what we do best and will continue to find innovative ways to stay ahead of the crowd.

A huge thank you goes out to i/o ventures for the chance we were given to take part in this VC round and for opening our eye’s in many ways.