Thinking about it a little more myself I see one of the main concerns. The fact that this is some sort of kill switch, it may invoke a fairly dangerous situation. If it`s implemented as a remote control, you could accidentally engage the kill switch while driving yourself on the freeway. Perhaps a safer method would be to just force an ignition kill after leaving turning off the engine but this is probably the same as any other built in car alarm. I did something similar to this before car alarms were popular. I just installed an electrical switch in-line with the starter wire from the ignition key switch. It was some obscure looking thing that was hidden behind the bottom part of the dashboard. Another thing to consider is that many new cars today already use RFID technology for keyless entry and ignition. This requires that an authorized keyfob be physically nearby before the car door can be opened and the car started. Perhaps then, it might be better to target the law enforcement angle like you have mentioned.
I feel your pain. I spent many hours, days, weeks developing a web application that was and still is novel. I did this as a side activity to working contracts and full time jobs. The problem I have is my app is data intensive and requires alliances with other companies and organizations to get access to this data.
Are you able to cover your life expenses with another job or will this be an all or nothing adventure?
I`ll throw in my 2 cents:
*Should i build the app myself after learning the language,and hire programmers later for maintenance and maybe fixing bugs? (comments below)
*Do i get a "innovation patent" (quicker approval process here in
australia for that kind of patent) for the web app? OR is not patenting
better at protecting the code? How should i protect this kind of
idea,if i do outsource programming?(apart from confidentiality
agreements)I really don`t know how well patents really work on software. If it`s a web app and the complexity is such that it`s not easily copied, maybe it`s ok . It`s not like software that you download onto your PC (that is easily copied/duplicated). If you can manage to keep the proprietary IP hidden inside your app, you should be able to protect yourself. I think the most important thing is to get your app going and get a head start on any competition.
*Is it necessary to start a company in order to launch a web app? or can i just start the web app myself? Whats more successful?I don`t think it`s completely necessary to have a company to do this. It may depend somewhat on how you are generating your revenue. There may be tax and liability benefits to having it run under a company.
*Whether i form a company or not,should i outsource as much work as possible?Maybe you have to ask yourself how much time you really want to commit to this on a daily basis. If you feel the revenue stream can more than cover any expenses to outsource updates and maintenance, that would be a good way to go.
*Do i need a physical offline team..or just do what i can and outsource the rest?Do you mean whether you hire employees or contract/outsource? I would try to make the financials work such that you can contract out the work rather than hire. Unless your business just explodes and it`s more cost effective to have in-house staff, I would stick with outsourcing.
*Are terms of service and disclaimers enough..is insurance a must when
starting a web app?(i.e. I`m wanting to minimise legal costs)I suppose this depends on what the app involves. For any type of business I`ve been involved in, I always factored in liability insurance expenses.
*I don`t have the offline contacts required,outsourcing makes sense but
then how do i entrust critical parts of business function externally? Perhaps you can keep the core, proprietary ideas to yourself somehow and outsource the mundane parts (GUI, database management, etc.)I am an electrical engineer by trade but have done a lot of coding. I did a number projects based on PHP (some web and others just offline software), RoR (this is the framework of the current web app), python, perl, C, etc.
I personally like PHP since it`s a lot like C programming and it`s easy to pick up and understand. RoR took a lot of up front learning to understand the framework but it ties in the database really nicely. You can also do database apps with PHP but it seems a little less elegant.
I hope this helps. If you need any other help or would like to collaborate on anything, let me know.
Sounds like an interesting idea. For the consumer point of view, it might be an attractive aftermarket add-on. You may want to do some searches for "remote" "kill switch" to see if there`s already something like it. I`d be interested to help if you need some technical collaboration. I`m an electrical engineer with 15+ years experience in circuit design.