You asked me if was a developer. My teacher at school taught us how every
programming task should start and end. These were something like 5steps. You
laugh probably at the moment, cause it is only the beginner theory and then
comes real life. That's also why the only thing that I remember from these 5 is
that successful software development should start with planning the
expectations and end with satisfying test results. That's why google that You
wrote about is successful: they do not release not working alpha versions with
the main update killing bluetooth (12.04) or... or look Yourself:
https://www.youtube.com/watch?v=zzfnrLCJOkQ&feature=youtu.be
I'm a human being that do not badly need to have convergence in a >phone< that
doesn't fulfill the >phone< conditions.Let me translate it this way:we build a
car. A car should take You from point A to B relative efficiently. But then one
day You say: "hey! I'd like to hear some music in my car and have air
conditioning!". So You put there a radio and air conditioning. Somehow You
forget that the power consumption of a radio is to big so You have not enough
energy to turn on the light in the evening: You can drive only during the day,
but heyyy! You've got the radio! The engine was to weak to power the air
conditioning so when You turn it on, You can drive only 50 mph though at the
beginning max speed was 100mph. Then some day You decide to umount the rear
seat and put there a TV set. S cl!Before You add another function,
check twice if the phone is still a working phone or in Ubuntu Phone case, if
You want to proceed, double check that there is nothing to be done better with
what You've got already.
Let's sum it up:1. I can check e-mail with my phone but I can't hear an
incoming message.2. ...3. ...4. ... no I'm not gonna list here all the bugs.
But I can tell You how >I< would make this project successful.1. Planning: I'm
about to release a >phone< not a car without wheels but with Facebook access.
So step first: the phone/message/contacts/alarm clock functions have to work
PERFECTLY!1a) ->especially in ubuntu case-> what is Your target audience? Is
this gonna be a phone for geeks only or is my mother also ALLOWED to use it?
2. If You already have the phone You have Your basis: now You can spoil and
"remove any functionalities/services/"libraries" "over the years" (Radics). You
can spoil everything but NOT THE BASIS! People will be delighted to have a
working >Ubuntu phone<. From this point You can go further:
3. You look at other devices that were already on the market. Community helps
You to develop same functions as the other devices have to offer: music player,
>!Bluetooth<, Facebook/Instagram access, apps, hot spot etc. etc.
If Your device work as a phone, You can try to sell it to the market just as a
basic phone. Then proudly announce another big steps in development. What
Canonical tends to do is giving empty promisses ("4K recording"?) and then
disappointing. Nokia was successful cause they went the way I described giving
no chance to competition from Ericsson, Sony, Siemens, Alcatel(lol), Panasonic,
who heard then about Samsung SGH-250? Every 50'th person? But everyone knows
what 3210 was until today, don't You?If I had a company and at first started to
shout about convergence and then closed the project, I'd start to think about
rebranding. "They are the ones who didn't make it". "They are the ones who
promised us 4K recording". "They are the ones who promised us...". Now go back
to point 1a and ask Yourself if all these promises are a good idea.
So all in all my friend, You can be the best developer and I can be the worst.
What's the big difference if one of us goes the right way and the other one not
the best way? It is not only about libraries.
Cheers
Marcin
From: Radics Geza
To: Marcin Xc
Cc: Ubuntu-phone
Sent: Friday, December 16, 2016 11:08 AM
Subject: Re: [Ubuntu-phone] What's the plan for Ubuntu Phone in 2017?
Hi,
If sby say "hater" it is not about critisism, but about style.
Are you a developer? Actually I know the answer, because of your questions.
Sometimes, in order to introduce new things (use new libraries etc) you have to
give up on functionality, which might come back over time (when resources spent
there). It is not UT specific e.g. many functionalities removed from "cloud
services" because they don't scale.
Do you think all windows update is without issue? Do you think google hasn't
removed any functionalities/services over the years?
System like these are complex, not like a simple equation..
bests
g.
Original Message
Subject: Re: [Ubuntu-phone] What's the plan for Ubuntu Phone in 2017?
Local Time: December 16, 2016 5:48 PM
UTC Time: December 16, 2016 9:48 AM
From: gtride...@yahoo.com
To: tallien <3mzuffu...@snkmail.com>, Ubuntu-phone
No, no, >NO< Tallien. It tried to function properly before someone put the text
markers from und
