tumultco

I didn't spend time doing an analysis beforehand. I did IE8 support which was impossible to ignore given its ~30% market share at the time. A friend in our early alpha testing said she couldn't use our app unless it supported IE6 for her site. Since I valued her feedback I started hacking to see how difficult it would be, and got most features working that day. From our [controlled output] perspective, IE6 really isn't that much different than IE8. The end of the story is that she filed several critical bugs dealing with how we insulate our JavaScript against other scripts, so it was worth it from that perspective alone!

You're correct, as many of these hacks to fall down in many cases or in unexpected ways. We've got hacks upon hacks to get them to work decently! These are items we (or tools) can manage though.

From our user perspective, non-transparent PNG in IE6 is the major problem. Partial transparency and 24-bit color support are vital for artist assets and not having them can influence the entire design.

Looks like this uses anywhere from 4-20% CPU while running on my 3.4 GHz quad-core i7 iMac. Have you thought about laptop battery life/power bill/world pollution implications?

Small thing: on the http://trypair.com/ site, I tried clicking the play button several times expecting a video demo until it scrolled up beyond the initial screenshot.

Here's the support article from google which describes why viewcounts become frozen around the 300 mark:

http://support.google.com/youtube/bin/answer.py?hl=en&an...

Agreed we need to tackle this -- I would definitely like to beef up how we support mobile devices better.

Bret and I actually overlapped at Apple a little bit, his work has always been insightful and amazing.

His first demo also is very similar to our own HyperEdit (http://tumultco.com/HyperEdit/) though he takes the concept to the next level.

Thanks for illustrating how we scale with the screenshot! :)

That's a good point. I put it at number one because I knew it was the first thing that would be noticed anyways and would only take a couple seconds to show. While I believe it is an improvement I wanted call it out to help manage the change (as any change can represent friction). Probably the end would have been a more appropriate place.

Many other places showing what has changed in 1.5 have the "top ten" feature list in more of a priority order in which I put the icon change in the last position. The video I made as more of a comprehensive guide to the changes for our existing users than a highlights video. Ordering in many cases was somewhat set by the features themselves; for example it is hard to show of smaller feature of the new animations timing functions without first discussing the more significant redesigned animation interface, etc.

I'd be curious if after some time you still hold that opinion, feel free to ping me in a couple weeks.

The good thing is Mac OS has always been great about allowing icon changes by copying/pasting in the get info window. I probably spent too much time as a kid redoing all the system 7 app icons :).

Thanks, I appreciate your thoughts. Discussion of the icon isn't unexpected given:

- it is the first change users will notice

- the style is quite distinct from the old icon; even large software changes like the redesigned animation interface aren't as visually different

- software is a personal experience

We do have separate variants for 32x32 and 16x16 sizes, which are visible when scaling in the Finder.

While the Hummingbird icon was well balanced and indicated motion, there were a few reasons that made us change:

- We didn't feel it was Mac OS X-y enough; it didn't seem to fit in with other icons in my Dock.

- The concept itself was too abstract. Given our product name is also abstract, we wanted something a little more concrete. The new concept is an animator's lightbox, which we felt is closer to its purpose. Admittedly not a lot of people have seen this in their lives...

- We wanted some way to convey the HTML5 given its importance in our app.

- Everyone is doing birds nowadays!

Meant to point out that we're YC W11.

There's a trend towards lists in new CSS values (see transforms, transitions, etc.), but this seems to go against making site styles easily customizable using cascading/inheritance. It is a bigger pain to programmatically control. How about one value for one property:

  font-caps: small; /* or none */
  
  font-swash: contextual; /* or none */
  

This also gives room for future flexibility in values.

Were you trying to make the point that your analytics can be for more than reporting? Ex: if you have a platform then you can feed the data back into a user-facing site to drive sales of popular items, make automated tweaks, or offer experiences tailored to the specific visitor?

This is a good idea. Practically no one would argue against charitable matching, so it gives Tim Cook an early win with rank-and-file employees. As COO, many within Apple have not interacted with Cook, so this popular move helps establish loyalty and reduce leadership uncertainty.

In his first company-wide email as CEO he said, "I want you to be confident that Apple is not going to change," yet Cook clearly knows he is not Steve Jobs. This sets a marker to distinguish that his run of the company will be different even if he is going to try to preserve Apple's DNA.

The HTML5 export ability in CS5 is rather limited now (can't do ActionScript nor many other features), and we think there will always be a mismatch in capabilities.

We developed Hype from the ground up to support the latest HTML5 features as well as some decent fallbacks and warnings for older browsers. It can be customized with JavaScript and interact with the rest of your page.

Hype was also built to be very easy to use; if you know how to use PowerPoint you can use Hype. It's "heritage" comes from how people make interactive content today, instead of the traditional animation space.

My company got a sneak peak using TellFi, and I'm pretty excited about it. We don't yet have a physical location, but using their service we were able to get a business number and setup menu systems ("for such-and-such, press 2") with appropriate forwarding to our cell phones. This gives us a legitimacy we otherwise wouldn't have.

Just as I personally don't see the point for a land line now that I've got a cell phone, I likewise don't see why I would want to worry about getting a real phone system when we have TellFi.

Nice! Very similar to my live HTML/PHP editor for Mac OS X called HyperEdit:

http://www.tumultco.com/HyperEdit/

A couple of ideas:

* Utilize contenteditable to go the opposite direction

* Bookmarklet to open any page you are viewing in htmlinstant.com

* Save the document to local storage (cookie or html5 client-side db) in case the page is closed

* Snippets for commonly used functions (like table or list tags)

And of course the further you take the editor, the more capable this will be. Bespin (https://bespin.mozillalabs.com/) in the best in-browser editor I've seen.