This Week's Sponsor:

Direct Mail

Professional Email Marketing Built Just for Mac Users


Favs for iPhone

I don’t normally begin articles with puns, but Favs has become one of my new favorite apps. Developed by Dirk Holtwick, Favs is “an app for your Internet favorites” – it collects items you’ve liked, starred, or marked as favorite on a variety of social networks and online services. In my review of the Mac version, I wrote:

Services like Instapaper and Pinboard empower you to “read later” and “bookmark” the things you like. Favs runs at a higher level, collecting favorites from other services that already enable you to save favorites. As I said, this kind of app is a web nerd’s dream come true for me.

Released yesterday, Favs for iPhone is a $2.99 mobile companion that serves the same purpose of Favs for Mac – it offers a unified interface to browse favorite items from multiple sources. The main screen features three general tabs for All items, Inbox, and Archive. However, I never use Favs’ own read/unread indicators, because I don’t want to “feel the guilt” of having too many favorites in my accounts. For this reason, I am glad Favs for iPhone lets me hide unread counts from the Settings, which also reveal iCloud sync will be coming soon to keep account information synced across Mac and iOS devices. I very much prefer to browse favorites by their original source.

The main screen of Favs also reveals a custom “pull to refresh” implementation that uses two stars that need to be aligned to initiate a new sync session. This action will refresh all your sources and check for new favorite items (single sources can be refreshed as well).

Like the Mac app, Favs for iPhone supports the following services:

  • Delicious
  • Dribbble
  • Facebook
  • Flattr
  • Flickr
  • GitHub
  • Google Reader
  • Instagram
  • Instapaper
  • Pinboard
  • Pocket
  • Readability
  • StackOverflow
  • Twitter
  • Vimeo
  • YouTube
  • Zootool

Tapping on items containing links will open an embedded web view in the lower portion of the screen. An option to load the Readability version of an article is present, as well as buttons to email a URL, tweet it, copy it, or launch it in Safari.

The app’s performances are good, but not perfect. I found Favs to be slightly slowed down when scrolling through thousands of Twitter favorites, though I recognize I may be an edge case here. However, after the initial refresh, the app was quite smooth at switching between Twitter, Google Reader, Facebook, and the main view. The sync animation could use some further optimizations.

If you already use Favs on the Mac, there’s no question you’ll want to take a look at the iPhone version. Favs for iPhone has a clean design, works with a lot of services, and, overall, leverages the convenience of having all your Internet favorites always with you. Favs is $2.99 on the App Store.


Instapaper’s Background Update Locations

Instapaper’s Background Update Locations

Last night, Instapaper was updated with a major new feature: Background Update Locations. Here’s how it works:

Now, with Background Update Locations, Instapaper can automatically download new articles whenever you enter or leave locations such as your home or workplace. Visit the Settings panel to set it up. (Requires an iPhone or 3G/4G-equipped iPad.)

I have been testing the feature this afternoon, and while I couldn’t get it to work initially, I think I have figured it out. Basically, Instapaper uses iOS geofencing to determine when you enter or leave a location (you can store up to 10 locations inside Instapaper). The geofencing, however, isn’t really precise, as granularity may vary, and it could be based on a combination of cell tower strength and triangulation. Having tried geofencing with Apple’s own Reminders, I can attest that location-based alerts were already problematic in my town; so my guess is that today, when I couldn’t get Instapaper to download items in the background, the issue was with geofencing in Viterbo – definitely not with Instapaper. I have noticed that some locations in my town just won’t fire off the geofence; I have no idea why this is happening, and I hope Apple fixes it in iOS 6 (perhaps through their new fancy mapping service).

Fortunately, Instapaper’s Background Update Locations are now working with the place I care about – my house. I was able to leave, drive around town, and then I found articles waiting in my list, already downloaded. It’s a really nice option to have, and I’m glad Marco was inspired by News.me to implement it.

Get Instapaper 4.2.2 from the App Store.

Permalink

iOS 6 Mockups

iOS 6 Mockups

The Verge Forums member “gizmosachin” created some nice mockups of iOS 6 and the next-generation iPhone based on recent rumors.

Well this week we saw the “composite” image of the new iOS 6 Maps app, the blurrycam photos of the new iPhone, and with the WWDC 2012 app it seems that iOS 6 will make most UI elements silver like their counterparts on the iPad. Thought I’d make some mockups of the new iPhone running Safari and the supposed new Maps app just for fun. I couldn’t find any high res C3 Tech images so I just used the OpenStreetMap maps that Apple currently uses in iPhoto.

According to speculation surrounding the next major version of iOS, Apple will switch to a “silver” theme – roughly the same that has been used on the iPad since iPhone OS 3.2. Marco Arment believes the iPhone UIKit widget styling (the stock blue element) is out of style. Cult of Mac thinks that the recently released WWDC app and iPhoto for iOS set the stage for silver coming to the iPhone soon.

In theory, apps that use stock UI items provided by Apple would work “out of the box” with an updated color scheme. However, developers who relied on custom icons, colors, and other patterns would still need to optimize their apps for the new UIKit – and that’s exactly why Apple “previews” new version of iOS at WWDC before their Fall release.

Composite mockups of iOS 6 Maps based on “leaked” screenshots of the software first surfaced last week. Check out more mockups at The Verge.

Permalink

Ecclesia Is A Stunning Audiovisual App Experiment

Usually, I’m a quite drastic purist when it comes to music. Music is art for the ear, and made for distraction-free listening. That’s the reason why I consider music visualization as rubbish most of the time. I never liked to look at computer-generated 3D figures, which are randomly moving without being truly connected to the music.

But then I found an interesting interview on Overlapps with Eric Wahlforss, the founder and CTO of SoundCloud, the well-known social sound sharing network. He is musically active under the pseudonym Forss and recently released a new album titled Ecclesia. The record is available for free (when you sign up to Forss’ newsletter) on his website, where you can also listen to every song off it completely. But his real engagement with this album lays in the idea of making it multi-layered by creating a visualization app with 3D graphics, effects, and movement connected to the music. Together with the design studio untouch.fm and designer Leo Lass, he created an iPad app with extensive visuals to enhance his newest record with some stunning 3D artwork. Read more


The Siri API

The Siri API

Samuel Iglesias has written an excellent post detailing the (possible) challenges developers will have to cope with if Apple decides to release a Siri API.

The second half of Siri integration, Semantics, is the tricky part: something that most iOS developers have never dealt with. Semantics will attempt to capture the various ways a user can ask for something, and, more importantly, the ways Siri, in turn, can ask for more information should that be required. This means that developers will need to imagine and provide “hints” about the numerous ways a user can ask for something. Sure, machine learning can cover some of that, but at this early stage Siri will need human supervision to work seamlessly.

This is exactly what I have been wondering since speculation on the Siri API started last year. How will an app be capable of telling Siri the kinds of input (read: natural language) it accepts? Will developers have to do it manually? Will Apple provide a series of automated tools to associate specific features (say, creating a task in OmniFocus) with common expressions and words? And how is Apple going to look into the natural language processing developers will implement in their apps?

Of course, the Siri API is still at the speculation stage, but it does make sense to greatly expand upon Siri’s capabilities as an assistant capable of working with any app. The TBA sessions at WWDC are intriguing, and Tim Cook said we’ll be pleased with the direction they’re taking with Siri. Right now, I’d say integrating with third-party software would be a fantastic direction.

Permalink

Mac App Store vs Buying Direct

Mac App Store vs Buying Direct

Wolf Rentzsch has published a good piece outlining the pros and cons of buying software through Apple’s Mac App Store, or directly from a developer’s website.

Some developers are going out of their way to allow seamless cross-grading from Mac App Store versions of their apps to direct apps, which is commendable and helps alleviate somewhat the situation Apple has created. Sandboxing is just the latest App Store rule change, I’m sure there’s more to come. All things being equal, it’s safer to buy directly instead of being cut off from your own software based on an arbitrary Apple policy change.

Sandboxing may be the latest requirement to get apps on the Mac App Store, but the trade-off involved with selling software through Apple’s channel has stayed the same since 2011: exposure vs. risk of change due to Apple’s policy. Because the environment is controlled and actively promoted by Apple, a developer gets all the perks of a store pre-installed on every Mac: millions of potential customers whose buying decision is just a click away, and nicely designed sections to showcase new apps (though Apple has to do more). On the other hand, because Apple gets to decide which apps and which functionalities are safe for the App Store, changes happen, like Sandboxing.

For the user, the convenience of the Mac App Store is obvious. Purchases are tied to an Apple ID, updates are easy, and the ecosystem is integrated with an existing structure (iTunes). Unlike John Gruber, I don’t think Sandboxing will be compelling for typical users, as I don’t see Apple showcasing Sandboxing-enabled apps the way they did for iCloud-enabled apps or apps updated with Lion features. It’s too technical, but Apple may figure out a way to market it (perhaps again the “Apps Enhanced for OS X Lion” section with new additions).

For developers, the Mac App Store means exposure to millions of eyeballs but also to Apple’s ever-changing strategies and technologies. The problem with Sandboxing, I believe, is that it introduced a change that is forcing developers of existing apps to reconsider functionalities that are not compatible with the Mac App Store anymore. If this will lead to serious fragmentation of Mac software with a proliferation of deeply different Mac App Store and “website versions” of the same apps, we’ll see.

Also worth reading: Lex Friedman’s story at Macworld on the first day of Sandboxing in the Mac App Store.

Permalink

Harry McCracken Reviews the Original Apple MessagePad

Harry McCracken Reviews the Original Apple MessagePad

When Jobs decided to shut down the Newton division, color screens were still unaffordable, touch input was crude and wireless data didn’t get much more exciting than two-way paging. When he launched the first iPhone nine years later, technology allowed Apple to build the sort of devices it wanted to create in the 1990s, but couldn’t. He may have killed Newton, but he didn’t kill the dream behind it so much as press a giant pause button–and after finally spending quality time with a MessagePad, I’m more convinced than ever that he made the right call.

Apple’s MessagePads were devices that were both ahead of their time and poorly executed. It embodied everything Apple wanted to do — its tie-ins with the iPhones and iPads of today are clearly evident — but the Newton platform and the MessagePads just barely teetered on self-proclaimed success before their eventual hiatus. Despite the MessagePad’s lack of sales and its post-designation as a failed product, Harry McCracken re-visited John Sculley’s infamous product, reviewing the original MessagePad while investigating market demand and how the press received the product at the time of its unveiling. The three page article left me with some interesting take-aways about the climate of technology at the time of the early 90s, and how the Newton platform itself contributed to Apple’s later successes in both hardware and software design. A bulk of the article focuses on the technology introduced with the original MessagePad itself, but that insight is used to build a timeline of the product’s evolution whose concepts lead us to the devices we have today.

Image Credit: Time Techland

Permalink

MG Siegler: Facebook Integration Coming To iOS 6

MG Siegler: Facebook Integration Coming To iOS 6

According to MG Siegler at TechCrunch, Apple’s upcoming new version of iOS – set to be unveiled at WWDC – will feature Facebook integration, similarly to how Twitter was integrated into iOS 5 last year.

It’s important to note that Apple being Apple, something could change in the next week and a half (see again: Facebook/Ping). But as of right now, Facebook is a go in iOS “Sundance”. One thing still being hammered out according to our sources is how sharing will work. Sharing is the other big part of the iOS/Twitter integration, and will be important for iOS/Facebook integration as well. But Facebook is significantly more complicated than Twitter in that there are all kinds of permissions for what you can post where and who can see what. And Open Graph adds another layer of complexity to all of this.

It is unclear for now how Facebook integration could work at a system level on iOS, presumably allowing users to share status updates, photos, and videos. Taking Twitter integration as a reference, it is worth noting how Apple doesn’t let users casually tweet at any time from iOS, having enabled the “tweet sheet” only in specific applications such as Safari and Photos. Facebook is more complex than Twitter in terms of privacy controls and functionalities, and we can only assume the system integration Apple has worked on will still strive for simplicity and intuitiveness when communicating with the service.

There are a series of factors as to why Apple could add Facebook integration to iOS. Firstly, such integration was spotted years ago into an unreleased build of iOS 4. Then, recent remarks by Apple CEO Tim Cook confirmed the two companies have mutual respect for each other, and that they are working closer together to provide the “best experience” with Facebook to iOS users. Tim Cook himself said to “stay tuned” about it. Last, Facebook’s own apps for iOS (including the recently released Facebook Camera) and the plethora of third-party Facebook-connected apps could incredibly benefit from direct integration on iOS.

Apple’s WWDC kicks off on June 11 in San Francisco.

Permalink

Review: DM1 Drum Machine for iPad

The day the iPad was unveiled, the whole Apple community screamed that the device would change the way we look at arts and be the center of any kind of creation process in mankind’s mobile future. While this mainly came true for writing and visual arts (think of apps like iA writer or procreate), it still lacks when it comes to mobile music making. Due to the absence of multiple optical inputs like FireWire, the iPad is not suited to be the only mobile recording studio. After the first wave of electronic music software with the KORG line (iElectribe, iMS-20, iKaossilator etc.) as the most prominent example, new electronic music production environments got very rare. I was very excited, however, when I saw this new iPad drum machine on Beautiful Pixels called DM1 Drum Machine. The demo video of Fingerlab’s new product promised a decent, easy, but powerful workstation on the road for a very fair price, so I downloaded it.

And DM1 didn’t disappoint me. The DM1 was the very first drum machine software I ever bought for iOS devices; I tried iElectribe once on a friend’s iPad, but even that iconic (and expensive) app seemed more like a toy than a serious musical instrument to me. On the iPad, I am after professional software, something that encourages me to create awesome music. And because you cannot impress through the haptic feel of a synth on a flat screen, you need UI simplicity combined with a stunning feature set to get your product to the user. With the DM1, I  finally found a music app that fulfills those needs.

In their demo video, Fingerlab shows a 3D animation of the DM1 as a Little Phatty-like workstation with several areas for its five different main features: a step sequencer, drum pads to manually enter beats, a mixer for each sequenced kit part, effects, and song information with structuring options. In the real app, those five features are available via the top selection bar right beside the three most basic selecting options to set the basis for a song – BPM, selected sound, and the currently played pattern, and a play button. In the following lines, I’ll firstly dive into each of these parts, and cover the visual arrangement, DM1’s production possibilities, and some features I’d wish for in future app updates to make the app even more pro-oriented.

Step Sequencer and Sounds

In terms of the provided variety of sounds, DM1 is the most professional effort I’ve seen to date. 19 classic drum kits (e.g. the iconic Roland machines TR-808 and TR-606), 19 acoustic sets from Ludwig drum kits to Cello sounds and Wurlitzer pianos, and 26 DM1-only kit including Bristol-styled beats and freaky synth sounds speak for themselves. In the 16/32-step sequencer, these sounds are divided into 9 kit parts: kick, snare, open and closed Hi-Hat, clap, rimshot, cowbell, tom, and cymbal. The sounds connected to these parts vary a lot, so it can occur (especially when using a synth sound) that the app plays melodic elements on the rimshot and cowbell steps.

This brings us to creating sequences with the step sequencer. In both 16 and 32 mode (which is twice as long, not twice as fast) tapping single steps works flawlessly; aiming and selecting is easy. The 4 bars are separated using different shades of grey, and they can also be easily identified using the LEDs on top, where each beginning bar is indicated with a bigger one.

Clearing steps is just as simple; you can even drag you finger around the whole screen and every step you swipe over is getting activated or de-activated, depending on what your first tap did. If this still is not fast enough for you, ou can also use the “hold to clear” button below the feature selection panel. This and the nearest three buttons (metronome, a very functional random rhythm creator, and the obligatory, very neatly implemented help menu) are also available over multiple screens.

Any time you change a single step, it is automatically saved in the activated pattern. You can create up to 25 different patterns, which then can be arranged to a final piece in the “song” section (I’ll come to that later). If you want multiple patterns (which are built upon each other to create an evolving rhythm), you can also copy one pattern into another slot, add some elements to it, and the basic beat will still be the same.

Drumpads

If you’re better at playing than imagining or experimenting with new rhythms using the sequencer (when you come from drumming for instance), you can use the drumpads combined with the integrated quantized recorder to teach the sequencer the rhythms you have in your head. The pads are really big and very responsive, even when double-tapping with two fingers to create a 16 step Hi-Hat beat.

Unfortunately, the app doesn’t play a bar solely with the metronome before a recording begins, so you have to wait four whole bars until you can input your beats properly. But the conversion into the single steps works perfectly and instantly. To make the recorded beats even more personal, there’s a large, functional pitch-shifting ribbon to customize the sequence further (this can also be applied after the four bars are recorded).

Mixing and Customizing Single Steps

The third big feature is the most used out one, with which you can edit any part of the available kit anyhow you can imagine: the kit mixer. In a moog-styled layout you can customize every sound in level, pitch, and length to make it sounds just the way you want it. You can reverse the whole sound of a step by holding the play button, and pan the part to the right or left to create a stereo effect. Set the sound on solo mode and use the bottom bar to add or delete steps for a specific track. But the to me, the most powerful feature is the velocity leveler that you can bring up by tapping the diagram-like button in the nav bar. Although the upcoming vertical bars (of which lighter ones indicate active, changeable steps) are not perfectly responsive to sliding to change their level, you can create crescendos and decrescendos with one tap here, something I always use when I start a new project.

FX and Song Timeline

The fourth way to customize your sequences is the FX section. It’s powerful, but also pretty hard to handle properly. Here’s why: you can select an effect (overdrive, delay, phaser, etc.), set the dry/wet mix portion, tap the red “on” button, and the effect is immediately applied to your mix. Yet most of the time, you’ll then think: “This is destroying the whole thing”. The reason for that lies within the two-axis field which is used to set the two main parameters of the effects; for instance, when using the delay, these parameters are Repeat (y-axis) and Speed (x-axis) with respective values from 0 to 100. Unlike the velocity columns, this is very responsive. Every time you move the LED dot indicating the current setting just a little bit, the sound changes more or less completely. As you see, this offers both a huge amount of treasured sounds, but can be completely counterproductive.

If you’re done creating, editing and customizing your sounds, tap the song panel to turn “just playing around with a drum machine app” into serious business. Here you can make an actual song out of your single beats; just drag and drop patterns into the timeline, and tap the play button to listen to your arrangement. If you like what you hear, you can export the song (or single patterns)as a .wav file to iTunes or send it via mail. You can even sync in via WIST to another device with the DM1 installed to have it on all of your devices or share your work with friends or colleagues.

Fingerlab also integrated AudioCopy to send the created beats to a variety of other music production apps like FourTrack or AirWrench. Other features in the song panel include MIDI Input (using auto or pre-selected channels to enable plug and play using a USB Camera Connection kit) and a swing option to play around with the overall song rhythm.

User Interface

The biggest issue I had with the app’s design was a really impudent one considering the immense feature set: the DM1 does not have Retina graphics. The features all worked great – my problem with the app was that it didn’t look nice. But this would need just an update, and considering the rest of the UI, I definitely excuse this lack.

I mentioned the 3D version of the machine the devs designed to visualize the feature set. This also makes the UI more understandable. Using the cool designed popups and the top navigation bars is easy after watching the demo video – don’t get me wrong, the app is very intuitive even if you don’t watch any demo, but it takes some time to find out how every feature works.

The leather background fits very well with the sepia tones the designers used for the buttons, text panels, and other controls. I disliked some buttons’ 3D look though, especially the square ones like the play button. Nevertheless, the UI design fits the needs of the feature set, making it understandable and flexible, and – what’s most important – it never privileges any feature to ensure that you will equally find and use all of them. Ultimately, this is the most intriguing aspect of the DM1: you always use every part of it and are thrown into a very clear but flexible workflow – which is optimized for mobile use, but still feels very professional and delivers great outputs.

Wish List

What follows now is something I normally avoid; I consider myself in a position to review and criticize existing features, but not suggest new ones. With music apps, though, it’s a little different. I use several desktop products including GarageBand and Ableton Live, and I always think about which features could be transferred to mobile apps while using them. DM1 offers many of such features, but some – even quite simple and obvious ones – are still missing in my opinion, and they could be easily added to make the app even more stunning.

First: better organization. If you like the app as much as I do, you will create many projects to dive into all those sounds and effects. And you’ll enjoy that for sure. What you won’t enjoy, however, is finding your favorite sounds and saved songs again. Both are displayed in one single list with dividers for categories which completely lack of folders, tags or anything. And especially the list of saved songs is designed way to small for the iPad’s large screen. A simple folder structure within this list could solve this problem, and having a separate list for your favorite sounds would also be pretty useful.

Secondly, I would like to remind developers of such professional software that iOS devices have multitouch. Please make use of it. It would’ve been both intuitive, very cool, and useful to use, say, two-finger swipe to switch between panels.

Last, but certainly not least, I imagined many possible extra features while using the DM1 to extend it up to the situation where you can have it it as your sole production platform, not just on the road, but also at home. In my opinion, the app doesn’t need not that much to reach that position. What it misses are basically just three things: 1) more options to create melodies like more synth kits (or maybe just indicating existing melodic steps better) to create whole songs with beat, basslines and hooks, 2) the creation of own drum kits on the go, and 3) the capability of applying different effects to different patterns. Currently, the two effects you set are applied to the whole song, whether you like it or not (they even cannot been disabled for single patterns). Some ideas in this direction would turn this drum machine into a full-featured workstation.

Wrap Up

I urge you to get DM1 Drum Machine for your iPad. If you’re into music and rhythm and whether you have experience in using sequencers or not, you will have a lot of fun with the app. It is flexible and offers an incredible amount of directions your sound can go. And, believe it or not, this whole package is available for just $4.99 in the App Store.