Lyza Danger Gardner on Building the Web Everywhere: How do we get it done, now?

For web platform enthusiasts, the developing ServiceWorker is a wunderkind among APIs. It’s taking a lot on: offline-first control over assets, performance improvements via network interception and cache management, background process enhancements.

It’s cool and I want to use it right away. I want to ride the offline-first wave. But ServiceWorker is in that awkward phase of partial adoption and implementation that raises the question I’ve asked myself before: how do I use this beautiful future thing, now?

ServiceWorker, valiant in shining armor

Briefly, ServiceWorker provides a proxy, letting you make decisions about how to handle and respond to network requests coming from your (client-side) app.

Want to respond to requests for gif files differently if the browser is offline? ServiceWorker can do that. Want to explicitly retrieve assets from the browser cache for certain requests? ServiceWorker in conjunction with its pal the cache API can do that, too. Neat-o.

ServiceWorker is, in part, a do-over for the API devs love to hate: Application Cache, a.k.a AppCache (though, I should point out, ServiceWorker is considerably more functional than AppCache).

The waning antagonist: AppCache

It’s rare that I say “this is really just how it is” about anything to do with web technology but, okay, I’m going to be straight with you: AppCache is awful to work with.

With AppCache, you (ostensibly) create a manifest file of the stuff you want the browser to cache locally. In practice, there are so many ways to get this wrong.

It’s confusing to debug and difficult (sometimes nearly impossible) to rectify if you make a boo-boo—which you will, because it is a cruel master. And it just doesn’t give you fine-tuned control.

Ideals vs. present reality

AppCache is a beast, but it’s been around for several years and is supported by the majority of modern browsers.

ServiceWorker is partially implemented in about 45 percent of the world’s browsers—newer Chrome, Android, Opera browsers. That seems substantial; however, there is no official word that Safari will ever implement it.

Another wrinkle is that ServiceWorker is partially re-implementing something that already exists. There is no straightforward progressive enhancement from AppCache to ServiceWorker. Supporting both probably means writing certain functionality twice.

That means for real-world project architecture, I have several options, each unsatisfying on some level:

1. Treat offline-first as an enhancement that works in under half of the browsers out there
2. Write an offline approach using AppCache and then also write it in ServiceWorker for browsers that support it
3. Write an offline approach in AppCache and leave it at that

Option 1 won’t fly right now if you have a need to support a broad set of users. Option 2 is technically possible, but requires logic duplication and budget-straining extra time. Option 3 is functional but unappetizing.

So now what?

We’re caught in the limbo between the web as it is and the web as we hope it will be soon. My heart is in the future; our reality is in the less full-featured now.

There is an ongoing conflict between what we want to believe is immediately doable and what is, in fact, feasible. I don’t want to suggest an academia-industry divide, because we’re all on the same side here. But we sometimes get wrapped up in the promise and energy of new standards and are blind to their growing pains.

Every new standard has to pass through the shadows of doubt as it makes its way to the light of day. We’ll always need to choose which questing API heroes to throw in with, knowing not every contender can be victorious.

The web demands risks and, dare I say it, courage. Its democracy leads to uncertainty—no one’s entirely in control of this crazy thing. Which is why forward-looking web thinking is considered future-friendly, not future-proof.

I’m not clamoring to put the brakes on the pace of change. We are getting what we asked for, for the most part: accelerating invention and improvement of the web.

But I’d like us to recognize that making decisions about fledgling platform APIs and the changing web is another expertise we have, though we may take it for granted.

And that building the web every day is a leap of faith.

via planetweb

Google Changes "First Click Free" Policy For Google News and Search

Google has updated its First Click Free policy over subscriber content behind a pay wall.

via planetweb

This week's sponsor: Contentful

Help your developers and writers manage dynamic content on the web (and in apps!) with our sponsor Contentful’s API-first CMS.

via planetweb

Google AdWords New "Customer Match" and "Universal App Campaigns"

Google's new "Customer Match" in AdWords allows advertisers to target ads on e-mail address database, and "Universal App Campaigns" lets developers promote their apps across search, Play, YouTube, and Google's display network.

via planetweb

It's Official: North America has run out of new IPv4 addresses

On 24 September 2015, ARIN issued the final IPv4 addresses in its free pool.

via planetweb

Click Fraud by Bots Could Cost $6.3 Billion in 2015

Everyone involved in the ad business, including Google, Microsoft, Yahoo, and advertisers big and small.

via planetweb

http://ift.tt/16fiYnL

Recently I’ve seen several interesting conversations about ad blocking, and I wanted to remind people about a great offering called Google Contributor. With Google Contributor, you contribute a certain amount of money each month. That subscription means that you see fewer ads on the web, and you support the sites that you visit with your money.

You get to decide how much to contribute (I do $10/month, but for example you can do $2/month if you prefer). The more you contribute, the fewer ads you see. The handwave-y explanation that when you go to a website, your monthly subscription actually bids on your behalf in ad auctions. So you end up buying the ad yourself rather than someone else. This is cool for several reasons:

1. You support the sites you visit without expending any energy.
2. You see fewer ads.
3. (And this is the cool part) you get to decide what to show in that ad space instead of ads.

That’s right: you can pick a custom URL to show to yourself instead of ads. It’s like buying space on a billboard and showing nature scenes instead of ads. Personally, I like to show a dynamically generated Mondrian-like pattern:

But here’s the part I love: when you sign in, click the gear icon and then “Advanced settings,” and at the bottom of the page you can provide any custom URL you want (it does have to serve over https). You could replace ads with pictures of kittens, or your family. Or make ads your todo list, or a reminder to get back to work. Think outside the box, like Paul Ford. It’s the open web–you can have all kinds of fun with your HTML.

Here are some common misconceptions about Google Contributor:

Q: I thought Google Contributor only worked with ten websites or so?
A: No, it works with millions of websites. Contributor launched with a small set of websites initially, but if a website runs Google ads like AdSense or DoubleClick for Publishers, it’s likely to be compatible with Contributor.

Q: Isn’t there a waitlist to join? Or I need an invite or something?
A: Not anymore! You can sign up immediately and support tons of websites with one monthly payment.

Q: Can I see which websites I’m supporting?
A: Yes! You get a report that looks like this:

If you like the web and use it as much as I do, why not support some of your favorite websites while reducing the number of ads you see? Give Google Contributor a try now.

via planetweb

Microsoft Drops Bing Default Search In China For Baidu

As part of Microsoft's move to get Windows 10 into China, Microsoft is to drop Bing as the default search on Edge browser and replace it with Baidu.

via planetweb

Mark Llobrera · Professional Amateurs: The Nearly-Headless CMS

If you’ve been paying attention to the CMS scene lately, you’ve probably heard the terms “headless” and “decoupled.” These terms describe websites and applications where the CMS is not used to render the actual site or application. For instance, it could be a website where the front-end is a JavaScript framework like AngularJS or React, and the CMS supplies the content via a JSON API. A List Apart recently hosted a very timely and informative ALA On Air panel titled “Love Your CMS,” which touched on the topic and sparked good discussion around the pros and cons of the approach. I recommend watching the archived video (or reading the provided transcript). I found it instructive to hear Ryan Irelan talk about the difference between “headless” and “decoupled,” and why he considers them to be related but not exactly the same.

At Bluecadet, we didn’t set out to do headless CMS development for its own sake. We were curious about it and could see the potential benefits, but we only ended up doing it when it solved specific problems we faced on two very different projects.

The first was a website for Haruki Murakami. We wanted to create as seamless an experience as possible, which meant experimenting with different animated transitions between sections on the site. We eventually settled on AngularJS to support those transitions, so the challenge was how to merge AngularJS with WordPress, the CMS we were using. There are a few themes that do this, but after some testing and much research we decided to use the JSON API plugin. The client got a familiar CMS to work with, but also a very tightly-orchestrated front-end layer that captured their creative vision for the project.

The second project wasn’t a website—it was a Cinder (C++) touchscreen application for the Art Institute of Chicago that helps visitors learn more about James Ensor’s multi-piece drawing, “The Temptation of Saint Anthony.” Prior to this project, we had completed another touchscreen project with the content managed via XML, and we felt that we (and our clients) could benefit from a CMS instead of hand-editing XML files. Since we have a lot of experience with CMSes for websites, the challenge was how to connect a CMS to a touchscreen application. Again, JSON was the glue—we had done some research into serving up JSON from WordPress, and once we found a JSON parsing library for C++/Cinder the two big pieces came together. We were able to quickly build the CMS in WordPress, giving content authors a familiar interface, as well as reducing potential data errors. This had a profound impact, bridging two sides of our agency’s practice that had previously operated in fairly separate spheres. Once we finished this first headless CMS, the rest came along quickly. We now use them with JavaScript applications, iOS/Android applications, and touchscreens.

Why do I tell these stories? The key lesson for us was that a headless CMS helped solve a problem. We didn’t dive into headless CMSes because it was trendy, we did it because we needed to solve specific problems (in the first case an aesthetic/creative one, and in the second a data-management one). The other important outcome was that we could let each piece of the project do what it does best—by letting the CMS simply manage content, we could use better tools for rendering the presentation layer. We were also able to let our team members focus on what they did best: with the James Ensor touchscreen, our CMS developers were able to take care of the data management problem while our Cinder developers could focus on the touchscreen application.

Use your existing CMS

So let’s say that you’ve got some very good reasons to go headless. Maybe you want to have control over the front-end markup and animation in a way that stretches past what your CMS’s theming layer can support. Perhaps you want cleaner separation of front-end and content-management tasks—it can be easier to staff multiple projects when the responsibility for building a site doesn’t require everyone to know both the front-end rendering layer in addition to the backend of the CMS. Or perhaps you’re not building a website at all. Maybe you’re building a native iOS or Android application, but you need a familiar, yet robust, way to provide data for it.

The good news is that your preferred CMS likely already has what you need. WordPress and Drupal both have modules and plugins to enable a RESTful API, which I’ve found to be the most straightforward way to provide data in a headless architecture. For WordPress there’s the aforementioned JSON API plugin, as well as WP-API (which is being developed with the goal of eventual inclusion in WordPress core). Drupal has the Services module and Services Views, which allows developers to turn Drupal output created with Views into API endpoints.

If you’re interested in the WordPress side of things, WPEngine’s Torque magazine has a number of posts that cover the basics. For Drupal, this is a very handy video tutorial covering Services Views.

One to many (even if it’s just one)

So far, the examples I’ve described are headless with a one-to-one relationship between the CMS and the front-end rendering application. A useful thing resulted from our work on those applications, however: my teammates and I started to decouple our expectations on the CMS side as well. For all the talk of dividing content from presentation, it’s still absurdly easy to build assumptions into your CMS for a single form of delivery. You start out knowing that the CMS will be used for a website, so everything from the order of the fields to the name of your fields is influenced by the form that it will take on the site. But what if your CMS later needs to support different products besides that initial website? This is something that Jeff Eaton and others on the ALA on Air panel addressed quite well, by drawing a distinction between the intertwined content management and web publishing responsibilities of most CMSes.

I’ve found that having to build CMSes that serve many individual products has made me focus more on flexibility. So even if I’m building something that is only being used for a website right now, in the back of my mind I’m wondering what would be required if we had to support a native iOS or Android application using the same CMS. I’ve started thinking of these as nearly-headless (or headless-ready) CMSes.

That relates back to one of the key tenets of the web: separating content from presentation. It’s why we have CSS separate from our markup, and rely on class hooks so that we can style things in ways that do not affect the semantics of the content.

Right now I’m at the very beginning of a CMS project that has to serve multiple products: multiple different touchscreen applications, iOS/Android apps, and a responsive website. If we hadn’t had the initial experience creating headless CMSes for those individual product types, we’d be nervous. But right now we’ve got confidence that we’ve done all of the separate pieces before, even if we’ve never tried to do everything using one CMS.

Downsides

There are a few potential downsides: it increases the number of variables in the system, for one. So not only do you have to deal with Drupal or WordPress, you also have to deal with AngularJS, React, or whatever renders your front-end. (I should interject here that I’m wary of using JavaScript frameworks purely for convenience, especially if the CMS could readily handle the front-end rendering requirements of the project. But that’s a subject for another time.)

This is less an issue for native mobile applications, because those are always going to be separate from the CMS anyway. Still, simply having multiple software systems can be tricky, because each piece comes with its own assumptions and opinions on how things can/should be done. It also means that your team’s expertise has to cover different codebases. (Although that’s potentially an upside, if your team already has that expertise in both camps.)

My litmus test is pretty simple: does going headless with the CMS solve a key problem, and is it enough to outweigh the complexity added to the project?

Try it out

I hope you come away from this thinking that this subject is not as mysterious as it might appear—you can use popular, well-supported CMSes to do this today. If you’ve been wondering how to get complex data into a JavaScript (or native) application, the tools you need are likely available for your CMS of choice. That means that you or someone on your team already has the skills and experience, and the question then shifts from whether you can, to when the time is right to do it.

via planetweb

This week's sponsor: MakerSquare

Accelerate your career with a 12-week immersion course from our sponsor MakerSquare. They’re enrolling soon in SF, ATX, and LA, so prepare your application today!

via planetweb

Google Releases Brotli: Open Source Compression Algorithm

Google has announced Brotli, a new, open source compression algorithm for the Internet.

via planetweb

Microsoft Releases Office 2016 for Windows

The new collaboration features look interesting...

via planetweb

Managing Your Content Management System

Privacy is UX

Google's Appeal Rejected By France, and "Right to be Forgotten" Should Apply Globally

France has rejected Google's appeal and says it must apply the "Right to be Forgotten" on a global basis.

via planetweb

Apple Removes Apps Infected With Malicious Code

A malicious program dubbed XcodeGhost was embedded in hundreds of legitimate apps.

via planetweb

Evaluating Ideas

Report: New Malware Campaign Targeting Vulnerable WordPress and Plugins

A large number of sites are getting infected with the aim of driving malware onto site visitors' computers. Google is already blacklisting infected sites.

via planetweb

Bing To Close Link Explorer October 1, 2015

Bing is to retire one of it's really useful tools from Webmaster Tools, Link Explorer, on October 1, 2015.

via planetweb

On Our Radar: A Nation of Makers

Facebook at Work coming soon to a cubicle near you

Facebook will likely launch a freemium version of its workplace product Facebook at Work by the end of the year in attempt to compete with Slack, Yammer

via planetweb

This week's sponsor: MailChimp

Big news from our sponsor MailChimp: new MailChimp Pro, with multivariate testing, comparative reports, and priority support.

via planetweb

Google SEO: Time to Retire the Keyword from Site Architecture?

WebmasterWorld Members debate the topic of retiring keywords from site architecture.

via planetweb

Stop Cringing and Embrace the Unknown

You know those moments when you’re shown a new feature to build, a description that needs to be written, or a design that needs to be translated to code, and you just freeze? When you aren’t sure where to go or how to begin?

This happened to me recently; the designer I was working with wanted to include a small animation on the homepage. I’ve taken an animation workshop, and I’ve done very small things on sites before, but I’ve never done something quite like what he asked for. At first I thought it was completely unnecessary, why bother? But as I worked through it, Googling madly and using Mozilla Developer Network a lot, I learned. When I got it working, or at least got it started, it was fun to see.

We’ve all had those moments when we’ve been asked to do something in our work, and cringe. I get it, some days you just want to coast, use the knowledge you have, get the job done. But on those same days, you may be thrown a new idea or concept that you need to make happen. How we handle these moments, can make a difference in how our days go.

Lately, instead of cringing, I’m pausing to think of the task differently when something new is thrown my way. Instead of feeling like I can’t do it, or searching for an argument for why we shouldn’t do it, I’m trying to look at these moments as a possible way to learn.

I can be old fashioned at times; I like the code that I know works, and sometimes I’m slow to warm up to new things. But, I’ve found when I keep an open mind to the possibilities and try something out, I learn and sometimes I even have fun.

We have so many tools at our finger tips that can help us learn quickly, and I know when I learn something on the job, the new ideas stick with me longer. Truth be told, I’ve gotten fond of reading the drier specs and documentation—it’s a way I’ve found I can learn on my own in these moments of uncertainty.

So now, instead of cringing when the new idea is presented to me, I’m pausing to think through what a plan of action could be. Can I figure out how to make it happen? When I get something to work, like I did recently with that animation, it’s a gratifying feeling, knowing that I pushed through the fear and learned. Truth be told, this is often how we grow, by pushing through those moments, we realize that we’re capable of figuring it out and getting it done.

via planetweb

More Resources for Accessible Animations

Tuesday’s article on animations and vestibular disorders may have left you wondering what else you can do to make your animations accessible. Here are a few resources to start learning more about how animation and accessibility can work together:

WCAG recommendations

This is a good place to start for the basics of accessible animations. In a nutshell, the WCAG has two recommendations that specifically apply to animation. The first is to provide pause controls for any animation that starts automatically and plays for more than 5 seconds. Auto-updating content and animated carousels could likely fall under this category.

The second is to not have any part of the screen flashing more than three times a second. Flashing any part of the page above this threshold can risk potentially triggering seizures.

Providing alternate content

Just like static content, there are times when providing alternate content for an animation is a smart thing to do. Webacessibility.com’s best practices for animation offers suggestions on when to provide alternate content and limiting the number of times or duration of animations for assistive technology.

Making your SVGs accessible

More web animation is being done with SVG—and that’s great news for accessibility. If you include SVG inline in your web page, it’s inherently more accessible than canvas: whereas canvas is simply a drawing area, the content and text inside your SVG elements can be access directly by the browser.

Dudley Storey and Léonie Watson have both published useful lists on how to make SVGs accessible in a variety of contexts. You can also assign ARIA roles to SVG elements for more descriptive power. The a11y project has a helpful primer on ARIA roles to get you started.

More on vestibular disorders

Marissa Christina does a wonderful job describing what it’s like to live with a vestibular disorder in her interview on The Big Web Show. Her site, Abledis, is full of great insights and information as well. (The section on motion warnings hasn’t been updated in awhile, but a lot of insight can be gleaned from the comments.)

Also, Greg Tarnoff has proposed using specific Twitter hashtags to warn others of potentially triggering links.

These are all useful resources to check along the way to be sure you’re making your animations accessible. If you have any similar resources that you use, please share them in the comments!

via planetweb

Google Contributor: New Ways To Fund The Web

WebmasterWorld members discuss Google Contributor: An experiment to find new ways to fund the web, instead of purely advertising. Can Google Contributor ever work?

via planetweb

Design Tools: What Are You Using?

Back in June, our friend Khoi Vinh launched a survey of tools used by designers over on Subtraction.com. Today, he shares the results from 4,000 designers working in some 200 countries. The findings contained a few surprises for our team:

Interface design

As anecdotal experience may already have suggested, Sketch has pulled into the lead for interface design, edging out Photoshop by 5% among survey respondents. Clearly Photoshop is not dead. And the results might skew differently if the survey had been limited to design studios and agencies, where Sketch weighed in at 27-28% (depending on size of studio). Still, there was a time before responsive web design when no one could have imagined Photoshop winning anything less than the whopping majority of designer desktops.

Version control and file management

No surprise here: Dropbox leads the field for version control and file management, followed respectably closely by Github. As you’d expect, Github fares best at startups, but it even does respectably well at small design studios.

Some classics are tough to beat

When it comes to brainstorming, the industry overwhelmingly favors that lo-fi classic: pencil and paper. The usual suspects in other areas of the survey (Sketch, Illustrator, and Photoshop) lagged further behind here than you might expect.

Check out the full results (beautifully designed by the fine folks at Hyperakt and powered by Typeform), and let us know what surprised you in the comments.

via planetweb

Google AdSense Sticky Ad Units Beta Test

Google AdSense is running a Sticky Ad Unit Beta test.

via planetweb

Google Updates and SERP Changes - Sept 2015

WebmasterWorld's monthly look at Google's SERPs changes.

via planetweb

Mentoring Junior Designers

Over the past 12 years, I’ve been in a lot of training sessions; some were company mandated, others were ones I designed and ran myself, still others were sessions I paid money to attend. For a number of years, I’ve been in charge of a design team, and that means being responsible for training and development for my team members. While they are, of course, active participants, it’s important to acknowledge that training is about the transfer of information and the building of skills. The junior members of your team do not spontaneously gain skills. Instead, you need a clear process in place to train and mentor them.

There are a number of things to consider when talking about training designers. My experience has been on an in-house team, so I’ll speak to that type of training and mentorship, but this applies to all kinds of design and development teams. OK, onward.

Your weekly or monthly check-ins with your design team are a time to catch up on how current projects are going, but you should also find out what they need help doing and what new things they want to learn. I try to match designers yearly performance and development goals with shorter-term goals, scaffolding them so that we constantly build toward more complex abilities and tasks.

But how to find out these things? A simple exercise often helps. As you do a wrap-up on one project, ask the designer to complete the following sentences:

1. One thing I can do now is ______.
2. One thing I’m still unsure about is ______.
3. One thing I’d like to learn is ______.

You learn:

1. They now have a fresh new skill that needs to be practiced and embedded in their workflow.
2. They are not clear on a task or technique and need your help to understand it.
3. After doing this project, they have an idea of where they fell short.

The second and third answers are where you can focus your training plans.

For many people, there is a temptation to just assign a big new task and “let them get on with it.” But this is only effective for the most motivated people, and actually assumes they already have the skills to complete the task. That’s not really learning anything new, is it? So, let’s look at this in a slightly different light. Assigning tasks means looking at someone’s current abilities and tailoring the assignment to match. I think of this in four levels of difficulty.

Imagine the task is to develop a pattern library for a new web app the company is working on. The development goal is for the designer to learn how to design UIs based on components, code, and systems, not full PSD layouts.

Level one

“I’d like you to develop a pattern library for our new web app. You should base it off the corporate pattern library, and build it in Sketch. We need type, button, and menu styles, and it needs to be completed by the end of the month.”

This is the lowest level, and has very little autonomy. All the variables are controlled, from the content, to the references, to the timeline. This is good for a designer who needs to get the basics down.

Level two

“I’d like you to develop a pattern library for our new web app. You should base it off the corporate pattern library, and build it in Sketch. It needs to be completed by the end of the month.”

There is still very little autonomy here, but fewer variables are controlled. The designer has the freedom to decide what UI elements will be in the pattern library. You would use this level when someone have their sea legs, and needs experience deciding what is important in their projects.

Level three

“I’d like you to develop a pattern library for our new web app. You should base it off the corporate pattern library, and it needs to be completed by the end of the month.”

Here you can see there is much more freedom to design independently. As the design lead, though, you are still controlling important factors like deadlines. The design tool, in this case Sketch, is no longer important, as the designer already has knowledge of what the project will need, and can plan accordingly.

Level four

“I’d like you to develop a pattern library for our new web app. Let me know if you have any questions.”

Wow—almost complete freedom. The company goals are still defined, but the designer is given freedom to deliver whatever they think will meet the project goals.

Whatever the designer has identified as a skill they would like to learn, or a project they would like to try, you can use these different levels to assign that project. By offering direction that acknowledges the gaps in their knowledge, you will challenge them without making it an impossible experience.

So, you have assigned a project that will develop new skills for them. They have started on their way. Regular check-ins, especially during team meetings, gives them a chance to share their progress, not only with you, but their teammates. After all, as a senior designer, it’s your job to make sure they are able to complete the task and learn specific new skills. By reviewing both the controlled factors, like deadlines and project goals, and the more creative factors, like tools and visual design, your check-ins create a measurable, achievable pathway through the project. Everyone likes pathways!

I encourage you to use a process like this to build up the skill levels of your more junior teammates. Looking out for the health of your team, and the projects you launch, means also looking out for the learning and development of your team members. This process starts with senior and junior designers working together to identify training needs. It continues with assigned work that builds, not crushes, your teammates. And finally, because few people can just spontaneously learn on their own, you act as a constant mentor through the assignment. The process standardizes the transfer of information and techniques from senior to junior designers, in a clear and understandable way, so that your team members gain the skills they need to grow as designers.

via planetweb

Instagram Ad Campaigns in 30 Countries Start 30 September

Instagram is to launch its advertising programs in 30 countries from September 30, and it's for large through to small advertisers.

via planetweb

IAB Closely Monitoring The Effects of Ad Blockers

When an organisation such as the Interactive Advertising Bureau (IAB) starts monitoring the effect closely, you know ad blocking is becoming a major concern.

via planetweb

Designing Safer Web Animation For Motion Sensitivity

Hello, My Name is

Facebook Tests New Mobile Ads Format

Facebook continues its tests of mobile adverts as it, and many others try to find ways to make mobile ads work for its customers.

via planetweb

Microsoft Uses Bing to Discourage Users From Switching Browsers Away From Edge

Microsoft is trying to discourage users from switching away from its Edge browser when searching in Bing...

via planetweb

Parody Twitter Accounts, Hot Water, And Lawsuit Settlement

When it's quite obviously a parody, it seems that a lawsuit may not go anywhere,...

via planetweb

Chrome 45 Comes With Power, Memory and Tab Restore Enhancements

Memory-saving, Flash pausing, power-saving, and tab restore enhancements all in Chrome 45.

via planetweb

Bing Ads App For Android Released

The Android version of the app for advertisers wanting to manage their campaigns while mobile.

via planetweb

Google Street View App For iOS and Android With 360 Degree Imagery

Google's Street View app for Android and iOS now include 360-degree imagery.

via planetweb

Firefox for iOS Preview

Mozilla has said the preview is being released in only one country right now.

via planetweb

TrueView Campaigns Now In Core Google AdWords Interface

TrueView now in core AdWords interface, along with new columns.

via planetweb

On Our Radar: Faux-Naïve

This week's sponsor: Squarespace

Make beautiful websites with help from our sponsor Squarespace. You can keep it simple, or customize HTML, CSS and JavaScript with their Developer Platform.

via planetweb

This week's sponsor: Squarespace

Make beautiful websites with help from our sponsor Squarespace. You can keep it simple, or customize HTML, CSS and JavaScript with their Developer Platform.

via planetweb

Google Says, The Wrong Type of App Interstitials Will Get You Penalised

"After November 1, mobile web pages that show an app install interstitial that hides a significant amount of content on the transition from the search result page will no longer be considered mobile-friendly."

via planetweb

Rian van der Merwe on A View from a Different Valley: The Distance to Here

Google unveils new logo

Google's new logo is not just for the desktop anymore

via planetweb