Fring - ReadWriteWeb http://www.readwriteweb.com/feeds/tag/Fring en Copyright 2009 Richard MacManus readwriteweb@gmail.com Sun, 22 Nov 2009 12:00:55 -0800 http://www.sixapart.com/movabletype/?v=4.23-en http://blogs.law.harvard.edu/tech/rss Fring API Could Shake Up the Mobile Web Popular mobile IM and VOIP service Fring just launched an Application Programming Interface that could bring some awesome new applications to mobile phones around the world. The new API offers the Fring mobile interface, IM, presence indication, file transfer and other features to developers seeking to build apps in standard server-side languages. Fring ties in to users' Google Talk, MSN Messenger, ICQ and Skype IM accounts.

While the iPhone App Store will open some day soon, will be available around the world and will be usable on more affordable handsets than is the case today - Fring may still be more globally accessible than iPhone apps will be.

]]>Sponsor

]]> At launch the API is only available for Symbian S60 9.2 phones and there are no working examples of apps yet. The platform should expand and a catalog of applications open by the end of July.

What would you like to see tied into Fring? I'd love to see some FriendFeed integration, perhaps Qik and I imagine interesting things could be done with VOIP and Yelp and Fring presence and Fireeagle location tracking. How about a notification when I'm near a contact's physical location and they are available online for IM contact? That would be great.

The company is well funded, has an app for the jailbroken iPhone and reports that it's seeing more than 100k new downloads every month around the world. Here at RWW many of us are happy Fring users and we're excited to see what the developer community can add to our IM, VOIP and file transferring mobile experience. Presence data, knowing when contacts are online and off, adds a particular exciting dimension to any application - mobile apps leveraging presence could prove wildly useful.

]]>Discuss]]>
http://www.readwriteweb.com/archives/fring_api_could_shake_up_the_m.php http://www.readwriteweb.com/archives/fring_api_could_shake_up_the_m.php Mobile Services Wed, 18 Jun 2008 09:33:21 -0800 Marshall Kirkpatrick
Plan B for Microsoft: Split up the Advertising Atom Since Microsoft made its $44 billion offer for Yahoo! (so far rejected), many industry veterans, including Fred Wilson and Paul Kedrosky, have proposed ideas for Yahoo! to increase profitability, avoid a take over by Microsoft (which could potentially damage M&A activities) and stay independent (though without search, I’d call it semi-independent). In this article, let’s take a look at the other side of the coin and discuss a scenario which would give Microsoft the competition power it needs without Yahoo!

]]>Sponsor

]]> Split Up the Atom

While Microsoft’s revenues are dispersed into many areas such as home software, enterprise software, entertainment, and Internet advertising, Google’s revenues currently depend solely on online advertising. While this may sound like a weakness, Google is currently well ahead of the competition and the barriers to entry in online ads are pretty high. Microsoft knows that, otherwise they wouldn’t be so ambitious about acquiring Yahoo!

But what Microsoft can do here is to change the rules of the online advertising game by making it more open in general and less profitable for Google. There have been many companies who have claimed to make advertising more open; OpenAds and RightMedia (which is now owned by Yahoo!) are just a couple of them. But what these companies actually did was make the advertising process more transparent. Advertising is still under the control of networks which manage literally everything; publishers, advertisers, parameters, matching algorithms, etc.

However if one can split up this "network atom" and divide it into more efficient parts, things will be very different. See the graph below:

In an open advertising model, the inventory silo, placement silo, and parameter silo are controlled by many different organizations, which can interact with each other and create advertising mashups. Today Google provides these silos under the following services:

  • Inventory Silo: AdWords
  • Placement Silo: AdSense
  • Parameter Silo: PageRank, Google Analytics, Gmail, FeedBurner etc

The most crucial part of the advertising network is the inventory silo. Therefore, in order to make the open advertising model a reality, a company (presumably Microsoft) would have to jumpstart things by opening up its inventory silo - so that others could use that inventory to create new applications for placement, parameters, etc. What would happen is:

  1. Companies would give away parameters that can be used with the open inventory. In return, they generate revenue when their parameters are used to place ads.
  2. Publishers would no longer be stuck with "contextually relevant" ads, but could instead use any of these parameters or mash them up for optimal results on their pages.
  3. New 3rd party companies would emerge and they would make the whole process easier and more efficient for everyone involved.

The graph below summarizes the ecosystem I’ve just described:

With this model, a web page that consists solely of a Flash game is not stuck with Google’s "contextually relevant" option. It can mash up a bunch of parameters, or get help from 3rd parties and choose the best option for itself.

As shown above, this creates a whole new economy for parameter providers. It also opens new doors for 3rd parties for matching inventory with providers, mashing them up, analyzing and finding the best solutions for advertisers and publishers. It would also enable advertisers to make bids by filling out some XML files and allow the best ad to be displayed on particular page in the best way for a particular visitor.

Gain for Everyone

This model would not only eliminate the dominance of a single network and create a whole new economy for a lot of players, but also it could prevent a possible bust in the Internet industry.

Today’s online advertising is far too linear. Whoever clicks gives the same amount of money to the publisher and the network. That is, under the current model, the click of a person with limited purchase power is worth the same as a click from Bill Gates.

But this unfair model is not sustainable. Because what it does is to shift money from real production to vaporware. The economy can only get better if clicks on ads produce real results. And that can only be established in an open model in which everyone participates, and all parameters are run in a fully competitive and flexible environment.

Conclusion

Yahoo! is too risky for Microsoft because of the size of the deal and possible inefficiencies. So my advice to Microsoft is to let Yahoo! remain as the online media mogul. Let Google be the search giant. Instead, focus on shaking up the advertising industry by pushing it toward a democratized structure, make it work for everyone, and weaken Google's business model before it takes a bite from your Office and Windows revenues.

]]>Discuss]]>
http://www.readwriteweb.com/archives/plan_b_for_microsoft_split_up_the_advertising_atom.php http://www.readwriteweb.com/archives/plan_b_for_microsoft_split_up_the_advertising_atom.php Yahoo Wed, 13 Feb 2008 13:44:06 -0800 Emre Sokullu
37Signals' Backpack Getting Major Upgrade - Losing Focus? This week, 37Signals started to preview the upcoming update to their Backpack service, which received its last major update in July. Though most of the new features seem very useful, they also seem to transform the app from a simple organizational tool into something else entirely. We can't help but wonder, considering the company wrote the book on keeping things simple in software development, has 37Signals lost focus with Backpack?

]]>Sponsor

]]> First, the updates. Monday, 37Signals CEO Jason Fried posted a preview of the new Backpack multiuser feature on the company's popular blog. Users have always been allowed to share Backpack pages and update them collaboratively -- a helpful feature that I have personally used to do things like manage a closed alpha test of a web app. The new multiuser feature takes that collaborative ability a step further by letting people create and link Backpage pages from a single common area.

Then yesterday, Fried announced two more new Backpack features: messages and newsroom. Messages is just what it sounds like, a message board where users of the same Backpack project can talk to one another. While newsroom is an activity feed for the Backpack. For any 37Signals fan these features should sound familiar because they already exist in one of the company's other popular applications, Basecamp. Basecamp is a great groupware tool that we rely on daily to manage our activities here at ReadWriteWeb. Backpack is starting to feeling a lot like Basecamp in a different skin.

With the addition of messages and an activity feed, both apps now sport more or less the exact same feature set. Both have lists, messages, files, and writeboards. The main difference is in the way those things are displayed and how much control users have over them. While Basecamp breaks everything out into separate pieces, Backpack combines them all on a single page in any configuration you want. Both approaches have their merits, but is it necessary that they exist as separate apps?

The implications of the upcoming changes haven't been lost on users. "Cool. So Backpack is the new Basecamp with a better calendar," wrote user Jim on the 37Signals blog. "Does anyone else now feel like Backpack will have too much," chimed in Tim. "With the announcement of these new features (which are great), the difference b/w Basecamp & Backpack is starting to blur."

When others echoed the sentiment, Fried responded. "Basecamp is your project management tool, Backpack is your company intranet," he wrote. "Basecamp and Backpack are entirely different products for different purposes. We use both for very different things."

But while Basecamp and Backpack still have some major differences when it comes to things like permissions handling, which drastically effects the use cases for each, they do now share most of the same features. That brings me back to the question about whether 37Signals has lost focus with the app.

When I saw Jason Fried speak at the BIF-3 Collaborative Innovation Summit last fall, Fried was asked by the Wall Street Journal's Walt Mossberg, how do you avoid feature creep? According to Fried, the key is the ability and willingness to say no. "You have to be a hard ass," he told Mossberg. So with Backpack going from a simple, single person organizational tool to what Fried now describes as a "company intranet," has 37Signals lost focus and succumbed to feature creep? Are they not eating their own dogfood, so to speak?

The answer is a firm maybe. When talking about feature selection in their popular book about their software development methods Getting Real, the company writes that when building a web application you should start with just the single core feature. Say "no" to all the others. But that doesn't mean to you always have to say no to new features. "Start off with a lean, smart app and let it gain traction," they write. "Then you can start to add to the solid foundation you've built."

That is more or less what they've done with Backpack. Started lean, let is get traction, then expanded it to where they thought it should go. But as an application Backpack has clearly evolved beyond a simple organizational tool to something that is starting to resemble their Basecamp application (which we, incidentally, already basically use as our intranet). Whether they've fallen prey to feature creep will really be measured by the response of their users. If people remain confused over the difference between Backpack and its cousin Basecamp, then the answer is yes, somewhere they stopped following their own advice and said "yes" to one too many feature that was better suited to one of their other applications. But if people embrace both apps as complimentary offerings, as Fried clearly hopes they will, then they've made the right decisions.

37Signals offers a range of applications, from simple, single-function apps like Ta-Da Lists (to-do lists), Writeboard (collaborative word processor), and Campfire (group chat) to more complicated apps like Basecamp (project management) and Highrise (group contact manager).

In the past, 37Signals has often integrated its simpler products into its more complicated offerings. Basecamp has Campfire chats, Writeboard shared writing spaces, and to-do lists clearly based on Ta-Da, for example. Along with their slow shift toward full OpenID support, this points to the potential for a modular, create-your-own app system from 37Signals, where users could pick and choose which of the company's applications to install. That's completely speculation on our part, but we really hope that's the direction 37Signals is headed.

What do you think? Has 37Signals lost focus with Backpack? Or do you still see differences distinct enough between Basecamp and Backpack that you could see yourself using both? Do you wish the functionality of both applications was merged into a single app? Let us know in the comments below.

]]>Discuss]]>
http://www.readwriteweb.com/archives/37signals_backpack_losing_focus.php http://www.readwriteweb.com/archives/37signals_backpack_losing_focus.php Products Wed, 13 Feb 2008 11:56:17 -0800 Josh Catone