1) Tweet when ever a meeting has reached quorum and when it is ended, as long as you have selected that you wish to tweet.  While this would be the simplest, it may not be prudent to tweet that you just wasted a ton of money by being in a meeting with your boss.

2) Only tweet when a meeting has completed.  

3) Only tweet when quorum is reached.

4) Ask at each major point, do you want to tweet about this event, i.e.  If you press quorum achieved, ask if you wish to tweet, or if your meetin ended, instead of asking "Was it worth it", ask do you want to tweet, and if you answer yes, then ask was it worth it.  This would allow the tweet to say "We just spent $1billion and it was worth it :)"

What do you think?  Any suggestions?

Do you think that it would make more sense to have a data store in the cloud which would automatically sync up when you start the app?  We do want to add a mashup of wasted time around the globe, but did not want to store any specific data.  If we have data persistence across devices, you could show total global wasted time within the app itself.  What do you think of this idea?

And just to complete the image.. here is it small (as it would show in the app...

 -- And just for fun.. the clock in app size --

 --- I think the clock shrinks down well....

These are early drafts... and the days of the week on the calendar are not consistent.. (learning new tricks in Photoshop - may need to get a book :) ).

1) For the toggle on hourly verses salary rates

A) Hourly would be represented by a clock. 

B) Salary would be represented by a calendar

2) Our toughest design will be for meeting information, but here's what we are thinking so far:

A) Start a meeting would be represented by a runner in the starting blocks

B) Quorum achieved is what is driving the design here - There is no universal quorum graphic, so a runner in full stride is our graphic of choice

C) and to complete the image - Meeting Ended has to be crossing the finish line, and breaking thru the tape.

3) If we do this, our goal is to remove the instructions page.  It is, after all, a bit lame.

If you have any suggestions, we'd love to hear from you.  Comment to this thread or drop us an email at support.

• Disallowing the paste feature - some of our users have been playing with entering text in the rate field.  The good news is that the program will treat this as a value of 0.
• Better graphics - Our goal is to make the entire application language neutral.
• Localization of the currency value - Right now the rate is currency neutral, but wouldn't you like to see your phone's currency setting?
• Odometers instead of text - We'd like to have a spinning odometer showing you the values as they spin up higher and higher. 

While each of these seem pretty easy, we will not publish until we have at least the bottom two done (they are the harder ones).  We value your feedback, so drop us an email at support or comment on this post.

A couple of changes are planned for version 1.2, including more graphic enhancements.  Can't wait to submit.