I'm reading through the Wired back catalog. While it's occasionally amazing how much was correctly predicted, there are just as many misses like this one. Most of all, I find it interesting that some things never change.
2,175 karma · joined May 17, 2009
Sometimes I write things here: https://writing.markchristian.org
I have built some things over the years. Some of them were pretty okay at the time.
http://isitsociallyacceptabletolistentoalliwantforchristmasisyouyet.com https://somanyfoodtrucks.com https://github.com/shinypb/watchnrun https://github.com/shinypb/feedfilterer http://whimsicalifornia.com/timebar https://shinyplasticbag.com/dragondrop https://shinyplasticbag.com/lidpop http://jbrewer.github.com/Responsive-Measure/ http://ffffallback.com/ http://appcachefacts.info http://openkeyval.org http://www.helpbubble.com/ http://prioritizemywork.com/
I'm reading through the Wired back catalog. While it's occasionally amazing how much was correctly predicted, there are just as many misses like this one. Most of all, I find it interesting that some things never change.
I'm not sure I can detect whether another app is non-natively full screened, I'm afraid. I'll give it a poke, but to be honest, working with full screen stuff is a bit difficulty on OS X. The APIs aren't super comprehensive.
Filling up rather than emptying out is a fun idea; I'll add that to the ol' feature request list.
You can change the overlay colour by clicking the blue rectangle next to the menu bar preview.
First pass at support: do you have any other mouse-related software installed? Some Microsoft Intellimouse support software has been particularly troublesome.
* Timebar actually compensates for sleep, so if you set an 8 hour timer at 12 PM, it will finish at 8 PM even if your computer was asleep for some of the time in between. * Definitely going to re-label this; there are a few little UI tweaks in the pipeline. Keep the suggestions coming; they're very welcome. * So, the very first drafts of this were built around the idea of a natural language text field for setting the time. I ended up abandoning it because a) I have no experience with NLP and b) since it's a menu bar app, your hand is already on your mouse/trackpad — not your keyboard. I think the Alfred workflows will go a long way towards letting power users work at warp speed. :)
As for separate pre-defined timers, that's a pretty good idea, but I'm not entirely sure how to do that without making it quite a bit more complex. That being said, I do plan on adding AppleScript support and some Alfred workflows, so I think we can definitely get things cookin'. :)
Oh, yes — an audible alarm is a great idea. I'll explore that for the first update. I hope to start hacking on 1.1 with my lady tomorrow night. :)
The App Store utterly dominates.
However, I still think it's good to have your own release path as well, because it gives you a bit more courage to argue with Apple when you need to. :)
My app is $4.99, so I net $4.55 from each copy sold independently, and $3.50 from each copy sold from Apple. That's a substantial bump.
I use Stripe for payment processing with a custom in-app UI for buying the app. Stripe has been great — they charge 50c+2.9%, so I lose about 44c per copy of DragonDrop sold (versus losing about $1.50 to Apple in the App Store).
I suggest releasing in the App Store if possible, but selling independently, too. The whole thing took about a day to set up and has been totally automatic since then.