Skip to main content

Royalty for developers - need open source App Store

In the developer world, royalty concept is not widespread, but glad that Apple has introduced the royalty through App Store.

What's in royalty?
You--the developer code a piece of logic for a company and it get sold and start milking; but you don't get anything even if it sells more than million copies. Apple's App Store is a novel concept that the developer acts as a company and directly gets sales commission.

Why royalty is important?
A book author gets royalty, a film maker gets it, an artist gets it--but not a developer. A developer has to code, code, code to live.

Who can change the scenario?
After open source revolution, I think, it's time for "royalty revolution". We need a movement like "free software movement" by Richard Stallman to take the royalty concept to all developers. In short, we need an open source "App Store"
Labels:

Comments

Anonymous said…
This comment has been removed by a blog administrator.
Oct 1, 2010, 10:34:00 AM
Post a Comment

Popular posts from this blog

Interview question #1

Since I have been asked to interview experienced PHP programmers, I was preparing few interview questions. I came to know, most of the people ask questions found in the Internet; most of them are like "What is the function used to connect MySQL DB in PHP". Personally, I don't like these types of questions; I'd thought the person must apply ideas what he was taught in colleges--finally I came out with one question: A product vendor has Quantity Vs. Price data like 1 -> Rs. 50 2 -> Rs. 95 3 -> Rs. 140 .... like upto 1 million data. He wants a system, which gives the price when the quantity is provided. For example, if you provide the quantity value as 2, then it should provide Rs. 95. How this system can be designed? As expected, all the people said about using database tables and quering on quantity. I have asked them to find out a system which doesn't use databases--provided the accuracy of the system may not be 100%--it may give at least 90% ac...
7 comments
Read more

Interview question #2

This is related to PHP's array . An array has number of elements. All elements are integers and unique, which means there is no repetitive integers. (e.g.) $foo = array(7, 5, 9, 13, 2, 8); You have to sort the array, provided: You should scan the elements only once. You're not allowed to compare the elements when sorting. (i.e., you're not supposed to use any comparison operators) Sorted resultant array may not be the source array. How will you do that?
6 comments
Read more

Open source PHP frameworks and problems

I was using CakePHP for sometime and proposed CakePlus , another UIMS toolkit on the top of CakePHP but also altering some problematic core of it. The thread should explain the outcome of the post. And, then I noted Akelos framework has most of the things built in. Issues with frameworks esp. CakePHP Scalability not a priority - Developers aren't aware that we can't throw more and more hardware Excessive use of regular expressions Evangelist isn't aware that the framework throws many queries unnecessarily More memory consumption - 100M would never be enough for a simple project Poor coding standards and practices - Prolong use of extract() often leads to more memory consumption Can't use the native approaches or baked codes. The override approach always lead to hard to debug codes Poor architected codes and no clear defined approaches. People belong to the cult drives the direction and often throws unprofiled codes. No native provision to share codes between M-V-C and...
6 comments
Read more