As mentioned a couple of weeks ago I have discontinued Twaddle for Windows Mobile in favour of working on Twaddle for Windows Phone 7. Without further ado, I present a series of screenshots of the new Twaddle;
As mentioned a couple of weeks ago I have discontinued Twaddle for Windows Mobile in favour of working on Twaddle for Windows Phone 7. Without further ado, I present a series of screenshots of the new Twaddle;
I think it’s probably pretty obvious, but thought I’d post an “official” update: I will no longer be developing Twaddle for Windows Mobile.
But it’s not all bad news: I have already begun “porting” Twaddle to Windows Phone 7. The good news is that both WP7 and Windows Mobile have .Net at their core and Twaddle was written in such a way to separate the UI from the logic. As such I’ve made good progress on porting Twaddle. Additionally, it’s the UI of Twaddle that was always pretty poor (in my opinion), and the new controls in WP7 have so far made the UI a breeze.
I don’t have any screenshots suitable for public consumption at the moment but shall post some shortly.
If you have any major issues with Twaddle for Windows Mobile, let me know, and I’ll see if I can release an update, but I won’t be actively updating it.
Good news everybody: I’ve just finished the final item on my TODO list for the 0.3 release. This means that all existing bugs have been fixed and all new features have been implemented. I’ve just put the first 0.3 release candidate build onto my phone and I’ll be keeping a close eye on it throughout the week. If there’s no major problems 0.3 should be released next weekend.
Thanks for waiting!
A few weekends back I finished implementing OAuth Echo support in Twaddle. This is the new, secure, way for you to use a third party site which communicates with Twitter for you. The classic example of this is photo sharing services such as TwitPic. Previously such services requires you to send them your username / password which isn’t a good idea. Using OAuth Echo you send them an opaque bit of data that uniquely (and securely) identifies the request as coming from you – the third party site then “echos” this data to Twitter to use for authentication.
OAuth Echo support – in conjunction with the new extensible architecture of Twaddle – means that over the course of a few hours I was able to provide TwitPic support within Twaddle. This support allows you to take a new picture with your phone’s camera (for devices with cameras) or to use an existing photo, both with preview support.
Yesterday the Twitter API team granted Twaddle access to the (newish) XAuth interface. What does that mean? Well it means that one of the biggest criticisms of Twaddle is gone. You’ll recall in previous versions to set up a new account you had to hit “Start” which would launch your browser. You’d then login to the Twitter website which would give you a 7 digit number. That number would need to be remembered and entered back into Twaddle. This process, which is relatively painless on a desktop or web application, was incredibly frustrating on a mobile device. XAuth is designed specifically to address this issue. I think the following screen shots of the new account setup process explain better than I could…
“But isn’t this going back to username / password combinations which is insecure?” you may ask. Well, no, not really. The username / password combination is sent over a secure channel only once (at the time you fill out this form). Twitter verifies this and then sends back a token which is used for all subsequent requests. This is in fact identical to the OAuth process used in earlier versions the difference is how that token is acquired.
All you really need to know is that signing up with Twaddle is now pain free! Hooray!
I do apologise for the delay on releasing the newest version of Twaddle. I guess this is a problem when you use free software developed by someone in their spare time, huh?
A couple of things have caused the delay of the latest version: Firstly my Real Job™ I was the Technical Lead on a very large project (since released successfully) which took up a lot of my time and motivation. I have also handed in my resignation and am currently looking for a new job. The upside of this is I’ll be taking a few weeks off before starting a new job. Time which I plan to devote to playing video games / coding Twaddle.
Secondly the announcement of Windows Phone 7, and what it means for developers of Windows Mobile apps, was a bit disheartening.
Thirdly: I’ve worked on a lot of the internals of Twaddle. This working means that third party developers will be able to write plugins for Twaddle. Don’t like the way it does notifications? Write your own! Want Twaddle to automatically hash tag things? Write a plugin! And so on, and so forth. This affects every aspect of Twaddle (The User Interface, background tasks, response to other events, etc) and required a fair amount of thought and tweaking. It also turned out to be a much bigger task than I’d initially anticipated. As to if any third party developers start writing plugins for Twaddle remains to be seen. But even if they don’t it will allow much quicker development of features for Twaddle, providing they fit within the existing model. I’ll release more technical details of this closer to the release date of 0.3 / if people are interested.
In the mean time, I apologise for the delay, but hope the delay will result in something everyone is really excited by.
So today I just checked the statistics for Twaddle and there are over 2000 users who have allowed Twaddle to communicate with the Twitter servers. Whilst I’d love for this number to be 10,000 and for each of those users to be paying me a fiver, I’m still rather happy with these figures. In order to celebrate this nice little milestone I thought I’d present you with a recent feature I implemented as part of the 0.3 release: Threaded Conversations.
Here we can see a conversation I held between my personal account and the @TwaddleWM account. You may notice a very subtle tree structure of the list – this is to indicate the hierarchy of the conversation. This view only works when statuses are properly tagged as replies to another status (which Twaddle and the Twitter website do, but some clients seem to do less reliably). I’m so far finding this feature really useful to manage long running conversations throughout the day (and you can sometimes find some great new people to follow as a result!). This interface can be brought up from any of the other views within Twaddle and allows you to interact with the tweets just like they were in your normal timeline. Expect the interface and how this is rendered to change before the final 0.3 release – this is after all just a preview! If you have any suggestions on improving the layout, I’d love to hear them.
Also, don’t forget to take part in the poll on the right hand side – it’s a great way for you to voice your views on what feature you desperately want included in 0.3 !
It’s been a long time coming, but I’m excited to announce that Twaddle 0.2 is nearly here. I now consider 0.2 to be feature complete and am now going through the process of final testing before I release it. I’m hoping to have 0.2 released in time for Christmas (if only so I can lounge about and play computer games instead of coding), but can’t promise anything.
A partial list of features, to whet your appetite, include;
I’d hoped to have a 0.2 of Twaddle out by now, unfortunately that’s not been the case.
First off, I recently moved house which took a fair amount of time and effort to get packed / unpacked and have DSL connected at my new place. In addition to this I’ve had a few Uni assignments which took away even more time. In amongst all this my computer chair broke… I’ve purchased a new chair which won’t arrive for another 4 – 8 weeks. The dining chair I’m using in the mean time places a lot of strain on my back meaning I can only code for short periods of time.
Secondly, I’ve put a lot of work into making Twaddle a lot faster. On my HTC Touch Pro rotating the screen redraws virtually straight away and Twaddle continues to be responsive throughout the whole process. A vastly improved algorithm for laying out tweets (50 tweets get laid out in ~150ms on my phone) as well as moving non-visible layouts to a background process ensures Twaddle remains responsive throughout rotations. I’m still working on improving the speed of performing updates.
Long story short: 0.2 won’t be released as soon as I’d hoped as I’m putting a lot of work into it to ensure it far eclipses previous versions of Twaddle.
CJ Lippstreu over at PocketNow.com has features Twaddle. You can read the article over at the site. PocketNow being rather popular caused a bit of a surge in the number of downloads, followers and authentications for Twaddle.
As a result we now have over 300 users! Unfortunately, due to my recent house move (and lack of broadband) I don’t have any updated pictures to post as a “Thanks guys!”