New Chrome Web Store Badges Might Help You Pick Better Extensions
12356
post-template-default,single,single-post,postid-12356,single-format-standard,bridge-core-1.0.7,ajax_fade,page_not_loaded,,qode-title-hidden,qode_grid_1300,hide_top_bar_on_mobile_header,qode-content-sidebar-responsive,qode-child-theme-ver-1.0.0,qode-theme-ver-18.2.1,qode-theme-bridge,disabled_footer_bottom,qode_header_in_grid,wpb-js-composer js-comp-ver-7.9,vc_responsive

23 Apr New Chrome Web Store Badges Might Help You Pick Better Extensions

Posted at 09:05h in education by

Earlier this week Google announced a new badge program for developers who make Chrome extensions. The program is supposed to make it easier for end-users like you and me to identify extensions that have been created by developers who adhere to Google’s standards of best practices and whose identities have been verified. 

There are actually two different badges that Google is giving to developers of Chrome extensions. The first is the featured badge. That badge seems to be reserved for developers who adhere to all best practice guidelines including privacy, user experience, and clarity of listing page. The second badge is the established publisher badge. That badge is for developers who have gone through Google’s identity verification process. 
It appears that the purpose of these new badges is to make it easier to identify the more or less trustworthy Chrome extensions. That said, the cynic in me now wonders why Google hasn’t required identity verification for developers all along.  
Are you a tech coach or media specialist looking for some new ideas to share with your colleagues? If so, 50 Tech Tuesday Tips is an eBook you need. You can get it right here.

Earlier this week Google announced a new badge program for developers who make Chrome extensions. The program is supposed to make it easier for end-users like you and me to identify extensions that have been created by developers who adhere to Google’s standards of best practices and whose identities have been verified. There are actually two different badges that Google is giving to developers of Chrome extensions. The first is the featured badge. That badge seems to be reserved for developers who adhere to all best practice guidelines including privacy, user experience, and clarity of listing page. The second badge is the established publisher badge. That badge is for developers who have gone through Google’s identity verification process. It appears that the purpose of these new badges is to make it easier to identify the more or less trustworthy Chrome extensions. That said, the cynic in me now wonders why Google hasn’t required identity verification for developers all along.  Are you a tech coach or media specialist looking for some new ideas to share with your colleagues? If so, 50 Tech Tuesday Tips is an eBook you need. You can get it right here.chrome extensions, Free Technology For Teachers, Google ChromeRead More

Print page
0 Likes
No Comments

Sorry, the comment form is closed at this time.