[Windows Mobile Apps and Games] thesecondsfade:
2.0 Beta 2

Here are my preliminary testing results for GV EasySMS 2.0 beta 2. I know I'm supposed to just be working it testing for bugs and such but I'll put my commentary related to features, usability, etc. as well.

Outgoing messages are sending without the error from earlier this week.

Hitting "Reply" directly from the notification is nice.

"Exit Compose Mode After Sending" wording in settings makes more sense for what it actually does.

It doesn't show the "Message(s) Sent" confirmation when 'Exit Compose Mode After Sending' is checked. It reverts to the original message, then exits to the inbox. It should still show the "Message(s) Sent" text while it's exiting just so the user doesn't get confused about whether or not it went through. I guess you could just assume that it went through if it kicks you back to the inbox but there's just no way to confirm that visually.

While in standby, it successfully wakes the device up on the correct interval, does the update, and then puts it back into standby.

While ithe device is already awake, it runs the update on the correct interval, does the update, and leaves it alive as it should.

With backlight off but not blank screen, it brightens the display to full brightness (on the correct interval), does the update, but does not turn the backlight back off after the update. Not a big deal just something I noticed.

I had an EasySMS notification up, did not dismiss it, and when it updated again, it forced EasySMS to the front and did not auto-dismiss the message. It should probably auto dismiss any pending EasySMS messages if you ever bring it to the front just to avoid confusion.

I was attempting to send a message and the auto-update initiated at the same time, then after about 90 seconds of just hanging, seemingly frozen, I got a "Communication error".

Failed sent message reverts back to original message text so that's fixed.

Sent items are

not

showing up as notifications, so that's fixed.

Battery life went down by 12% in 20 minutes with a 1 minute update interval. Obviously I wouldn't use a 1 minute interval in a real-life situation but I thought I'd mention the drain in case there's something you can learn from that.

While S2U2 is running, the notification does not show up and is dismissed after sliding to unlock but Easy SMS shows up in the foreground. I suppose that's fine since you can see that there is a new message even though there's no Windows notification.

After not getting notification while S2U2 was running (in the previous bullet), I didn't get any more notifications. After a while I did though... weird.

It's showing my response from 30 seconds ago as "9 minutes ago" in the thread view. It's because the conversation was started 9 minutes ago. If possible, it'd be nice to see when the last message was sent or recieved, not when the conversation was started.

Inbox update should happen right after message sent, not at the next auto-update interval. It seemed to update right away a couple times but then a few times it seemed to only update at the regular update interval. Not sure how it's written to work but it was just a bit confusing and I wasn't sure how it was supposed to work.

I gotta go back to work. Hope this helps. As far as I'm concerned, it's great as a release candidate. No bugs other than those few minor things which are more just feature updates than actual bugs. For using it as only an outgoing service, it's flawless. Keep up the great work!