Posts tagged with "developers"

Safari 5.1 Developer Preview Released

As a last update to the various Dev Centers that a few hours ago received new betas of iOS, OS X Lion and iCloud for developers, Apple has also posted the Safari 5.1 Developer Preview that, as seen on Lion (running 5.1 out of the box), will bring some of the browser’s latest advancements to Snow Leopard. According to Apple:

You can now download Safari 5.1 Developer Preview and take advantage of new technologies, including support for full-screen webpages, media caching with the HTML5 application cache, and better graphics acceleration on Windows.

With Safari 5.1 Developer Preview, you can tap into new extension APIs, including support for popovers, menus, new event classes, and interaction with Reader.

The Developer Preview can be downloaded now from the Safari Dev Center.

iCloud Beta for Developers Goes Live

Right on time after iOS 5 and OS X Lion developer seeds, Apple has updated the Dev Center to include the new iCloud beta for Developer pages, which lists all the instructions to get iCloud going on iOS devices, Macs and iPhoto. Indeed, Apple is including a download link to iPhoto 9.2 to test the new Photo Stream features in a separate development environment (your existing library won’t be ported over). Obviously, many of these features are exclusive to Lion and Apple clearly tells developers to go download the latest OS X Developer Preview if they want to test iCloud’s functionalities.

The iPhoto update will replace your current version of iPhoto. Your existing iPhoto Library will NOT open with this version of iPhoto. For this reason it is recommended that you work on a test/development system ONLY when using this release. You will not be able to revert the system to an earlier version of iPhoto without doing a clean install of Mac OS X and reinstalling iPhoto either from your original installation DVD or by downloading from the Mac App Store.

An iCloud Control Panel for Windows is also available to enable “Photo Stream, Contacts, and Calendar” on a PC through iCloud. A new iCloud account can be set up in the iOS 5 setup assistant or Settings app; in Lion, iCloud can be enabled from the Internet Accounts section in System Preferences – Developer Preview 4 is likely required for this action. Once installed an enabled on all devices, Apple is asking developers to test the new features and take advantage of the new APIs in Lion and iOS 5 – it will be interesting to see how devs will implement the iCloud storage API unveiled this morning.

Mac OS X Lion Developer Preview 4 Now Available

Following iOS 5 beta and iTunes 10.5 beta for Mac, Apple also flipped the switch on Mac OS X Lion Developer Preview 4 – available now for download in the Mac Dev Center. Build number is 11A480b, and it should contain all the new features demoed at the WWDC keynote today, including iCloud integration.

We’ll update this story with more details as they become available.

iTunes 10.5 Beta for Mac Released

Alongside the first beta of iOS 5, Apple also released iTunes 10.5 beta for Mac – which is required to sync iOS 5 devices and enable more iCloud-related features than iTunes 10.3, also waiting for release.

As the changelog confirms, the new iTunes enables compatibility with devices running iOS 5 – we’ll update this story with more details as they come in.

Read more

Apple Releases iOS 5 Beta 1: Details, Screenshots, And More

Apple just updated the iOS Dev Center with the first beta of iOS 5 – registered developers can start the download now. However, as the Dev Center is coming back online as we speak, there might still be errors when trying to download the DMG files.

Update: the Dev Center has come back online for (almost) everyone, and the first news about iOS beta 1 are starting to come in. Notably, some users are already tweeting from iOS 5 as you can see from the screenshots below. Twitter reports “via iOS” as the client that sent the tweet, but redirects to twitter.com when clicking on it. Photos are hosted on Photobucket as part of Twitter’s recently announced photo service.

Read more

Developers: Tweetmarks Will Keep Your Twitter Clients In Sync

I’ve tried several Twitter clients over the past three years; some of them were iPhone apps with no Mac counterparts, others were Mac apps that found their way to iOS with smaller, more affordable versions. After the iPad came around and companies like the The Iconfactory and Echofon showed that it was possible to create a “Twitter ecosystem” outside of Twitter’s official applications (which also happen to be available on the Mac, iPhone and iPad), users like me started wondering whether it was possible to achieve the long-awaited dream of a continuous client – an app that always remembers where you left off, and allows you to start reading (in our case, tweets) again in the same position across devices, through the cloud. For Twitter clients, the concept is simple: if you’ve already read tweets from 3 hours ago on your Mac and then you pick up my iPhone, you shouldn’t see those tweets again.

Echofon has tried to implement this, with results far from perfection. Echofon’s unread sync isn’t always reliable, and when switching devices I often find the app picking the wrong spot in the timeline or automatically scrolling to tweets I’ve already read. Still, the idea is there: as users switch devices, the position of the “last read tweet” should be maintained with online sync.

Manton Reece, developer of Tweet Library for iPad at Riverfold Software, wants to offer developers who are building Twitter clients a solution to easily keep timelines in sync using Tweetmarks. Tweetmarks is a service that runs in the cloud and can be implemented to keep the last-read tweet in sync across apps and devices. With documentation available here, the developer explains:

I’ve already showed it off to a few developers, and if you’re writing a Twitter app I’d love for you to support it too. It will be baked into the next version of Tweet Library.

There are still some unknowns (especially around whether I will need to ask for help to cover hosting costs), but I wanted to launch it now before WWDC so that other Twitter app developers meeting at the conference can give me feedback on the service. Tweetmarks has actually been running for months, and when an opportunity came along this week for a new logo (thanks Alex!), I knew it was past time to finish documenting the service and get it out.

The concept is simple, yet nobody until now managed to pull it off with a system that’s reliable and unobtrusive enough to work “like magic” across platforms and different devices or computers. Developers who are interested in the project can learn more about it here and, personally, I’d love to see a new version of Twitterrific with such a feature (alongside live streams, but that’s another story). If you build and sell Twitter clients for a living, we strongly recommend checking out Tweetmarks for your next multi-platform update – the continuous Twitter client may start right here.

Apple Releases Official WWDC 2011 App

Apple has just released the free, official WWDC app on the App Store – the app is propagating now in iTunes and should be available here. Unlike last year, this year’s WWDC app works both on the iPhone and iPad with a native interface. The WWDC app allows you to check on the conference’s schedule, view floor diagrams of the Moscone Center and create your own schedule of labs, sessions and events you’re planning on attending. The app also comes with a News section to stay on top of the latest announcements made at WWDC throughout the week.

Apple says a new photo gallery will be updated daily with the latest photos from the show floor, labs and events, and the Favorites tab in the bottom toolbar will offer a way to organize sessions you want to attend. The new map feature will allow attendees to tap on a specific session or lab to find the specific level or location they need to go.

Access to the app is limited to WWDC attendees only – developers who purchased a ticket to WWDC ‘11 can use the app.

From the iTunes description:

Reserve Time at the Labs
The WWDC 2011 app allows you to make a reservation at the User Interface, App Review, iTunes Connect, Program Support, or Developer Publication lab. Once you make a lab reservation, it will appear in the schedule section of the app when you filter your view by Favorites.

Sessions and Labs Schedule
View the daily conference schedule including lunchtime and evening events. Filter your view to search by technology, platform, sessions, or labs.

Create Your WWDC Schedule
Tap on the detail view of any session, lab, or event. Then tap “Add to Favorites”. Your selections will be added to the Favorites section of the app and can be updated on-the-go.

Locate Sessions and Labs
Easily find your way around Moscone West with detailed floor maps. You can also tap on a specific session or lab for the level and location where you need to go.

The WWDC ‘11 schedule has also been posted online but it’s only available to owners of a WWDC ticket. Check out more screenshots of the app below. Read more

“iPhone Hooks” Now Allow Apps To Send Photos to Instagram

After the launch of an official API a few months back that allowed developers to read content posted on Instagram and display photos in external iOS, Mac and web apps, the service saw a huge growth in popularity, registered users, and connected applications capable of visualizing Instagram’s streams outside of the (only) official iPhone app. We have seen a plethora of iOS and Mac apps coming out in the past weeks, giving users the possibility to browse Instagram through a “client” different from the app, providing new interactions and interface schemes otherwise impossible without the use of an API. What the API lacks though, is read access to let 3rd-party apps upload to Instagram.

As MG Siegler at TechCrunch reports, Instagram founder Kevin Systrom has no plans on opening a full-read API to let other control the social stream and upload photos not generated with Instagram’s filters and requirements, but they do have a plan to allow developers to easily send files to the Instagram app. This feature is called “iPhone Hooks” and it sounds a lot like iOS’ default “Open In” menu combined with clever URI schemes: provided an application can snap photos and save them to jpeg or png, Instagram can let this app hook into the posting process to transfer the file from app x to Instagram. Just like in the 100 Cameras in 1 iPhone app, users can snap a picture and “send it to Instagram” to apply filters and upload. With iPhone Hooks, any photo app in the future could be updated to support sending a photo to the filter interface, or simply open a specific user stream, tag and location feed. The possibility to pass along photos is of course the most intriguing option, as apps like Photogene, Camera+ or Camera Genius could take advantage of that to shoot photos, let users apply filters and edits, then send to Instagram. iPhone Hooks apparently don’t let developers apply any sort of watermark or ID to the photo (example: “shot with Camera+”) as the file is still processed by Instagram; however, users could still leave a comment to specify what app they used, and overall it’s a good thing for a 3rd-party dev to have an app that works with Instagram.

Co-founder Kevin Systrom compares this functionality to the copy and paste functionality baked into iOS. But again, this is for images, not text. “We wanted to make it easier for other iPhone apps (and iPhone web-apps) to hook into Instagram to open a particular item or post a photo through our app,” co-founder Mike Krieger says. Yes, you read that correctly, this can work with web-based apps too.

Currently, only 100 Cameras in 1 is using this functionality, but Instagram says they’re discussing implementation with other partners.

More details from the Instagram Developer page:

When triggered, Instagram will immediately present the user with our filter screen. The image is preloaded and sized appropriately for Instagram. Other than using the appropriate image format, described above, our only requirement is that the image is at least 612px tall and/or wide. For best results, Instagram prefers opening a JPEG that is 612px by 612px square. If the image is larger, it will be resized dynamically.

An important note: If either dimension of the image is less than 612 pixels, Instagram will present an alert to the user saying we were unable to open the file.

The new feature can be tested in the 100 Cameras in 1 iPhone app, and it’s likely more developers will support it in the next weeks. With iOS 5 rumored to get direct Twitter integration for photos, sharing pictures on our iPhones and iPads could soon become a very different process.

Lodsys Starts Filing Lawsuit Against App Developers

With a series of blog posts published earlier today, Lodsys has confirmed [via MacRumors] that they’ve started filing lawsuits against app developers allegedly infringing patents related to in-app purchases and upgrade links in their mobile applications. Lodsys initially said that they would give developers 21 days to license the patents before filing any lawsuits, but the firm decided to change its schedule in order to defend against Apple’s legal response, which showed support for iOS developers and claimed third-party “app makers” were not infringing any patent as Apple is already licensing patents from Lodsys.

Why did Lodsys sue some App Developers on May 31, 2011

Lodsys chose to move its litigation timing to an earlier date than originally planned, in response to Apple’s threat, in order to preserve its legal options.

As for why they have decided to target small, indie developers who don’t have the resources to legally defend themselves, Lodsys writes:

Why are you targeting Apple developers or Android developers? Why are you picking on small developers who cannot defend themselves?

This story is about accountability for actions. If you are a Developer, it’s about knowledge about the scope and risks of your own business.

Lodsys has only one motivation: we want to get paid for our rights.

Lodsys also posted a response to Apple’s claims that third-party developers using Apple’s SDK and agreeing to the company’s terms are not infringing patents from Lodsys. They company also says they’ve sent a letter to Apple’s legal team, which Apple can publish in its entirety if they want to.

The letter was very surprising as Apple and Lodsys were in confidential discussions and there was clearly disagreement on the interpretation of the license terms of Apple’s agreement.  Before, during and after these interactions, Lodsys has carefully considered this issue and consulted several legal experts to consider Apple’s claims.  We stand firm and restate our previous position that it is the 3rd party Developers that are responsible for the infringement of Lodsys’ patents and they are responsible for securing the rights for their applications.  Developers relying on Apple’s letter do so to their own detriment and are strongly urged to review Apple’s own developer agreements to determine the true extent of Apple’s responsibilities to them.

Lodsys previously explained that usage of in-app purchases would cost developers 0.575% of their US revenue over the period the technology was implemented – for example, an app that generates $1 million in revenue  in one year would pay $5,750 to Lodsys. Finally, Lodsys says they’ll send $1,000 as reimburse to developers hit by the lawsuit if the whole story turns out to be wrong:

While it is true that Apple and Lodsys have an obvious dispute about the scope of Apple’s license to the Lodsys Patents, we are willing to put our money where our mouth is and pay you something if we are wrong.  Therefore, Lodsys offers to pay $1,000 to each entity to whom we have sent an infringement notice for infringement on the iOS platform, or that we send a notice to in the future, if it turns out that the scope of Apple’s existing license rights apply to fully license you with respect to our claim relating to your App on Apple iOS.

As many previously suggested after Apple’s response, the story is far from over and Lodsys appears to be pursuing its agenda by suing developers that don’t agree to pay licensing fees. Several bloggers broke down Lodsys’ patent claims in the past weeks, and the EFF even came out and said Apple should stand up for its developers.

Update: Florian Mueller of FOSSpatents tweets the names of the companies and developers sued by Lodsys today.