tailieunhanh - iPhone Design Award-Winning Projects phần 9

chủ yếu là vì tôi nghĩ rằng sẽ dễ dàng hơn cho tất cả mọi người, mà còn vì nó cho phép bất cứ điều gì mà sử dụng Growl cũng sử dụng prowl, không có bất kỳ sửa đổi hoặc redistributions. Và những gì tuyệt vời là Windows Growl bản sao tiếng gầm gừ và Growl cho Windows cũng đã thông qua khả năng sử dụng prowl. | 156 CHAPTER 12 Iterative Design But Jetha or AJ as most people call him isn t talking about billable hours. And he s not talking about the urgent kind of time right before a looming deadline. He s talking about a much more whimsical version time to stew. Unlike most of the apps that Mac users see and use every day Billings 3 and its companion iPhone app Billings Touch exist under the principle that time takes productivity not the other way around. It s an app that knows when you re working and when you re not and it can tell you when to stop working and bill somebody on schedule. And it has to be intuitive meticulous streamlined and steadfast because it s not just another productivity tool when it comes to invoicing apps a bum feature or confusing workflow means literally screwing with users livelihoods. When Billings is done bouncing in your dock time isn t o the essence. It is the essence. Fitting then that it would be the clock not technical prowess inspiration or any number of more nebulous ingredients that would be Billings perennial threat. It started says AJ with Billings 2. There was a tremendous amount of debate about workflow back then he says. One of our developers at the time was an interaction expert. So we went back and forth with him trying to find a good medium but ultimately development stopped for a good two or three weeks he says. Work pushed on but problems bubbled up. We d get into heated debates taking off more weeks to hash out ideas. Then we d come back to the original idea and that s how we d know it was right. Billings 3 which launched in September 2008 was burdened by the same democratic stalling but it may have been the secret to the app s success. A lot of times customers make requests but if you dig deeper and ask for the use cases behind them you find they don t necessarily know what they re asking for he says echoing other developers in this book. What appears to be the solution initially isn t always the best solution. If you jump .