After nearly a year of having Sylence in the Android Market and only two sales (ironically, one to myself and one to a relative), I’ve given up on making money on Sylence as a product for sale. I’ve made it free of charge so anyone can download a copy; and so far, a few people have done so. When I last checked, more than 40 new people tried the application, and I don’t think I have it opened fully to the world at this time. So what does this mean? It means that when I have some spare time, I’m going to add a few new features, fix a few issues that I’ve wanted to correct for a while, and possibly add advertising to it because I’m certainly not making any money with it the way it currently is.
I’m sorry to say that I’m pulling the plug on Gas Up, primarily due to lack of interest. At the moment, according to the Android Market Developer/Publisher Dashboard, I have about 280 installs of the application out there, but I only get the occasional price submission from any one. In addition, since I launched the application a year ago, a number of other apps with similar functionality have sprung up, all of which seem to be more popular than my little one. I thank those of you who gave it a try, but with my limited time and lack of interest, I don’t see any point in pushing on with Gas Up.
This project did teach me a lot, and I’ve managed to gather a lot of experience working on Gas Up, Sylence, and other unreleased projects. Hopefully the knowledge gained will aid me in a future project.
For those of you that still have the app installed and use it, the app will continue to function normally, but I wouldn’t hold my breath for any updates. (Unless you really, really urge me to do so. 😉 )
I just released a slightly newer version of Beta 5 that fixes 2 bugs: the most important issue resolved is that posting prices over 3G/Edge wasn’t working for some strange reason, though I didn’t change that code between releases at all. So I switched to a different method of communicating with the server and it seems to be working well again now. The other issue resolved is one that I had hoped would be in the initial Beta 5 release: you may now double tap on a location in the map to enter a gas price at that location. I’m still not 100% sure why this wasn’t working on Android 2.x but was on 1.6, though it may have to do with code obfuscation that is now being done. Whatever the cause, it’s fixed now.
Over the last week, despite my other obligations, I’ve been a bit busy with my published Android applications. Among other things, I fixed a few annoying bugs in Sylence culminating in a series of releases last week, and today I published the long awaited update to Gas Up.
I am disappointed in this release, beta 5, of Gas Up however. A feature I spent a fair amount of time figuring out seems to be working on only one of my three Android devices. That feature is the ability to double tap on the map and enter a gas price/station at that location. It works properly on my G1 running Android 1.6, but is missing from my Huawei Ascend (Android 2.1) and Nexus One (Android 2.3.3). I’m not going to dig around and fix this issue at this point; instead I’m going to do a complete rewrite of Gas Up because I have learned a significant amount about Android since I started development on Gas Up nearly a year ago. I’m sure it will be quite some time before I complete the next iteration, but I’m even more sure it will be better than ever.
Ok, since I have financial needs that aren’t currently being met and I want and need experience, I’m making myself available as a freelance screenwriter. I’m not limiting myself to any particular genre, topic, or anything else and I’m willing to either do scripts solo or collaborate. If interested, please contact me via my An Evil Genius web site.
Although I’m a couple weeks behind on this, I thought I’d note that I fixed the cookie parsing in the HTTP add-on in Themis, and cookie handling is probably working better than ever at the moment. This isn’t to say I’m done with it; I need to go back in and fix a few curious issues with non-standard dates, empty cookie values, and restricting the maximum length of both a cookie name and value, but I can say that it’s significantly better than it was. I’m also considering moving the cookie system into a plug-in of its own; which it originally was.
In addition, I’m now faced with adding configuration options for the cookie system, and it would be easier to manipulate those settings in the preferences window if the cookie system was in its own separate plug-in. This isn’t going to happen tomorrow, so don’t worry about it right now, but this is going to be a change in the future.
As of now, Sylence is available in the Android Market in the United States, Canada, and the United Kingdom for $1.00 U.S.. There are still somethings that need to be worked on, but I wanted to get a functional version out and about tonight. Go buy it and enjoy!
As of Tuesday afternoon, Sylence is feature complete though I sill have a bug or two to squash, and other details to implement. The gist of the application is that it allows you to set “silence alarms” so that your phone’s ringer will automatically be turned off at scheduled or recurring times.
I’ve decided to sell the app for $1.00 (US) in the Android Market, but I don’t yet have a target date for that. The word is “soon” though. I’m considering doing an ad supported version but I guess it depends on the demand.
As of today, this semester is over for me and I am already working hard again. While I haven’t touched Gas Up today, I have started on another project I’ve been meaning to do for a while now. This new project is called Sylence and is fairly simple and straight-forward: it is a scheduler for silencing your phone. For more than a year, I had been using FoxyRing to silence my phone as needed, taking advantage of the widget that would let me silence my phone for up to 5 hours at a time, but I found that I would occasionally forget to use it before I entered a class. So, I did the logical thing, and wrote the author(s) to ask them to add a scheduling feature. Let’s just say I got a negative response, and I’m still not sure why.
So, for months I mulled over the idea of writing my own, but didn’t do anything about it. Tonight, after watching the FoxyRing service crash yet again for no apparent reason, I uninstalled the app, and vowed to do something about it. Since I just finished my finals today, I got started on the app. At this point, I don’t know if I’ll make it free or attach a low price (I’m figuring around $1.00), but I’ll be putting it in the Android Market as soon as I deem it done, or at least done enough to use. Eventually I think I’ll add a widget similar to what FoxyRing offered, but right now I’m not sure how far I’ll push this new little app.
On the Gas Up front, I will be doing some heavy coding on it in the next week, and I’m going to try to get Beta 5 out and about by the end of next week.
I just want to give a quick status update on Gas Up Beta 5, so here we go:
As of about 5 minutes ago, double tapping on a location on the map will switch to the “Submit Price” tab, and attempt to look up the address of the tapped location. This is not fool proof, and it’s not guaranteed to get an address ever, let alone on the first try, simply because of network congestion, server latency, or even if Google simply doesn’t have an address for the tapped location. But, when it does work, it gives you the ability to submit gas prices at locations other than where you currently are. For best results, zoom in as closely as possible before double tapping.
The code to prevent double accidental duplicate price submissions caused by network lag is mostly done in the application. I still have a few loose ends to tie up in the app, and to handle on the server side of things, but so far so good.
I’m now considering downloading all current gas prices for the selected fuel type at once rather than doing it based on the viewable area in the map at designated intervals. Although I’m not too concerned about network traffic on the server side of things, the repeated querying, several times a minute, from all running clients can slow down overall performance for everyone, not to mention it could affect your bill if you don’t have an unlimited data package. What I will probably do is switch it to download all the price submissions once every 15 minutes for the selected fuel type, and if the app hasn’t checked in the last 15 minutes on start-up or when the fuel type is changed, to download updates immediately.
[ad code=2 align=center]
Also under consideration, though not deeply yet, is the possibility of adding some kind of excitement to the app. I don’t know how many of you have even heard of it, but there’s a social mapping/gps app called Waze. It makes using the app at least somewhat fun by giving subscribed users points for exploring previously unexplored or not recently explored streets, and it maintains a leaderboard on a state by state and national basis. Perhaps something similar can be added to Gas Up with a little effort, but that would mean that I’d have to add account information, which in turn means that when a gas price is submitted, I’ll be associating that account with a location. Not to mention storing that location and user information. I’m a bit reluctant to do that, but I would appreciate getting some feedback from my user community on the issue. (Assuming there is a user community for Gas Up… 😉 )
November 30, 2010 8:27 pm
Just wanted to make an addendum. As of a few minutes ago, double tapping ton the location of a gas station already in the database will automatically load that gas station’s name, address, and coordinates (latitude/longitude) in addition to switching to the Submit tab. I’ll be applying the same thing for when you switch to the Submit tab normally as well. If the gas station isn’t in the database, you’ll still need to enter the information as before.
Also, I’m in the process of changing how the data is transferred to your device. When building or rebuilding the database, it [Beta 5] will now download all gas stations currently in the database, though I’ll probably change that to be all within the country that you’re currently located in. Yes, I’m considering opening this up to more countries now, but initially I’ll probably only expand the beta to Canada.
As a further note, I just updated the server side code to handle some of the new changes, and everything still seems to be working. Please let me know if something isn’t…