Earlier quoted context omitted.
>> Frankly, I can't understand how Google is so chaotic. I'd love an open and honest answer from someone up high in the org chart at Google on that. Better yet, just an acknowledgement of it and how they're going to stop doing this in the future. If they were a startup with 200 employees under the age of 30 I'd understand it, but they're obviously waaaaay beyond that stage.
People high up are aware of it; nobody seems competent enough (at management) to do anything about it.
Updates to our Google Voice apps
301–310 of 364 posts
Re: Updates to our Google Voice apps
#302Earlier quoted context omitted.
This: "they release two products that should be one instead (Android & ChromeOS)"... I've been thinking the same exact thing. Google basically split the ecosystem in half...devs have to unnecessary build seperate apps for each (unless they are using a cross platform engine).
Not really... chromeos is the bare minimum linux environment to run a chrome browser on laptop hardware. Android is some frankenstein of java IDE to develop phone software. They might-should-be the same, but they're fundamentally very different roots.
Re: Updates to our Google Voice apps
#303Edit update: This is similar to forcing sign in on maps (via dark ux) and search (for cross device attribution, ie squeezing more $ out of you, not providing a better service).
Re: Updates to our Google Voice apps
#304Earlier quoted context omitted.
Hell, at this point I would settle for some closure on "what the hell did you mean by 'more wood behind fewer arrows' in 2011 when you began the process of mass project shutdown?!... that's not really how arrows work :/".
More wood = bigger bow. Shoot fewer arrows harder, i.e. more resources behind fewer projects, i.e. quality over quantity.
Re: Updates to our Google Voice apps
#305Earlier quoted context omitted.
Opening iMessage to other platforms would cannibalize iOS sales. I hear soo many people say they'd try Android, but they can't lose iMessage
Apple wanted to open it up, supposedly, but I read somewhere that they were apparently blocked by lawsuits with VirnetX (an apparent NPE/patent-troll), ongoing since 2010.
Re: Updates to our Google Voice apps
#306So, is this the death of Hangouts and rebirth of Google Voice then? They had previously been transitioning the UX off of GV and onto Hangouts.
It's absurd that consumers are left guessing which of Google's services are around for the long-haul and which are doomed. There was a time when success was the default outcome for a new Google product/service. Now it's the opposite, and the crazy thing is that Google did it to themselves.
Re: Updates to our Google Voice apps
#307[edit] I guess it's not updated in the play store yet?
[1] http://www.apkmirror.com/apk/google-inc/google-voice/google-...
Re: Updates to our Google Voice apps
#308Earlier quoted context omitted.
I've never had an eyePhone and switch to Android from Palm's WebOS. But for years I've always used 3rd party ROMS (Cyanogen mostly). Google has a vested interest in not fixing Android's brokenness. They make a lot of money off phones that needs to be replaced every 2 years. With their strict control over OHA, they can easily mandate PC style platform standards to reduce e-waste, fight planned obsolescence and offer r…
> They make a lot of money off phones that needs to be replaced every 2 years. Someone is vested in making money every 2 years alright, but it's not Google - it's Qualcomm. > With their strict control over OHA, they can easily mandate PC style platform standards to reduce e-waste, fight planned obsolescence and offer real security updates Unfortunately due to Linux's intentional lack of a stable driver ABI, the abili…
Re: Updates to our Google Voice apps
#309Earlier quoted context omitted.
Hell, at this point I would settle for some closure on "what the hell did you mean by 'more wood behind fewer arrows' in 2011 when you began the process of mass project shutdown?!... that's not really how arrows work :/".
The real problem seems to be inability to aim. Google fired a ballista at Facebook with G+ and missed completely.
Re: Updates to our Google Voice apps
#310Earlier quoted context omitted.
Uber Eats thinks that my former Voice number (now Fi number) is not a real cell number, so it does not let me order. After repeated support tickets, they still assert that it's a virtual number and will not let me order.
Voice & Fi numbers are considered "call forwarders." Call forwarders are not allowed (legally?) to forward numbers to other call forwarders. Hence the issues between Voice & Fi. This might be the same issue with Uber Eats.