Posts Tagged ‘Developer Conference’
Seesmic Launches App For Windows Phone; Rolls Out New Silverlight-Powered Desktop Client
Seesmic Launches App For Windows Phone; Rolls Out New Silverlight-Powered Desktop Client

Startup Seesmic has perfected the art of making a compelling Twitter clients on a variety of platforms. Seesmic offers a web client, an Adobe Air-powered desktop client, an Android app, a BlackBerry app, a brand friendly Twitter client and a native Windows desktop client. At developer conference MIX today, Seesmic founder Loic Le Meur is announcing a new Silverlight-powered development platform and Seesmic for the Windows Phone.
The new desktop platform from Seesmic is built based off of Silverlight, which is a refreshing change from the buggy Adobe Air platform. The design itself is similar in look and feel to the Windows client, and includes functionality for integrating your Facebook, Twitter, and Linkedin accounts. You can also personalize your background of the app. And the new platform works on both Macs and PCs.
But the most compelling feature of the new desktop platform is that it was designed with plugin features, which will now allows developers build features or integrate their services in Seesmic’s suite of Seesmic clients. One example of a plugin feature is a Bing mapping control plugin, which not only allows you to track geo-location but integrates trackable links at Bing.com
The Seesmic Desktop SDK includes an Extensibility layer as well as a set of utility classes, and the accompanying documentation. Seesmic is also launching a Twitter client app for Windows phones, similar to the BlackBerry app, that will integrated Bing maps and geo-location together.
Le Meur has told me in the past that he has invested in the Windows platform because 80 percent of Seesmic users use a PC. But with the new Silverlight-powered client, both Mac and PC users will be able to experience the client. I’m curious how the client will far against rival technology Adobe Air powered clients, which include Seesmic, and Tweetdeck. And Le Meur is wise to create an ecosystem around his applications, allowing developers to create plug-ins for Seesmic clients.
Disclaimer: Michael Arrington is an investor of Seesmic; I am not.
Facebook Firehose May Be Released at Developer Conference F8
Facebook Firehose May Be Released at Developer Conference F8
Facebook plans to announce the availability of a firehose of user data at its F8 developers conference in April, we believe based on research. Such an offering could be similar to the firehose that Twitter has shared with large partners and select small developers building the famous Twitter ecosystem of 3rd party applications around the web. A Facebook representative did not offer a denial, saying only that the company would not comment on speculation.
The huge social network was once private by default, then made controversial changes in December that pushed hundreds of millions of users toward publishing their information in public and now appears aimed to complete the about-face at its F8 developer conference by offering up public user data in a huge river that outside parties can consume, analyze and build on top of.
“Nobody thinks about how much valuable information they’re generating just by friending people and fanning pages. It’s like we’re constantly voting in a hundred different ways every day. And I’m a starry-eyed believer that we’ll be able to change the world for the better using that neglected information. It’s like an x-ray for the whole country – we can see all sorts of hidden details of who we’re friends with, where we live, what we like.” – Pete Warden, The Man Who Looked Into Facebook’s Soul
The first F8 conference saw the unveiling of the Facebook Platform, a way for app developers to build games and utilities inside of Facebook. This announcement would represent Facebook as a platform and enable far more to be built outside and on top of the social network. Privacy concerns? For sure. Genuinely world-changing potential? There’s a lot of that too.
It’s not clear exactly what would be included in this firehose, it could be a stream of low-value Fan Page promotional content, for example. The most likely thing content to be included though is user activity data published under public privacy settings. There’s far, far more of that today than there was just a few months ago.
If you’ve participated in a supermarket loyalty program, you’re familiar with the concept of opting-in to sharing data about your activities with outside parties in exchange for benefits. In that common practice, though, consumers gain shopping discounts but get nothing from the analysis of the data they emit.
In the case of the Twitter Firehose, the much sought-after full feed of public user data from across the site, users gain access to all kinds of interesting applications and insights based on analysis of their use of Twitter.
A Facebook firehose would be much bigger. We’re hearing that there will be no launch partners in the announcement, but the imagination runs wild thinking about all the mashup possibilities. We learned last week that user location data is coming to Facebook at F8, now picture all this rich data roaring like a river into the data digesting machines of a wide range of developers all over the world.
A firehose of public Facebook user activity data could function like a living, breathing global census. Cross reference that data with any other data set and we may find an ocean of insights into the human condition, around the world, for slices of people, second by second or over time.
This is something we’ve been calling on Facebook to do for some time. I’ve sat with founder Mark Zuckerberg and discussed the importance and potential of releasing aggregate user data at length.
That, though, was before last December when the privacy policy changed.
Privacy Concerns
Just because something is posted publicly on the web, Microsoft researcher danah boyd said in her opening keynote at SXSW yesterday, doesn’t mean people want it to be broadcast more generally. Making something public is not permission to publicize it.
Is the inclusion of public activity into a firehose programatically available to outside developers a case of broadcast that violates user control and thus privacy?
I don’t think it’s clear either way. In a discussion about aggregate Twitter data analysis late last year, a representative of the Electronic Frontier Foundation told me that Twitter users had no reasonable expectation that their data wouldn’t be redistributed and analyzed in bulk because Twitter was a public forum.
Facebook used to be different. It was private by default, our actions were shared only with friends and family that we gave permission to see our status messages and photos.
Then in December the company made a dramatic shift, prompting users to re-evaluate their privacy settings and making “share with everyone all over the internet” the new default for most options. Mark Zuckerberg said Facebook was only changing to reflect the way the world was changing, but we argued that was a disingenous rationalization of Facebook’s culture-changing actions driven in part by its own profit motive. We also argued that by pushing users toward being more public the company was reducing user control over data and spreading distrust about making data available online at all. That put at risk the idea of sharing your data in a way that could be analyzed.
Is there a reasonable expectation that online social networking activity set to “public” will not be redistributed in bulk to outside parties? How can a company like Facebook respect user privacy as much as possible while still achieving the incredible things that can be achieved by making aggregate user data available for analysis?
Let’s begin to discuss it.
See also: The personal blog of Cameron Marlow, Facebook’s in-house sociologist and big data guy.
Related analysis: Twitter 2.0: API Rate Change Could Lead to a World of New Apps & Features
Chewing on the Issues: Twitter Data Dump: InfoChimps Puts 1B Connections Up for Sale
The Facebook Verified App Saga Ends Tomorrow
The Facebook Verified App Saga Ends Tomorrow
For the last six months, you may have noticed that some of your favorite apps on Facebook Platform carried a special badge deeming them to be “Facebook Verified”. These apps “passed Facebook’s review for trustworthy user experiences”, and were given both greater exposure in the App Directory and less restrictive limits on the number of messages they could send to users. And tomorrow, just over six months after the program launched, Facebook is killing off Verified Apps for good.
This shouldn’t come as a surprise: Facebook announced plans to end the program in late October, and has been Emailing developers about it for weeks. But now that Verified Apps are going away, it’s a good time to look back at the long, convoluted road Facebook took to a program that was ultimately very shortlived.
The Verified Apps program has been anything but a smooth ride for developers. It was first announced at the Facebook developer conference in July 2008, with the intention of helping users identify the most trustworthy apps on the platform. In return for meeting Facebook’s guidelines, apps would be rewarded with bonuses like advertising credits and relaxed rules on how many notifications and messages they could send to users.
More concrete details about the program were revealed the following November, when Facebook opened up the program to applications. Developers were charged a $375 fee to apply, which we likened to a protection racket. But after developers paid their money, Facebook went silent about the program for half a year. That understandably led to growing developer unrest. Finally, nearly a year after it was first announced, Verified Apps made its debut in May 2009.
But Verified Apps was only supposed to be a stepping stone to the site’s true cream of the crop. The most elite class of applications was to be called “Great Apps”, and launched with iLike and Causes as inaugural members. But that was another false start. Two months after the launch of Verified Apps, Facebook revealed that it was canceling its plans for its Great Apps program and demoting current members to regular Verified Apps. Or, as Facebook put it, they were getting rolled into the same thing, so Verified Apps were getting the benefits that would have been reserved for Great Apps.

Despite these logistical hurdles, developers certainly benefited from the program. For example, CampusBuddy, a verified app we covered in September, has grown from 60,000 to over 150,000 monthly active users. CEO Michael Moradian says that the company will especially miss the “extra boosts” that applications received as part of the program because they helped virality. But while CampusBuddy would have liked to see the program continue, Moradian acknowledges that times may be changing. You can see his blog about the news here.
So why is Facebook getting rid of Verified Apps? Facebook gives the following explanation:
We are standardizing the idea of verification to apply to all of the applications on Facebook Platform. We are evolving the program to improve the overall user experience and ensure that applications on Facebook Platform meet verification standards. We intend to make sure that the experience that our users have on Platform is of the same quality as they experience elsewhere on Facebook, which is something that we are constantly asked for by developers.
In other words, Facebook wants every app to be trustworthy. To do that, they’re planning “to expand [the] team responsible for policy enforcement on Platform so that they can support the upholding of the principles we’ve introduced as part of our roadmap.” It’s not really clear why they wouldn’t have done this from the start.
The timing is certainly suspect. Some of the companies we called out in our ScamVille posts for using scammy offers, like Zynga, have some of their apps Verified. Granted, Facebook announced the decision to end Verified Apps a few days before we first broke the Scamville story, but they’ve been aware of the infringing games, offers, and ads for a long time. In effect, they’ve been stamping their seal of approval on games using tactics that are the target of a class-action lawsuit.
Crunch Network: CrunchBase the free database of technology companies, people, and investors
Seesmic Goes Native: Launches Windows-Only Twitter Client
Seesmic Goes Native: Launches Windows-Only Twitter Client
At Microsoft’s Professional Developer Conference, Seesmic’s founder and CEO Loic Le Meur just announced that the company will release a native Windows version of its popular Twitter client later today. Seesmic developed this client on top of .NET. As Le Meur told us yesterday, the new client will be faster and use significantly less memory than the current AIR client. In addition, Seesmic will now also feature a Firefox-like plugin infrastructure that will allow developers to extend the application through a new, built-in API.
As usual, Seesmic will first make this new Seesmic for Windows client available to members of its Team Seesmic beta test community. Signing up for Team Seesmic is easy and you will immediately get access to all of Seesmic’s public beta products.

Le Meur told us that a native Windows client was something that Seesmic’s users had been requesting for quite a while. The Seesmic team worked on this new client for the last few months, though the company managed to keep this development under wraps and today’s release comes as a surprise. While there are quite a few good native Twitter clients for OSX, the most popular Twitter clients on Windows are currently AIR apps.
Features
Being a native client, Seesmic can now also make use of some of Windows’ built-in features like a system-wide spellchecker or Windows 7’s location services. While Twitter hasn’t launched it’s location API yet, Seesmic will now be able to tab into this data quickly.
The new client will also allow users to drag and drop their friends’ avatars into user lists.
Just like the current beta version of its AIR app, Seesmic for Windows will support Twitter’s userlists and while the look and feel is similar to the AIR app, the Windows client also features vertical tabs in the sidebar that allow users to quickly switch between different views (all, accounts, userlists and searches).
Plugins for Seesmic
For developers, of course, the new plugin infrastructure also means that they can now offer their services directly in a Twitter client. The current version already showcases plugins from TweetMeme and MrTweet. According to Le Meur, this will also allow other Twitter-like services to build their own plugins and build their own columns in Seesmic without having to establish a formal relationship with the company. In a few weeks, Seesmic will launch a plugin gallery to showcase these extensions.
What About the AIR App?
Seesmic will continue to develop its Adobe AIR client for the time being, though chances are that the company is also looking at developing a native Mac client.
Flash 10.1 coming to just about every platform but iPhone
Flash 10.1 coming to just about every platform but iPhone
![]()
Adobe is kicking off its Adobe MAX developer conference by announcing that version 10.1 of its Flash Player will run on mobile and embedded devices just as it does on the desktop. The culmination of its Open Screen Project launched last year, the update to the rather ubiquitous browser plugin will finally synchronize the Flash experience on all platforms with the exception of arguably one of the most successful smartphones: Apple’s iPhone.
Previously, Adobe offered Flash Lite for some mobile operating systems, which was essentially an older version of Flash optimized for the lower-power processors in cell phones and other mobile devices. Adobe announced the Open Screen Project last year in an attempt to bring a single, ubiquitous platform for developers to deliver rich media applications to desktops and mobile devices without requiring separate development. Flash Player 10.1 attempts to provide a single runtime that should run identically on a Palm Pre, for instance, as it does on a Dell Mini or a Mac Pro. It will be optimized for netbooks and so-called “smartbooks” in addition to smartphone platforms, and will utilize GPU acceleration whenever possible. Flash Lite will still be available for lower-end devices.
AT&T responds on Google questions, throws Apple under the bus
AT&T responds on Google questions, throws Apple under the bus
Filed under: Analysis / Opinion, iPhone, App Store
It’s going to be interesting to watch the next few weeks as AT&T, Apple and Google respond to the FCC questions about which apps get approved for use on the iPhone.
Yesterday, AT&T responded to press questions about this by sending a P.R. email.
“AT&T does not manage or approve applications for the App Store. We have received the letter and will, of course, respond to it.”
You betcha. The problem is that AT&T already publicly copped to keeping the Slingbox software off the Apple iPhone, while letting other bandwidth eaters like YouTube and MLB At Bat live video run without interference. And of course the Google Voice app and the Slingbox app are running fine on BlackBerry phones on the AT&T network. Slingbox is also running on Windows Mobile Smartphones. In conversations with one of the Slingbox developers, I was told Apple was fine with the app until AT&T got involved.
Of course, looking at the statement, it is carefully worded. AT&T does not manage or approve applications. Correct enough. In the case of the Slingbox software, they told Apple to knife it. I don’t think the FCC will be amused by that particular dodge.
One wonders about the deteriorating state of friendship between Apple and AT&T. Recently, AT&T hinted that they don’t expect to be the exclusive iPhone distributor forever, and Apple certainly held them up to a bit of ridicule at the June developer conference on MMS and tethering.
It must be fun on those Apple/AT&T conference calls as they prepare their responses to the FCC.
TUAWAT&T responds on Google questions, throws Apple under the bus originally appeared on The Unofficial Apple Weblog (TUAW) on Sun, 02 Aug 2009 13:00:00 EST. Please see our terms for use of feeds.
Read | Permalink | Email this | Comments









