Android, Auto Respond

Auto Respond 1.2.7.1 – ICS crash fix

Sorry guys, there was a function that I thought was introduced in 4.0, and apparently it was introduced in 4.1…. long story short, if you’re running Android 4.0.x then Auto Respond 1.2.7 may crash on opening. (Android 2.x should be fine, 4.1.x and 4.2.x should also be fine)

1.2.7.1 fixes this, I accurately changed the cutoff for that function’s usage from 4.0 to 4.1.

1.2.7.1 was JUST published, so it may be a while before it is live. If you haven’t updated to 1.2.7 yet, you may want to wait until 1.2.7.1 is live on Google’s servers. Sorry for the mixup :-\

Android, Auto Respond

Auto Respond 1.2.7

Auto Respond 1.2.7 has been published, and should be available right now on the Play Store. The only difference is the tutorial.

Let me know what you think about the tutorial, and if there is anything that needs to be changed/fixed. (I saw a few small issues, but the things I noticed were small aesthetic issues, not performance issues)

Android, Auto Respond

Auto Respond Tutorial

The last couple days I have been working on a tutorial for Auto Respond. This tutorial will display the first time Auto Respond is opened, then will not show again. It is an overlay on top of the main screen.

There is also a new option in the settings menu to force the tutorial to show again. But even when that is turned on the tutorial will show once, then it will not show again unless you again enter the settings and turn on that option.

I have tested the tutorial on Android 4.2 and 2.3, and it seems to work well on both.  The only thing I have not done yet is built it into the free version, which includes ads. I may have to find a way to wait until after the tutorial ends to load the ads. This may be easy, I just haven’t tried yet.
Here is a screenshot of the first part of the tutorial:
As you can see here, the tutorial disables the entire interface, except the OK button at the bottom, and highlights the specific piece that it is referring to. This shows the user EXACTLY how and where to interact with the app, and how the app works.
I hope to release this update later today. The sooner the better, because it will help new users understand how to use the app.
Android, Auto Respond

Auto Respond 1.2.6 and beyond

I just published Auto Respond 1.2.6.

Not a whole lot of changes in this version, but I think they are important changes:

  • Finished standardizing the look and feel throughout the app
    • Settings screens now have “OK” and/or “Cancel” buttons in them
Also, I went out and got myself a Nexus 10 on Christmas eve (for those of you who are wondering,  I found it at Walmart. Same prices as on the Play Store.)
I know it’s not really an app for tablets, but I have confirmed that Auto Respond DOES open properly, turns on properly, etc. on a tablet. I know there are apps out there that allow you to send and receive SMS messages on a tablet (such as DeskSMS) but I have not yet tested it with such apps. I’m not sure if the app actually PERFORMS properly on a tablet with such apps, but I have confirmed that it at least opens and it looks OK on a tablet. (No FC’s or glaring bugs that I found. The new settings look caused some FC’s on the tablet, but I fixed them.)
I do plan on making sure that it is compatible with apps such as DeskSMS at some point, and giving it a tablet UI, but I’m not sure exactly when that will happen. (I’m sure not too many people will be using this app with a tablet, so it’s not on the top of my to-do list… unless some of you let me know that you will actually use that functionality.)
As I’ve said before – this is my first Android App, so I’m kind of learning as I go. With the tablet implementation it will be another learning experience.
I did get a request over the weekend, so I will be thinking about how to implement that. The request is the ability to send a specific response to specific contacts, or contacts that follow a certain pattern. (In the case of the individual request, anything that contains @theRequestedDomain.com) I have received similar requests in the past, so this is something I am going to make a priority.
I’m not exactly sure how to implement this, or how to properly test it, but I have some ideas to get me started.
As usual, I just published this release. It may be an hour or 2 before it’s live on Google’s servers. And if you find any bugs or feature requests, let me know.
Lastly, I hope everyone had a safe and enjoyable holiday, no matter what you celebrate. I hope you all got the gifts you were hoping for, and I wish you all the best in the upcoming new year!

Android, Auto Respond

More Polishing

I just spent a few minutes polishing up my layouts.

  1. layouts which have a list view in them (such as the “Preset Messages” screen) previously have no separator between the list view and the button(s) at the bottom of the screen (On Android 4.0+, no separator is needed on 2.x). This was because the way that I had it set up, that separator would end up on top of one of the list items if the list was long enough. I found a way to fix that, so now ALL buttons on the bottom of the screen have separators.
  2. I found an easy way to add Cancel and OK buttons to my settings screens. Unfortunately, this is not a simple add the buttons to the view and I’m done. I need to now go through all of the settings screens and make the cancel button return the settings to their previous values. This is not hard, it is just time consuming. (And considering I don’t have a whole lot of time to program this weekend, it won’t be done immediately… likely early to mid next week.)
  3. I added a Cancel button to the bottom of both the Credits and the Help screens.
  4. I added a separator above the buttons on the purchase dialog, when clicking on “New Schedule” in the free version of the app. (Again on Android 4.0+)
  5. The “Do Not Respond” contact picker screen looks exactly like the “Preset Messages” screen. The Sort button is not enabled right now, as I have not worked on sorting the list of contacts yet. I’ll probably work on that early next week as well. (Unfortunately, sorting is not my strong point. But now that I have schedules sorting properly, I should be able to reuse the same code, with some minor changes, for the contact list.)
I think that’s about it. I’m pretty sure that all of the changes I’ve made so far are purely aesthetic, so I won’t be releasing an update today. When I finish the functionality of the buttons at the bottom of the settings screens, I will release the update which includes all of the above mentioned enhancements. 
Once this update is released, navigation throughout the app will be VERY consistent. At the bottom of each screen will be a Cancel and/or OK button, which will take you back to a previous screen, and any actions above those buttons will take you forward to a new screen.
The only screen which will not have such buttons is the main screen, with the tabbed view. This is for 2 reasons:
  1. The scheduler screen is already cramped, and adding more buttons will only make it worse
  2. This means that the user has to hit the Back or Home button on their phone to exit the app.This is consistent with the Android design guidelines, and I think is more intuitive for the user.
Android, Auto Respond

Do Not Respond Window (And happy holidays)

I realized the other day that there was yet another neglected window when I did my redesign… the “Do Not Respond” window.

Part of the reason why I forgot it is because it’s buried in the settings, and I cannot apply quite the same design to the settings window (or at least not easily… maybe I’ll look into that as a possibility.)

So I just spent a few minutes reworking that window as well. It was a quick and painless transition, but it isn’t really enough of a change to need a new release (especially since I just put out an update this morning) so I’m going to sit on it for a while, and it will be included in my next release.

Since I just mentioned it (and literally just thought of it as I was writing it) I will look into the possibility of adding a cancel and OK button to the bottom of the settings screens, to keep that constant with the rest of the app, but I’m not sure if that’s easily done. I may have to literally rewrite ALL of the code for those screens in order to make that possible, instead of just rewriting the layout and a small bit of logical code. If that’s the case, it will not be done. But if there is a way for me to easily add buttons to a settings screen, I’m sure I’ll find it.

Until next update, let me know if there are any feature requests or lingering bugs. Otherwise, you probably won’t hear from me for a week or so. I have family in town this weekend, and will likely be spending the next few days with them instead of my computer.

Happy holidays everyone! I hope you all get all of the presents that you asked for and, as always, stay safe!

Android, Auto Respond

Auto Respond 1.2.5

I just published an update to Auto Respond. Not much in the way of changes, but I may have potentially finally killed a big bug.

People have been emailing me, saying that sometimes my app doesn’t send a response. Some people have sent crash reports when it has happened, all of the crash reports pointed to a “null pointer exception”, but I couldn’t figure out where exactly it was happening. (Even with all of the information provided in the error reports.)

Today I was going through my code, block by block, and commenting it thoroughly, in case there comes a time when I put this away for a while and return to it months later. While I was doing this, I finally realized where this error is possibly being generated. (And possibly fixed some other errors in the process.)

That being said, here’s the change log:

  • More work towards supporting multiple languages
  • Some small bug fixes
    • Hopefully a fix for the people who have had occasional issues with it not sending a response (I’ve been looking to squish this bug for a while now!)
    • Small logic changes to fix things that you probably didn’t notice
I usually do this occasionally with all of my programs… go through them line by line, or block by block, and see what I have overlooked. Usually I do find something small that can be changed or improved somehow. This time I potentially found, and fixed, a big bug.
If you DO run into an issue where the app doesn’t seem to be sending responses correctly (or any other bugs for that matter,) please let me know via email, Google+, Twitter, whatever.
As usual, I JUST published this update, so it may be a couple hours before it’s live on the Play Store.

Android, Auto Respond, Google Analytics

Google Analytics

Yesterday I started playing around with Google Analytics, and figuring out how to build it into Auto Respond.

The versions that are out now do not include Google Analytics in any manner, but I am looking into possibly building it into future versions. That would mean that the paid app would once again need internet permission in order to send the data back to Google, but this would be the ONLY information sent and there would be no personal information transmitted.

For those who aren’t aware, Google Analytics helps developers understand how users are interacting with their products. It will tell me how many times specific screens are viewed, how many active users I have, and potentially which buttons and other elements are interacted with most often.

This information can help me understand how you, as users, interact with my app. It can tell me which things you use often, which things you never really use, whether you tend to click buttons more than list views, and possibly even what settings are used most often.

I’m not sure of the exact information I can get, as I have just started playing with it, but rest assured that I will NOT be able to see that John Smith opened the app x times, or click this button, or has these settings set. I simply get a report for ALL of my users and cannot tell the difference between interactions from one user to the other. (I do not need, or care about, statistics on a per user basis in order to get useful information.)

I can then use this information to improve the parts of the app that are used most often. If people tend to use the scheduler a lot, I can spend some extra time with new features to give you more of what you want. Or if people use the preset messages a lot, maybe I can add more information to the list view, or create new sorting options, etc.

Or, on the other hand, if people tend to not click on my list views, I can make it more obvious to the user that clicking on the object will cause some action.

Overall I’m very excited to see what I can do with this tool! And once it’s set up I think it can greatly help me improve interactions in my app. The ONLY downfall is that the paid version will require permission to access the internet, which I think is a small price to pay for an improved app.

Let me know your thoughts, and if you have any experience with Google Analytics, feel free to let me know how it worked out for you!

TL;DR – Google Analytics will potentially help me understand how my users use my app, and help me improve the user experience.

Android, Auto Respond

Auto Respond 1.2.4.3

I just released a new Auto Respond, this is only for paid users. The only difference is a new sorting option for schedules.

Unfortunately, I was in the middle of working on this when I released 1.2.4.2, and included the incomplete code in that version, so I decided to finish this ASAP as to minimize problems. There will be even more sorting options in the future.

If you are using the paid version of 1.2.4.2 DO NOT sort your schedules until you update to 1.2.4.3. If you do sort them prior to updating you’ll likely end up with duplicate schedules, or missing schedules, and you’ll end up needing to delete them all and recreate them.

The new version was just published, and should be publicly available in an hour or 2.