Status Update
Fortunately, I am almost finished with the major portion of my work (as you know, I primarily oversee the UI stuff) for future versions of Pixelmator – 1.6, 1.7, 2.0. Therefore, I think that I will be able to be in touch with you more often. We (me and you guys, that is) must live through the period when Aidas and other Pixelmator development staff (I promise to introduce them to you sometime) will completely finish version 1.6, code named “Nucleus.” Everyone here is very hard at work and cannot wait to introduce you to the latest and greatest Pixelmator.
As for Pixelmator 1.6 Nucleus, although I would love to offer you more details about its features, it is too early for me to do so. Some features may be delayed for later, and some may be added in the development process (even though our development plan is very strict, some changes still find their way in or out). We want to be sure that we ship everything we promise—a goal that we always strive to attain.
But one thing that I can tell you about Nucleus is that it is mostly about the Pixelmator foundation and basic tools. The pleasant thing is that the major part of Nucleus improvements will serve as an effective basis for 2.0. Remember, we promised that Pixelmator 2.0 will ship with a rock-solid foundation and we aim to deliver on this pledge – we just need some time.
Since Aidas is very busy at the moment and I am tasked with letting you know about the happenings at the Pixelmator Team command post, I think it is OK for me to take over the Pixelmator Team’s Twitter account (yes, it does exist). So from now on (dunno, maybe just temporarily), I will babble for you on Twitter – follow me!
Pixelmator took the lead right out of the gate and never looked back. With a final tally of 56% of the votes cast, Pixelmator was the leader from start to finish.