We've Moved

THIS BLOG HAS MOVED!

It can be found at the new website: http://fifteen15studios.com/blog/

Personal Blog

Want to know more about the man behind the programs? Check out my personal blog: http://havens1515.blogspot.com

Tuesday, October 16, 2012

Auto Respond 0.9

I was doing some thinking yesterday about the fact that I had a lot of duplicated code. So I did some looking around as to how I could get rid of it, and have 1 instance of all of the duplicate code that I had.

I've said before that this is my first Android project, and it is also my first major Java project. I took a class in Java in college, but it was my first ever programming class so a lot of the information presented to me in the class didn't really sink in.

I read up yesterday on static variables and static methods, and I used that to get rid of A LOT of duplicate code in my app. Streamlining this code seems to have made navigation a little smoother from one screen to the next.

While doing this, I also changed a few things. My settings menu was starting to get cluttered, and is just going to get even more cluttered as time goes on, so I separated it into multiple menus. There is now "Do Not Respond List", "Dock Options", and "Phone Options", and a couple loose end options that remain on the main settings screen.

I also implemented an option in my SMS to GPlus app to have the permanent notification be optional. I added this into Auto Respond as an option in the settings menu. (Which is actually what led to all of the code re-arranging and consolidation.) This option is on by default, but can easily be turned off.


As I was doing this, I also realized that if Auto Respond is enabled and you reboot or turn your phone off, it may not be re-enabled on boot. That is no longer the case. Also, the dock listener may not have been active on boot in previous versions. Which means that when you dock your phone, Auto Respond wouldn't automatically turn on unless you had opened the Auto Respond app after the phone turned on. That service is now started on boot, if the dock options are enabled.

And lastly, TapForTap (the new ad network that I am using in the free version) just updated their SDK and changed the way their service works. I included the new SDK in the new version of Auto Respond Free. Part of this change is that the ads from TapForTap are now single ads, instead of putting 2 apps in 1 banner sized ad. You should, however, see a mix of ads from TapForTap and ads from admob.

I noticed when I initially implemented TapForTap that the ads didn't display on devices running anything prior to Android 4.0. I'm hoping that this is fixed with the new SDK but I haven't tested it on my Droid 2, which is the only device I own which has anything prior to 4.0. (and unfortunately, the ads don't seem to show AT ALL on emulated devices. Even with 4.0 or 4.1) If it's not working properly, I guess those of you running 2.2 or 2.3.x can enjoy ad free Auto Respond for a while until I get the ads fixed.


Full change log for version 0.9:

• Start services and show notification (if enabled) on reboot
• Re-arranged settings menu
• Made permanent notification optional
• Cleaned up A LOT of unnecessary code (Seems to have improved performance as well)
(Free Version Only)
• integrated updated TapForTap SDK


Both the free and paid versions 0.9 are live in the Google Play Store right now.

Free:
https://play.google.com/store/apps/details?id=com.havens1515.autorespondfree

Paid:
https://play.google.com/store/apps/details?id=com.havens1515.autorespond