It is currently Tue Apr 25, 2017 10:22 pm Advanced search
What is the reason TouchControl target Nexus devices? Is it because they are easier to program? Author deliberate choice? Or simply because they don't have a home button so TC is more useful?
I suppose owner of other devices would like to have TC working on their phone too.
Just curious, thanks for any info.
Rex wrote:Oh wow, thank you for sharing the story which is quite straightforward actually. But pardon me for a silly question. So programming TouchControl is something you must have access to the hardware physically? For testing or is it because each hardware require a different module for TC? Let's say for an app like a game or music player, I suppose it's high level enough so the developer could test on one device and is almost certain it will work on other devices.
What if a user having a smartphone of a brand that you didn't test yet. Is there a possible chance that TC will work (like the music player app in the example above) or would this fail 100%? Because if you need to validate it for each model of smartphone individually, I am afraid your app will not cover a big market share in the play store.
Rex wrote:You could be a rich man if you can sell the idea of TouchControl to Google. Does Google people know such a cool thing is possible? This must be implemented natively in Android!
You must somehow get help to patent this idea. If ever Apple is aware of this. They will patent it and you will be screwed! Imagine iPhone users have this on their phones? They will all run nake down the street and screaming that's the greatest feature in the universe.
Users browsing this forum: No registered users and 1 guest