In the last 8 hours the 100th user allowed Twaddle to communicate with Twitter on their behalf. It’s good to see people are finding Twaddle useful.
As my gift on this milestone I present… a screenshot from the 0.2 version of Twaddle.
0.2 Preview – New navigation and @Replies
In this screenshot we can see two new features of 0.2: First of all is the new navigation control. This is a bar of icons displayed along the top of the screen in the same vein as Microsoft’s Facebook application. I’m thinking I’ll move it to the bottom of the screen so there’s less distance for your finger to travel to get to it. Additionally the graphics used here are placeholder images – if anyone wants to volunteer to provide design services for Twaddle I’d love to hear from you. When you change which section of Twaddle you view you’ll get a textual overlay to indicate what you’re now viewing – in this screenshot I’m viewing my @Replies. The second feature, you may have picked up on, is the @Replies. In this view you can see several tweets people have targeted at me (I do apologise to those who are pictured)
Anyway, if you have any feedback, suggestions, criticisms or problems, please let me know and I’ll do my best to address your issues.
hey I’m posting my feedback in tweets #twaddle check for them from @_cave hopefully direct message support will come soon
Thanks for the feedback Daniel.
The geotagging uses Google’s Cell/Mobile tower database so it won’t work if you’re not connected to a phone network. I have noticed that sometimes it won’t perform a lookup correctly… I’ll put some more logging in around this so I can diagnose. Future geotag related changes are: optionally using GPS and working on a way to use less characters for the geotag (Perhaps a geohash – see http://geohash.org)
I’ll make sure that pressing up / down works correctly without having to tap the window first – sorry about that. I generally use finger scrolling.
In regards to memory… I find it typically uses 1400kb (According to Running Programs). It will fluctuate up to about 2300kb when it’s refreshing any data from the twitter services as it has to parse XML. I’ve got plans to try and cut down the parsing memory usage though, so we’ll see how it goes.
Glad you’re liking the application so far though!
My memory footprint never strays to far away from 2900k, here are my settings
Post with geotag check
Refresh 10 mins
Statuses 50
Scale images check
Notification vibrate always popup always even if twaddle is active check
automatically start on reset check
don’t know what else could change the memory usage, but let me know what you’d like me to try.
By the way I am running on a stock ATT Tilt firmware
Windows Mobile Professional
Rom 1.62.502.0
Radio 1.27.14.09
I’ll keep posting thoughts with #twaddle on @_cave.Still loving how good the notifications work, and will definitely keep using this. Thanks for the app.
The 50 statuses will have an impact on memory footprint, but it shouldn’t be *that* big an impact. Can you try dropping the statuses down to 20 and see what the memory footprint is like then? That’ll at least help me target my analysis.
Hi,
thanks for Twaddle, it looks good. I use it for offline tweeting too – yes, i wrote tweet, post it (got error) and when I am online, select ReTweet (do nothing – bug?), then Edit and Post – now is my tweet posting without error.
I have few suggestions / questions:
- do you plan inserting pictures using TwitPic?
- it would be great inserting pictures via internal Camera!
- can you please repair Twaddle icon to higher resolution? (in Program list looks not good)
Thanks and many accomplishments with your app.
Choze
Yup, I’ve noticed that there’s a problem when resending posts that have errored. While on holiday the idea of “offline” tweeting became rather appealing to me, so it’s something I actually want to implement properly (ie. Tick “Send later” or some such, but still be able to geotag, maybe have a date stamp, etc)
Uploading to TwitPic or similar is planned – the problem I’m having is finding one that offers OAuth, otherwise the user will have to enter their username/password *just* for the picture service. When it comes, it will offer taking a photo and uploading that as well as selecting an existing image.
In regards to the program icon… I’d love to, but I’m not a graphics person. If you know someone willing to provide icons for use throughout the application I’d *love* to hear from them.