07/09/2010

IMify your self-services apps!

Over at The Next Web I’ve published an article about Voxeo’s IMified acquisition. Go, check it out and start building outstanding self-services solutions.

Ihren XING-Kontakten zeigen

@24z

In an attempt to keep meta information as short as possible and leave more room for content, I’ve renamed my Twitter account to 24z. You don’t have to do anything. If you followed me @ralfrottmann before, you keep on following @24z automatically. My “old” account is still there so that links in some older posts don’t break.

Thanks for being patient with me during my “twitter-account-merger-mania”!

Ihren XING-Kontakten zeigen

5 Tips on Getting Started with the Thesis WordPress Theme

Having tried many other WordPress themes for 24100.net before, I absolutely fell in love with Thesis. Thesis is a professional theme created by DIY Themes which comes with built-in search engine optimization (no additional plug-ins needed), a unique approach for customization and fantastic customer support.

Prior to switching to Thesis I’ve been using a design provided by WooThemes. It also worked like a charm but adding social media features without breaking the advanced theme design ultimately got more and more difficult. So I’ve decided to give Thesis a try. And I fell in love.

Thesis is not free. But it’s well worth your money.

This article covers tips from my ongoing journey of customizing Thesis the way I want.

[Read more...]

Ihren XING-Kontakten zeigen

Nokia’s Ovi Store launched (sort of)

Today Nokia has launched it’s response to Apple’s App Store, an event which has been eagerly expected by the industry. I’ve covered my first hand experience with the Ovi Store and more specifically how it relates to Apple’s offering over at The Next Web. Though I’ve got to admit being a bit biased, given that I’m an obvious Apple fanboy, I tried to comment from a pure end user’s and developer’s perspective.

Enjoy the article and feel free to comment at any time.

Ihren XING-Kontakten zeigen

No additional Twitter meta tags, please

Over at The Next Web I’ve published an article about upcoming ideas to introduce more meta characters to annotate tweets. Check it out, you might like it, or not. The discussion is – as always – controversial and every feedback is appreciated!

Ihren XING-Kontakten zeigen

Changing 24100.NET’s Design

We are currently working on the design of 24100.NET in order to streamline it for faster browsing. If you’re not reading this with your feed reader you might see some quirks while 24100.NET is undergoing maintenance. Sorry!

I’ve chosen to try an entirely new WordPress Theme as it got more and more difficult with the previous theme to include Web 2.0/Social Media features. Having conducted quite some extensive research, I found the Theses theme (created by DIYTHEMES) a wonderful alternative to every other WordPress theme I’ve ever used.

The site will also get a new logo, my designer is still working on it!

While you’re here you might want to try out the new Google Friend Connect integration. Find the “Join this site” link in the Community section to the left. You can log in via your GMail account and start submitting comments and participate in future community services.

I’m planning to have the redesigned finished this next Sunday. Your comments are more than appreciated!

Ihren XING-Kontakten zeigen

PhoneGap and iPhone SDK 3.0 (No launchable executable present at path)

Just a quick note on getting a “No launchable executable present at path” error when trying to build and run the PhoneGap Demo project for the iPhone Simulator.

(Before you read on, why don’t you follow me at twitter?!)

Today one of our devs grabbed a fresh and clean copy of PhoneGap from GitHub, changed the Bundle Identifier accordingly, switched to the iPhone Simulator – 2.2.1 | Debug configuration and tried to Build & Go. This yielded a “No launchable executable present at path” for an executable named “Glass.app”. A quick search over at the PhoneGap Google Groups indicated that quite a few folks ran into this or similar issues.

I don’t exactly understand why the checked-in PhoneGap projects do not get at least some sort of quality assurance but maybe we’ve got to accept rocky paths if we opt for free lunch. My Google searches on this issue indicated that quite some devs turn away from PhoneGap because failing at “Getting Started” is probably the most frustrating experience.

I was able to resolve the issue by executing the following steps:

  • Get a clean version of PhoneGap by running git clone git://github.com/sintaxi/phonegap.git in a Terminal session.
  • Open PhoneGap.xcodeproj with Xcode.
  • Open Info.plist and replace the com.sintaxi.phonegap Bundle Identifier with your own. Ours is com.grandcentrix.phonegap.
  • Right-click the top most node named PhoneGap and select Get Info.
  • Make sure that Configuration says All Configurations and Show says All Settings.
  • Adjust Code Signing Identity, Any iPhone OS Device and Device – iPhone OS 2.1. I switched these from <Multiple values> to iPhone Developer.
  • On the Build tab in Search in Build Settings type Product Name. In my project the product name was empty. Double click the empty value cell and enter PhoneGap. Close the Project Settings.
  • Expand the node named Targets, right-click PhoneGap and select Get Info.
  • On the Build tab again search for Product Name and enter PhoneGap. Mine had <Multiple values> here, too.
  • From the Build menu select Clean All Targets.
  • Make sure iPhone Simulator 2.2.1 is the active platform and Debug is the active build.
  • Select Build and Go.

This worked for me. The PhoneGap application runs fine in the 2.2.1 Simulator and crashes shortly after launch if I build for the 3.0 Beta 5 Simulator (which is ok given the beta nature of Apple’s 3.0 SDK).

I have not yet tested to deploy the device.

Ihren XING-Kontakten zeigen

Vodafone plans the Ueber-App-Store

(For latest thoughts follow me on twitter!)

Today Vodafone announced plans to “Redefine the Mobile Internet Experience”. The essence of the announcement is in the first three paragraphs:

Vodafone is to stimulate a new generation of mobile internet applications by providing internet service developers with a single point of access to Vodafone’s global customer base.

Developers will only need to create internet applications once in order to reach millions of Vodafone customers on any device and will be able to charge for it directly through Vodafone’s billing system. This will provide internet content partners, such as the media or game developers, with a cost-efficient and effective micro-payments system to reach all customers on mobile devices.

Vodafone will also provide partners and developers with customer controlled access to other network capabilities, such as location awareness, enabling them to create even more innovative mobile internet services and applications.

Wow, these are potentially big news for all developers of mobile services and applications.

Since Apple’s App Store has absorbed almost 100% of the press’ attention for mobile distribution platforms, it has clearly only been a question of time until others would follow. It’s only a few days to the Grand Opening of Nokia’s Ovi Store, RIM started the BlackBerry App World and Android folks got their Android Market.

None of these device vendor driven initiatives have yet established the global reach and seamlessness that Apple is so well known for, but that’s also only a matter of time, too.

The Vodafone announcement is remarkably different because for the first time a carrier announces to open up its holy grail to – literally – everyone: The Billing Engine.

betavine, Vodafone’s “open community for mobile application developers” has been around for quite a while but did not receive too much attention from either devs nor the press. And the fact that nobody has responded to a betavine team member’s post regarding today’s announcement as of this writing, might be an indicator for a not-so-hot community. In comparison, Apple’s App Store birth announcement yielded thousands of comments just seconds after its publication.

Given the potential disruptive nature of Vodafone’s initiative, lets briefly look into some key aspects of mobile service delivery and specifically what the announcement states with respect to each:

The Client Platform

Application developers are controversially discussing whether native applications (read “SDK”) or leveraging web technologies (read “HTML 5″, hopefully) or hybrids are the best way to build for mobiles. As of today there seems to be no clear answer and we might have to wait until HTML 5 transitions into a real standard and becomes widely supported across devices.

The announcement says: 

Vodafone is to stimulate a new generation of mobile internet applications by providing internet service developers with a single point of access to Vodafone’s global customer base. [emphases added]

So the platform targets internet service developers. A Google search on this term returns the Vodafone announcement so we might be fair to assume that “internet service developers” is either meant literally or deliberately non-specific. I assume the latter. It is pretty obvious that Vodafone is not going down the route to build a multi-devices SDK or anything else which would require strong device vendor co-operation.

Presumably services running on Vodafone’s “redefined mobile internet experience platform” will leverage standard web technologies. This is currently very likely the only path to go if supporting hundreds of different devices, including ones that you don’t even control, is part of your strategy.

It does, however, not solve the problem of device diversification entirely. One of the key drivers for Apple’s mass market success with respect to delivering mobile applications is the optimized, enhanced and device specific user experience iPhone applications deliver.

One of the paragraphs to the end

Vodafone is also exploring a range of other ways to expose its network enablers to the broadest possible audience.

is again deliberately unspecific which might mean, that they have not yet decided on a strategy for this (key) area.

If Vodafone’s new platform is going to promote a one-size-fits-all approach, I doubt whether it’ll break out of a geeky user base.

Discoverability

As with the Web 1.0 the ability for an application to be found by customers and users is a key aspect for service providers. In the mobile space discoverability is required on two ends: First, users need to find a service and be able to “get it onto their phones”. Second, once they’ve successfully downloaded or bookmarked a service, they need to be able to quickly access it. (I remember some older Nokia smart phones where I had to traverse down six levels of folders until I could start a downloaded JAVA app.)

Vodafone’s announcement does not state anything related to the problem of discoverability.

Developers will only need to create internet applications once in order to reach millions of Vodafone customers on any device [...]

“Only creating internet applications in order to reach millions of customers” sounds pretty euphemistic to me. The difficulty of application marketing is already the number one issue on the App Store and I seriously wonder how Vodafone is planning to support a developer ecosystem to reach their target audience.

Micropayment

For years making money with mobile applications has been a tough business. The absence of a seamless cross-device, cross-carrier, cross-country micro-transaction payment has limited the options for developers to charge their customers significantly.

Apple’s announcement of supporting in-application-purchases with the upcoming new iPhone operating system is a game changer – for developers targeting the iPhone platform. And it’s a quite natural move for Apple to open up the iTunes billing engine with roughly 50 million chargeable credit cards on stock.

As ultimately making money is the driver for mobile businesses, this aspect of the Vodafone statement is extremely important:

Vodafone will enable developers to use its direct billing capabilities to permit customers to pay for services wirelessly through their existing Vodafone pre- and post-paid accounts rather than having to input sensitive credit card data into multiple application stores.

This will make Vodafone to directly compete against PayPal and all the other start-ups that are currently incorporated on an almost daily basis and try to address mobile micropayment.

It’s also worth to mention that this is the first time a carrier announces to open its direct billing capabilities to the wild. Previously subsequently charging customers was tied to let them call premium rate numbers or send premium short messages (a business with a 90% profit margin).

Letting developers tie into Vodafone’s billing engines is huge and highest priority to investigate further on my watch list.

This will provide internet content partners, such as the media or game developers, with a cost-efficient and effective micro-payments system to reach all customers on mobile devices.

Well, at least all Vodafone customers on mobile devices that will support these new type of applications.

The real news is about “Building a Relationship”

As so often with press announcements, most of the details remain foggy.

I guess that the smart folks at Vodafone have primarily decided on the overall strategy and are now facing the difficult phase of executing it correctly. (One of the unique aspects of Apple’s success it to constantly define the right strategy AND master its execution.)

The biggest news for me is that one of the problems in dealing with carriers before was building a relationship. This has been extremely difficult and was not possible for many.

Hopefully this might have changed and we will see other carriers follow.

Ultimately: Who is going to work on a cross-carrier, cross-device, cross-user-identity, cross-platform solution?

Ihren XING-Kontakten zeigen

Tumble Into Peace

Originally found here and pointed out to me by Michael Arrington via twitter, I wanted to share this with my subscribers:

Now, I do love the iPhone platform but this video is just too good to not being shared.

Ihren XING-Kontakten zeigen