Showing posts with label Google. Show all posts
Showing posts with label Google. Show all posts
Wednesday, April 25, 2012
Chromebook just got infinitely better, and this is the future of Android
I've been using a Samsung Chromebook Series 5 500C for some time now, but to be honest, I was getting ready to sell it because I just couldn't get used to having only one browser open at time. Especially with multiple Google accounts, it just didn't mirror how I work on my Mac with multiple Chrome profiles for every Google account I use. Fifteen full page tabs just feels weird.
The newest release into the Chrome OS dev channel just changed all that. It allows for multiple Browser windows to be overlapped, and includes a ribbon launcher on the bottom of the screen that makes this feel more like a computer.
To get the newest release, you go to the wrench, select "About Chrome OS", select "more info..." and choose "Dev - Unstable". The next time your Chromebook looks for updates, it will download this version, which although it is called "Unstable" has been pretty stable for me.
This all got me thinking...this is probably one of the biggest reasons I don't take a tablet seriously for getting real work done. That is, the multitasking presentation that exists today on iOS and Android just doesn't make sense for how my brain thinks about multitasking apps. I need to see the multiple windows to remember they are there.
The closest I've seen to this being solved is Chrome on Android. There's an affordance that's always there to tile the multiple windows, and it just works so much better than having to remember that button is down there to see the other programs that are running on Android. And having to double button on iOS - I wonder how many people know that is there. The simplicity of iOS doesn't work for me. My brain craves something more complex.
If Google can solve the multi-window problem in Android like they have in Chrome for Android, and merge that with Chrome OS, then I think they will actually have a powerful weapon against Apple. When I can effectively use my Android phone as a Chomebook, then this starts to all make sense.
The Motorola Atrix kind of has a feature like this when you dock it, and although it looks pretty klunky now, perhaps this is one of the things that Google really bought from Motorola mobility, especially if they patented it.
I expect the next iteration of the Xoom tablet, to be a Google tablet, sold like they started selling the Galaxy Nexus yesterday. I expect Chrome to be front and center on said tablet, to pave the way for the Chrome OS/Android merge, with this Moto docking technology coming in the background.
Chrome on Android is already so good, I definitely use it more than I use native apps on my Galaxy Nexus, so this doesn't seem like a stretch.
This post was written entirely on my Chomebook.
[n.b.: this is all conjecture - I don't have any knowledge of this as a strategy from my time working at Google]
Monday, February 13, 2012
Sony and AdWords Remarketing Really Want me to Buy a Nex-5N
A few days ago I did a search for the "Sony Nex-5N" camera, and most likely clicked on the promoted (when ads move from the right column to the top, they are called "promoted") text ad that Sony is running on Google search. This took me to Sony's site on the Sony NEX line, as expected.
I didn't buy the camera from them, but they sure want me to. In fact, whenever I go to any site that has a block of Google AdSense text ads, there's an ad for the Nex-5. Here's four examples from sites you probably recognize.
![]() |
| from PCMag |
![]() |
| from LA Times |
![]() |
| from Chicago Tribune |
![]() |
| from CNET |
Spooky? no. Is Sony reading my mind? Invading my privacy? no.
This is Google AdWords remarketing at work. And it's working beautifully. It's like my own private reminder that I want to buy this camera as I browse the web all day long. It's stuff like this that is making Google's Display business $5 Billion per year. From the AdWords help:
Next, a small piece of code called a remarketing tag is embedded on your homepage, for example. This code tells AdWords to save visitors to your "Homepage List." When people visit your homepage, their cookie ID is added to the remarketing list. Once the remarketing tag is in place you can create an AdWords campaign that targets messages only to people on your "Homepage List" while they browse the Web. Your remarketing messages won't be shown to people who aren't on the list.
The remarketing tag can be embedded on any page within your website, not just the homepage, so you can develop more detailed audiences. For each remarketing list that you want to create, embed a different tag. If you want to create a "Homepage Visitor" list and a "Completed Conversion" list, you need two separate tags -- one to go on the homepage, and one to go on the conversion page. Learn more about remarketing and users' cookies.
There's a balance between creating very detailed and broader remarketing lists. While detailed lists allow you to further target your message, you'll get the most scale and volume with broader lists. Read more on strategies for your remarketing lists, and learn how to tailor your creatives to these lists.
I'll let you know how the camera is.
Tuesday, February 07, 2012
Chrome for Android...wow
|
|
||||
|
|
Some quick thoughts on Google Chrome for Android:
Awesome user experience. For a beta, it's incredibly polished. The animations on the Galaxy Nexus are smooth, and just beautiful. This is the mobile browser you want to look at. You can't see it in the stills, but when you dismiss tabs, they fly off the screen at an angle. Really slick.
The best execution of multiple tabs on a mobile browser I've seen.
It pre-fetches websites it thinks you want to read next - if you want it to. The default is not to do this on the mobile network. ( I wonder if it generates ad impressions for pre-fetched pages, or if they've created an API with Doubleclick to delay impressions somehow. )
When there are no tabs open, your recently closed tabs are there in a list.
According to html5test.com the browser implements 343 out of 475 of the necessary actions (compared to iOS5 Mobile Safari doing 305) and it does seem to render most websites better than anything else I've seen on a mobile device.
And it's fast. I'm sold.
It sure seems to me that the rate in which Android and its collection of apps and services are improving is faster than the rate in which iOS and its apps and services are improving. I personally find myself grabbing my Galaxy Nexus over any other phone about 90% of the time these days. My iPhone is getting jealous for sure.
Wednesday, October 12, 2011
What most non-Google employees don't understand about Steve Yegge's post
Steve Yegge of Google accidentally posted a great rant on Google not forcing its product teams to encapsulate functionality and expose all data and actions as APIs...essentially that Google internally does not use a Service Oriented Architecture.
This is totally true and while I agree it would have actually been a heck of a lot easier to integrate products in Google if they did (something I know a thing or two about) - having one big codebase and database also had the benefit of allowing engineers to really understand what was going on in other parts of Google and forced them to work in a distributed environment across offices.
The web will make a big deal about his post, but I think what most people don't get about his post is that you see posts like this almost every day at Google. At least once a week. I enjoyed seeking out the engineers, PMs, and the occasional sales person, who would take the time to write a well thought out, lucid essay on something that could be changed, made better, or simply challenging a management decision like de-staffing certain projects.
Generally, the Google culture would hash this out, and at times, when appropriate, the exec team would address it. Eric, Larry and Sergey were almost always aware of these things because they would get asked about them in TGIF (company wide weekly update meetings) and they'd usually have a reasonable response.
So enjoy reading this, as it will give you a peek into the Google culture from a freedom of expression point of view, but it's otherwise not a big deal.
This is totally true and while I agree it would have actually been a heck of a lot easier to integrate products in Google if they did (something I know a thing or two about) - having one big codebase and database also had the benefit of allowing engineers to really understand what was going on in other parts of Google and forced them to work in a distributed environment across offices.
The web will make a big deal about his post, but I think what most people don't get about his post is that you see posts like this almost every day at Google. At least once a week. I enjoyed seeking out the engineers, PMs, and the occasional sales person, who would take the time to write a well thought out, lucid essay on something that could be changed, made better, or simply challenging a management decision like de-staffing certain projects.
Generally, the Google culture would hash this out, and at times, when appropriate, the exec team would address it. Eric, Larry and Sergey were almost always aware of these things because they would get asked about them in TGIF (company wide weekly update meetings) and they'd usually have a reasonable response.
So enjoy reading this, as it will give you a peek into the Google culture from a freedom of expression point of view, but it's otherwise not a big deal.
Labels:
Google
Saturday, April 16, 2011
Hoping Larry Page says "Damn the torpedoes"
Wow, Ben Horowitz really nails it with his Peacetime CEO/Wartime CEO post. I think the first item in his litany about halfway down is amazingly salient:
While at Google, I worked on features in my products were never launched because lawyers were concerned about potential legal actions of their direct competitors, and there were times I was asked to reword or redact statements in interviews for fear of seeming too competitive. Meanwhile we had to watch as smaller competitors and launched the exact same features and make the exact same statements with impunity. The result is that instead of providing features the users want, features got watered down. It's the nature of the beast but it was truly a shame because the users lost, and Google lost users.
At the startups I have been involved with, the ones that have been the most successful (including FeedBurner) were the ones where the wartime strategy (redundant because most startups are always in wartime) was "we are going to crush competitor X and we are going to outflank competitor Y." There's no better way to pull a team together and motivate them than when you have a solid opponent to rally around and beat.
A reason I'm bullish on Larry Page being in command at Google is I think he will take more of a "damn the torpedoes" approach to some of these risks and actually compete publicly. He needs to be a wartime general and not a peacetime diplomat. At least that's what I want as a Google user.
Peacetime CEO knows that proper protocol leads to winning. Wartime CEO violates protocol in order to win.and also
Peacetime CEO aims to expand the market. Wartime CEO aims to win the market.Google has been at a distinct disadvantage in that everything they do is under the microscope. Google has deep pockets and people love to sue them when they mess up. Externally, they can never admit who a certain feature might be competing with or outflanking with things like competitive feature matrices in marketing material. Users have to figure that out for themselves.
While at Google, I worked on features in my products were never launched because lawyers were concerned about potential legal actions of their direct competitors, and there were times I was asked to reword or redact statements in interviews for fear of seeming too competitive. Meanwhile we had to watch as smaller competitors and launched the exact same features and make the exact same statements with impunity. The result is that instead of providing features the users want, features got watered down. It's the nature of the beast but it was truly a shame because the users lost, and Google lost users.
At the startups I have been involved with, the ones that have been the most successful (including FeedBurner) were the ones where the wartime strategy (redundant because most startups are always in wartime) was "we are going to crush competitor X and we are going to outflank competitor Y." There's no better way to pull a team together and motivate them than when you have a solid opponent to rally around and beat.
A reason I'm bullish on Larry Page being in command at Google is I think he will take more of a "damn the torpedoes" approach to some of these risks and actually compete publicly. He needs to be a wartime general and not a peacetime diplomat. At least that's what I want as a Google user.
Labels:
Google
Subscribe to:
Posts (Atom)









