An unemployed software engineer, I've been picking up Android to sharpen the saw and stave off boredom. I've built, yet another, power manager that seems to provide a unique feature set (as best as I can discern from the primitive marketplace search capabilities). I'd like to publish it as a free download, but without some litigious a$$ suing me into further poverty. I have two questions.
1. It seems that the common practice is to provide a EULA by interjecting a EULA activity screen into your application code and scouring the appropriate EULA content from the web (or going into the hole buying one from a lawyer / law site). Is this correct? 2. If #1 is correct, then I'm curious. Google must have more lawyers than you could drown in the bay. Why does Google's Android Market do nothing to protect individuals contributing free software to the marketplace? It seems a trivial thing to add an EULA acceptance flow as part of the Marketplace application. Generate an as-is, no warranty agreement for non-commercial providers during setup in the marketplace and allow commercial providers to override with their own EULA either packaged in the app or uploaded through the web, if so desired. In this fashion, everyone is protected and each application isn't forced to clutter up their codebase with the same legal garbage. -- You received this message because you are subscribed to the Google Groups "Android Beginners" group. NEW! Try asking and tagging your question on Stack Overflow at http://stackoverflow.com/questions/tagged/android To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en
