Split Piwik in multiple projects

• tracking database
  • with a well defined API (REST or whatever)
• tracker (Javascript / PHP)
• GUI for desktop
• GUI for mobile

I've updated the description of the task, next year Piwik 3.0.0 is coming, let's start discussing what we want to see in this major platform release?

See issues in 3.0.0 milestones for more information about Piwik 3

sorry just found this issue today. Even if this is already closed just want to share a strategical thought:

Piwik 3.0 milestone already includes lots of important issues.
When looking at them, I noticed that most of them are work topics "inside" of Piwik.
This is of course good to generate a solid technical basis.

On the other side the normal user is no developer and will hardly notice the changes.

Since 3.0 is a major milestone one should maybe think of giving additionally some great "visible" changes/features, which make normal users

• wanting to upgrade to 3.0 instantly
• make them talking about great new features
• produces visibility on professional magazines and Websites & start reader discussion

so that the general impression is: 3.0 is a HUGE STEP - not only for technicians but for everyone!

=> What do you think of this?

an idea on
what could these "I want it" features be?
e.g. for everyone: some features in the unique field of "actions on tracked data" like delete #3385, mark/flag #8161 etc.
or
e.g. addressing the big group of the small store owners using piwik: a packet of 3-4 features of the field of ecommerce
https://github.com/piwik/piwik/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+ecommerce