FREQUENTLY ASKED QUESTIONS
Why don't you publish games on platform X/Y/Z?
Don't get me wrong, I WANT to but unfortunately I'm limited to publishing on products that I own and that reasonable for me to acquire. I publish my games on Google Play purchasing the necessary license to do so is VERY affordable and I already own the necessary tools (including two Android phones, my personal one and a second slower one to make sure it games work on slower devices) to properly work on games for the platform.
To publish on other platforms, I would need to go out of my way to buy them and the required licenses and not many other platforms are as affordable for me at the moment. If my work becomes successful enough to stand on their own, then I will seriously consider biting the cost to increase availability.
To publish on other platforms, I would need to go out of my way to buy them and the required licenses and not many other platforms are as affordable for me at the moment. If my work becomes successful enough to stand on their own, then I will seriously consider biting the cost to increase availability.
Where did you come up with neoxid501/how do you say neoxid501?
Please see About.
How often do you update your games?
Generally as needed. If new bugs or really interesting ideas arise then I try to address them as soon as possible. Certain cases like Garbage Bird and Bagel Bash are far more community driven and therefore I'm more inclined to provide regular content updates for those. Other reasons for keeping a game updated include (but is not limited to): an active player base, compatibility issues, and my personal interest.
Why do some of your application package names include "neoxid" instead of "neoxid501?
When I first starting making applications for the Google Play store, I wasn't really sure if there were any standard naming conventions for all of the items, sort of how class names are considered proper or how variables are generally camel cased (myVariable instead of myvariable).
It turns out the naming convention for packages is generally the relevant website domain backwards so in my case they should all be "com.neoxid501.appname" instead of "com.neoxid.appname". This convention exists purely to prevent overlap and I recall actually using neoxid501 before but I didn't think it was proper to have numbers in the package name (now I see how silly that is). Applications made after Bagel Bash's release (07/05/2017) will use neoxid501 in its package name to avoid any further conflict!
It turns out the naming convention for packages is generally the relevant website domain backwards so in my case they should all be "com.neoxid501.appname" instead of "com.neoxid.appname". This convention exists purely to prevent overlap and I recall actually using neoxid501 before but I didn't think it was proper to have numbers in the package name (now I see how silly that is). Applications made after Bagel Bash's release (07/05/2017) will use neoxid501 in its package name to avoid any further conflict!