Alpha Release FAQ

If I'm only going to try JournalBetter once, is this the right time?

No!

As software consumers, we live by the same rule you probably live by - we only try a new application once. If it's a dog, we never go back. Life is too short to mess with crappy software.

If you live by this rule, don't try Journal Better yet. It's not good enough for real users. This release is for die-hards who enjoy helping us prioritize our next fixes and features.

Why are we releasing JournalBettter before it's ready?

We need lots and lots and lots of feedback. It's a big win for us to get some eyeballs on our work.

We've been working on the design of this app for several years part time, and the implementation for over a year. We are putting this out, even if our design is only maybe 20% visible, and even this is not yet fully functional.

When will it be out of (alpha, beta) state?

Not until operational to come out of Alpha, and not until it's relatively bug-free to come out of Beta. Don't hold your breath - developing good software is not a quick process, and our team is microscopic.

If not ready, will this alpha version of JournalBetter hurt my computer in it's current form?

Other than taking up space on the hard drive like any application, no. It might waste some of your time though.

When will critical features like Cross Platform Releases and Undo Redo and Browser-Based Releases be added?

We invested a lot of time in 2010 and 2011 implementing these features at the architectural level, without adding them to the final user interface release. That's a fancy way of saying "Hey, we'll get to it."

Our plan is to complete these implementations after we get more critical features solid at the alpha release level, such as proper pagination, drag and drop, and other critical display and usage issues.