After initially rejecting Boosty (because I wrote to ~/Library/Boostivity) I resubmitted it, and within a few hours I got an email saying Boosty was accepted into the Mac App Store and will be released on Friday (Aug. 26) for $.99 for the first 24 hours!!! You can purchase Boosty here.
Boosty has been submitted and will (hopefully) be released next Friday for $.99 for the first 24 hours and $4.99 afterwards.
Yesterday, I completed Boosty's last feature! I've also signed up for the Mac developer program (now I'm just waiting for the email activating my account).
Today, I focused on a few UI fixes and I made the icon (which is shown later on in this post). All that's left is two final UI changes, and a couple bug fixes, one that has to do with a UI inconsistancy and another that has to do with memory management, specifically in the Task Controller and Notification Controller.
And now, Boosty's icon!
For the past week I've been squashing bugs, writing features, and testing. I can say that Boosty is now 90% done. One "secret feature" has been completed, the other is just getting going.
I hope to finish Boosty by the 10th, from there I will be using it full time to manage my tasks and hopefully fix a few bugs. Then I'll submit it to the Mac App Store after I'm satisfied it's fully functional.
And now, I present the (almost) final UI! The killer photoshop job is hiding the "secret feature" (I'll reveal them after I submit Boosty to the App Store).
I've decided to change the name of Boostivity. I never really liked it, maybe it was because there were two t's in it, who knows. Boostivity was a combination of the words "boost" and "productivity."
Boostivity is now known as Boosty.
This name change will make a lot more sense when you see what I have in store. It's pretty awesome.
The past few days I’ve been hard at work on Boostivity.
Notifications are now complete and look pretty good.
I’ve realized that a custom font is not the way to go with the secret feature. Let’s just say it didn’t look pretty, letters were on top of one another, the spacing wasn’t quite right, everything was off. I’ve decided that I’m going to instead use images instead, since I know I can do that and make it look great.
I’ve fixed a lot of bugs too, one that effected notifications in a big way, which luckily was a quick fix.
Notifications are about 50% done. I now get a notification from my task controller (using NSNotificationCenter) and sort it in the event more then one task's date is reached (which would most likely occur when you start the application after the due/remind date) and display it in a standard NSAlert. I would've gotten them all done, however I decided to start research on one of the secret features.
Tomorrow (hopefully) I'll finish notifications and get to work on a custom font (O_o) and at least get Boostivity to load it and display characters from it.
This past week (other then breaking down the wall), I’ve been busy getting the todo logic all set up and, of course, playing with Apple’s new big cat, Lion.
I have all the todo logic done. Now I’m working on notifications. Notifications will be the biggest part of this application. I have whiteboarded out a few different ways of doing notifications, and now I’m torn between two different ways. One way involves an NSDrawer subclass, an NSAlert subclass, and a bouncy icon. The other way will be more “disruptive,” but easier to implement. It’s one of those things I may just implement both and have the user decide which one they want.
After notifications there are only two more features left to implement (“secret features”) then make the UI look fantastic and go bug huntin’ then make a website for it and submit it to the App Store.
I hope to get all the features implemented next week, although it might get pushed back to the week after since I’m getting some new toys later in the week (literally toys, not awesome gadgets).
Last week I ran into a wall: I couldn’t figure out a way to do reminder and due date notifications. I had tried numerous ways, and I couldn’t quite do it in a way that was both stable and made sense.
Again, I consulted the Book of Knowledge, and I got an answer that caused a big “DUH” moment. Unfortunately I couldn’t access my code for a few days because I went on a mini vacation (of sorts).
Now I have it working, FULL STEAM AHEAD!
In other news my graphics guy is sending me some pretty rad graphics. Hopefully I can show you guys in a few days.
Today I focused on deleting (which took me a while because of my unfamiliarity with core data) and drawing up/researching all necessary APIs to get todo working fast and efficiently. Tomorrow I hope to begin writing that part, then work on notifications then work on "secret features" and making it look pretty.
I also fixed a huge bug with auto saving, it wasn't saving correctly, whoops!
I also had to consult the book of knowledge because I apparently don't know much about NSIndexSet (which is true), thankfully I got an answer in a few minutes, thanks Paul.s!
