Hubbry Logo
IGoogleIGoogleMain
Open search
IGoogle
Community hub
IGoogle
logo
8 pages, 0 posts
0 subscribers
Be the first to start a discussion here.
Be the first to start a discussion here.
IGoogle
IGoogle
IGoogle
View on Wikipedia
from Wikipedia

iGoogle (formerly Google Personalized Homepage) was a customizable Ajax-based start page or personal web portal launched by Google in May 2005. It was discontinued on November 1, 2013,[2] because the company believed the need for it had eroded over time.[3][4]

Key Information

As of October 17, 2007, Google had made the service available in many localized versions in 42 languages, and in over 70 country domain-names.[5] In February 2007, 7.1 million people used iGoogle.[6] In April 2008, 20% of all visits to Google's homepage used iGoogle.[7]

Features

[edit]

Gadgets

[edit]

iGoogle gadgets interacted with the user and used the Google Gadgets API. Some gadgets for Google Desktop could also be used within iGoogle. The Google Gadgets API was public and allowed anyone to develop a gadget for any need.[8]

The API allowed developers to create widgets (web plugin, portlet, webpart) to run in users' iGoogle pages or other web pages quickly and easily. Users had the ability to add a gadget to their iGoogle portal, or have it coded into their own website, by specifying a URL (this could be done indirectly via the gadget registry). Users appeared in the registry if the gadget had been submitted to iGoogle.

Gadgets were rendered as an iframe. Security constraints prevented users from damaging the portal and other gadgets. Users communicated with other gadgets via a remote call to a common third party server.

Google also allowed users to create special gadgets that did not require the use of the Gadgets API. The gadgets were designed to be shared with friends and family. The special gadgets were required to be created using an online wizard and belong to one of the following types:

  • "Framed Photo" – displayed a series of photos.
  • "GoogleGram" – created special daily messages.
  • "Sidebar" - designed for middle school chat rooms
  • "Daily Me" – displayed user's current mood and feelings.
  • "Free Form" – allowed the user to input text and an image of their choice.
  • "YouTube Channel" – displayed videos from a YouTube channel.
  • "Personal List" – allowed the user to create a list of items.
  • "Countdown" – countdown timer.
  • "Daily Literary Quote" – displayed literature-related quotes served up by ModeRoom Press.

Some of the developer-made gadgets included:

  • "Meteo-si": displayed the current weather and the weather forecast for selected areas.
  • "eBay Gadget": searched for items on eBay.

Additionally, a "You might also like" gadget suggested similar gadgets to those the user already had.

Themes

[edit]
iGoogle with the Winter Scape theme

With iGoogle, users could select unique themes for their Google homepages; some themes were designed by Google itself and others by third parties.

Experimental iGoogle

[edit]

On July 8, 2008, Google announced the beginning of a testing period for a new version of iGoogle which altered some features, including replacing the tabs with left navigation, adding chat functionality, and a canvas-view gadget for RSS.[9] Users were selected for this test and notified when they logged in by a link to a brief description and further links to forums. On the forums, it was explained by Google staff that there was no opt-out, as a control for the test. Further, there was no information on how long the test would continue. On the main discussion thread, almost 600 users expressed dissatisfaction with the new version and with the inability to opt out.[10]

On October 16, 2008, Google announced the release of a new version of iGoogle and retired its older format. The release did not initially include the persistent chat widget. It did include the left navigation in place of tabs as well as a change to widget controls, however.[11] The stated purpose was to prepare for OpenSocial, with the new canvas view stated as playing an important role in that.[12] InformationWeek[13] reported "a vocal group of users" as unhappy with the changes, pointing out that many users do not want change forced on them, and that this is a general problem with cloud software under a service provider's control.

A workaround to restore the original tab layout was found by attaching "?gl=all" to the end of the iGoogle URL. On June 4, 2009, this workaround was eliminated. Within days, another workaround was discovered. Changing the URL ending to "?hl=all" would again restore the original tab layout, with some missing links across the top of the home page, including "Maps" and "more". This workaround was again eliminated on November 18, 2009. This led to an immediate resurrection of the controversy over user choice, both in the UK and worldwide, as many people unhappy with the new layout imposed on US users had switched to the UK Google site where the workarounds still worked. Within hours, the most frequently asked question on the help forum was how to restore the old layout, and there was a large number of feature suggestions to the same effect on the Google product ideas page. Other solutions had come to the fore, which require adds-ons, greasemonkey scripts or bookmarklets.[14]

Discontinuation

[edit]

On October 14, 2011, Google announced through its official blog that with its new focus on Google+, the ability to interact socially on iGoogle would be disabled on January 15, 2012, and the mobile version of iGoogle would be shut down on July 31, 2012.[15][16]

On July 3, 2012, Google announced on its blog that several of its services, including iGoogle, would be retired due to "the unforeseen evolution of web and mobile apps and the erosion of the need for the site." iGoogle was retired on November 1, 2013, with the mobile version being retired on July 31, 2012.[2]

Since Google announced its discontinuation of iGoogle, several alternatives appeared, many of which are still online (as of June 2017).[17]

A later feature in 2022 tested a revised Google.com home page with customizable widgets at the bottom of the screen, this was compared to iGoogle.[18] As of November 2024, this feature had not launched.

References

[edit]
[edit]
Revisions and contributorsEdit on WikipediaRead on Wikipedia

IGoogle

View on Grokipedia
from Grokipedia
iGoogle was a customizable Ajax-based personal and start page service developed by , originally launched as the Google Personalized Homepage in May 2005 and later renamed iGoogle in April 2007. It enabled users to tailor their homepage with modular "gadgets" for displaying real-time content such as feeds, weather updates, stock quotes, news from sources like and Wired, and integrations with Google services including and , all while supporting themes and developer-created extensions for enhanced personalization. The service quickly expanded internationally, becoming available in over 70 countries and languages by late , and introduced features like canvas views for gadgets and full feed reading in , along with chat integration later that year and game themes in , to make it a central hub for daily web activities. At its peak, iGoogle served tens of millions of users who relied on it for aggregating , news, videos, and social interactions directly on one page, reflecting Google's early vision of "fusion" to blend search functionality with personalized . However, with the evolution of mobile and web apps on platforms like Android and Chrome, the need for a dedicated portal diminished, leading Google to announce its retirement in July 2012 and fully discontinue the service on November 1, 2013, after providing users 16 months to export data or transition.

History

Launch and Early Development

iGoogle, originally launched as the Google Personalized Homepage, debuted on May 19, 2005, marking Google's entry into the personalized web portal space. The service was initially offered in beta through Google Labs, accessible to users with a Google account, such as those with Gmail. Developed under the supervision of Marissa Mayer, it represented Google's strategic push to expand beyond its core search engine into more interactive, user-focused web experiences. The core concept centered on a customizable start page that allowed users to aggregate and organize personal content without leaving the interface. Key features included drag-and-drop modules for feeds, news headlines from sources like the and New York Times, weather updates, stock quotes, email previews, and integrated Google search results. Built using Ajax technology, the platform enabled dynamic content loading and seamless interactions, enhancing usability by avoiding full page reloads. Early adoption was swift, driven by its seamless integration with existing Google services like and search, leading to millions of users within the first year and positioning it as one of Google's fastest-growing products by 2006. This growth reflected broader industry trends toward personalized portals, as Google aimed to compete with established players like Yahoo's My Yahoo and Microsoft's by offering a more tailored aggregation of . The foundational design of the Personalized Homepage later evolved to include advanced features like gadgets for further customization.

Renaming and Major Updates

In 2007, Google rebranded its Google Personalized Homepage service to iGoogle, launching the updated version on May 1 to emphasize its role as a customizable personal portal and to drive greater user adoption by adding a prominent link on the main Google homepage. The name change, which rejected alternatives like "Yougle" or "Fusion," positioned iGoogle more distinctly within Google's ecosystem, attracting around 7 million monthly unique visitors shortly after relaunch. A major update in July 2008 integrated iGoogle more deeply with core Google services, introducing full-featured gadgets for , , and that allowed users to access these tools directly within the iGoogle interface, nearly replicating their standalone experiences. This convergence also added initial social capabilities, such as sharing updates with friends and a newsfeed for activity streams, enhancing iGoogle's appeal as a social hub. By 2011, amid Google's pivot to , these social features were deprecated in favor of the dedicated platform, with iGoogle's non-social elements preserved. Technical enhancements followed, with a beta release optimizing iGoogle for mobile devices like iPhones and Android handsets, incorporating tabs, quick access, and support for 38 languages to enable faster loading and usability even on slower networks. These improvements, including streamlined sidebar integration for services like Chat, reduced load times and expanded accessibility, contributing to sustained user engagement through the early .

Core Features

Personalization and Layout

iGoogle employed a tab-based layout that enabled users to create and manage multiple customizable tabs, allowing for the organization of diverse content streams such as , weather, and into distinct sections for easier and focus. This structure complemented the core page by providing a modular approach to content display, where each tab served as a dedicated canvas for selected elements. A key aspect of the layout was its drag-and-drop interface, which permitted users to rearrange modules and sections intuitively on the page, facilitating real-time adjustments to the and prioritization of information. This functionality extended to mobile views, where desktop configurations could be optimized for smaller screens by dragging gadgets into preferred orders. The platform integrated feeds directly into the layout, enabling users to aggregate and display dynamic content from external sources like news sites on their personalized pages. Additionally, results within iGoogle were personalized based on user preferences and search history, drawing from the user's to tailor relevance and suggestions. Users had options to set iGoogle as their default browser homepage and sync customizations across devices through their , ensuring consistent layouts and content access regardless of the platform. These features were enhanced through the addition of gadgets, which could be incorporated into tabs and rearranged as needed.

Gadgets and Widgets

Gadgets in iGoogle were modular, dynamic web applications built using the Google Gadgets , a framework that enabled developers to create lightweight and JavaScript-based widgets for embedding interactive content into personalized homepages. This facilitated the development and sharing of functional add-ons, such as real-time weather updates that displayed local forecasts, stock tickers showing live market data from major exchanges, and search tools allowing users to query auctions directly from their page. Developers could host these gadgets on Google's servers or third-party sites, with the providing built-in support for data fetching, user preferences, and rendering within iGoogle's layout, promoting widespread community contributions and reuse across web platforms. The iGoogle gallery served as a central directory, cataloging over user-created and official gadgets for easy discovery and addition to homepages. This vast repository included contributions from individual developers, teams, and partners, ranging from utility tools to options, all accessible through a searchable interface integrated into iGoogle settings. Users could browse categories like , , and to find and install gadgets with a single click, fostering a vibrant of shared content. Among the most popular gadgets were news aggregators, which embedded RSS feeds from sources like BBC or CNN to deliver customizable headlines and article previews that refreshed automatically, and mini-games such as puzzles or casual arcade titles that provided quick diversions without leaving the page. These gadgets were embedded as self-contained modules within the iGoogle canvas, leveraging the API for periodic updates— for example, a news aggregator might poll feeds every few minutes, while a mini-game could save progress via local storage proxies. Integration was seamless, with gadgets resizing dynamically to fit tabs or sections, and updates propagated through API calls to ensure content remained current without manual intervention. To safeguard users, the Google Gadgets enforced security features including a sandboxed execution environment that restricted gadgets' access to browser resources, external domains, and inter-gadget interactions, thereby preventing malicious scripts from compromising or the overall portal. limitations, such as proxied HTTP requests and whitelisted domains for cross-origin fetches, further mitigated risks like unauthorized or injection attacks, ensuring that even third-party gadgets adhered to strict isolation protocols. These measures allowed safe deployment of content while maintaining iGoogle's .

Themes and Customization

iGoogle offered users a vast collection of themes to personalize the visual appearance of their homepage, with over 360 options available by early 2008, encompassing designs created by Google and contributions from third-party designers through the iGoogle Themes API launched in January 2008. These themes included seasonal variations such as Winter Scape, which featured dynamic winter landscapes, and Seasonal Scape, designed to evoke changing times of year with evolving imagery. Celebrity-themed options were also prominent, with custom designs incorporating colors, patterns, and motifs from figures like fashion designer Tory Burch and musician Coldplay, allowing users to align their interface with popular cultural icons. Customization tools enabled users to tailor themes beyond selecting from the directory, including options to upload personal background images for the header (recommended at 640x175 pixels) and adjust color schemes for elements like header text and overall theme accents. Introduced in January 2009 via the official iGoogle Theme Creator tool, these features allowed real-time previews and simple edits directly in the browser, enhancing the ease of stylistic . While font adjustments were not explicitly supported in the core theme editor, the color and image modifications provided substantial flexibility in defining the page's aesthetic. Users could generate and share their own themes using the Theme Creator or by leveraging the Themes API to produce XML-based designs, which could then be submitted to Google's themes directory for broader availability to the iGoogle community. This ecosystem fostered creativity, with themes ranging from personal photo integrations to variable designs that adapted to time of day or location, promoting a sense of ownership over the interface. The emphasis on themes and visual customization significantly boosted user engagement, contributing to iGoogle's growth to over 20 million unique monthly visitors by April 2008, as options like these encouraged frequent returns and deeper interaction with the platform. By making the homepage a reflective extension of individual preferences, themes helped sustain daily active usage among millions, underscoring their role in iGoogle's appeal as a dynamic personal portal.

Experimental Developments

2008 Redesign Efforts

In mid-2008, Google began testing a redesigned version of iGoogle with a select group of users to modernize the interface and enhance social features. The test, which started rolling out in June 2008 and expanded in , introduced a left-side navigation panel for tabs, allowing expandable sections that displayed gadgets and status updates such as unread messages. It also integrated a persistent widget, pulling in online contacts from by default, and included a social updates feed aggregating content like stories, photos, and statuses. This phase emphasized compatibility with , Google's initiative to standardize social applications across platforms, with full support planned for later in the summer to enable developers to build interactive gadgets that accessed users' social networks. The redesign culminated in a full public rollout on October 16, 2008, which shifted tabs permanently to the left sidebar to free up more central space for content and introduced "canvas view" layouts. Canvas view allowed individual gadgets to expand into full-page experiences, supporting richer social applications through APIs, such as friend lists and activity updates integrated into widgets from partners like and . This update aligned iGoogle more closely with Google's broader social ecosystem, including tools like and Reader, aiming to transform the portal into a more dynamic rather than a static aggregator. However, the changes drew significant user backlash shortly after launch, with complaints centering on the left sidebar wasting valuable screen real estate, the removal of features like live links in the Gmail widget, and the lack of an opt-out option for the new layout. Users reported frustration over forced adoption without the ability to revert to the top-tab design, leading to a petition that garnered over 700 signatures within days and widespread discussions on Google forums. In response, Google monitored feedback and made partial adjustments, such as tweaks to widget functionality and eventual workarounds like accessing regional versions of iGoogle, though no full rollback was implemented. These issues highlighted tensions between innovation and user preference in the redesign process.

Apache Shindig

Apache Shindig was an open-source project initiated by in 2007, providing a downloadable package to enable users to create private, self-hosted instances of iGoogle-like personalized portals using OpenSocial-compatible gadgets. This release, centered around the Apache Shindig project, allowed organizations and developers to deploy the core technology stack independently of Google's hosted service. The package incorporated key components such as the gadget server for rendering and managing OpenSocial-compatible gadgets—similar to those used in the original iGoogle service—a proxy mechanism to securely fetch and display external content, and a theme engine for customizing visual layouts. These elements enabled the recreation of iGoogle's modular, widget-based interface in controlled environments. Targeted primarily at enterprises seeking to build portals with personalized dashboards and at developers aiming to extend or customize the platform, Apache Shindig facilitated offline or on-premises deployments without reliance on public internet services. For instance, companies could integrate it into internal networks to host custom gadgets for productivity tools. The initiative saw notable adoption, with the downloads and related resources accessed by thousands of developers and organizations during its active period. Community contributions, including code enhancements and bug fixes, were coordinated through the Apache incubator process, fostering improvements until the project's retirement in October 2015 due to inactivity.

Discontinuation and Shutdown

Announcement and Reasons

Google announced the discontinuation of iGoogle on July 3, 2012, as part of its ongoing product cleanup initiative launched in fall 2011 to retire or consolidate underutilized services and focus on higher-impact offerings. This effort had already addressed over 30 products by mid-2012, aiming to streamline 's portfolio and enhance innovation in core areas like search and mobile technologies. The primary reasons for ending iGoogle centered on the shifting landscape of web and mobile usage, where the need for aggregated portals had significantly eroded. stated that "with modern apps that run on platforms like Chrome and Android, the need for iGoogle has eroded over time," as users increasingly turned to dedicated applications for accessing content such as updates or feeds, rather than customizable widgets on a single homepage. Launched in , iGoogle's role as a personalized gateway became less essential in an era dominated by standalone services and mobile-first experiences. Internal communications via Google's official blog underscored a strategic emphasis on concentrating resources on products that drive broader user engagement and technological advancement, rather than maintaining legacy aggregation tools. This decision mirrored other service retirements in the cleanup wave, including the March 13, , announcement to shut down due to declining usage and a similar pivot toward fewer, more focused products.

Timeline and User Impact

The shutdown of iGoogle proceeded in phases to allow users time to adapt. Social features, powered by and integrated with services like , were disabled on January 15, 2012, as Google shifted focus to Google+ as its primary social platform. The mobile version of iGoogle, which provided a simplified interface for smartphone users, was retired on July 31, 2012, prompting affected users to rely on the desktop site or alternative mobile browsers until the full closure. The entire service was finally discontinued on November 1, 2013, after Google provided a 16-month notice period starting in July 2012. To ease the transition, Google offered migration tools that enabled users to export their personalized data, including gadget configurations in XML format for manual recreation on other platforms, and theme settings via built-in download options within iGoogle settings. Post-shutdown, any attempts to access iGoogle URLs automatically redirected visitors to the standard google.com homepage, preserving basic search functionality while ending all customization. User reactions to the discontinuation were notably vocal, with multiple online petitions circulating on platforms like and GoPetition, where thousands expressed dismay over losing a highly personalized start page that aggregated news, weather, and feeds in one place. Media outlets covered the backlash extensively, emphasizing the service's role in user productivity and the frustration among long-time users who had invested years in curating their layouts, often comparing it to the broader trend of consolidating products. Developers faced substantial challenges from the shutdown, particularly with the deprecation of the iGoogle Gadgets API, which had enabled the creation and distribution of over 100,000 third-party widgets for embedding content like stock tickers and social updates. This forced creators to port their tools to alternatives such as Netvibes or Symbaloo, disrupting workflows for those reliant on iGoogle's open development and leading to the of many custom applications.

Legacy and Successors

Influence on Web Portals

iGoogle pioneered the use of widget-based aggregation in personal web portals, enabling users to assemble customizable dashboards from modular components that pulled in real-time content from various sources. This approach directly influenced competitors, as evidenced by the collaborative development of in 2007, a set of open APIs spearheaded by and adopted by platforms like Yahoo! and to standardize social application development across sites. By integrating OpenSocial gadgets into iGoogle, demonstrated a scalable model for cross-platform interoperability, prompting Yahoo! to enhance its MyYahoo portal with similar widget functionalities and MySpace to incorporate OpenSocial for third-party app embedding, thereby shifting the industry toward more open and extensible portal architectures. The service also played a significant role in accelerating the adoption of RSS feeds and Ajax technologies in consumer-facing web applications during the mid-2000s. iGoogle's gadgets facilitated seamless integration, allowing users to subscribe to and aggregate feeds from news sites, blogs, and other content providers directly on their personalized homepage, which broadened RSS's reach beyond technical audiences to everyday users. Complementing this, iGoogle's Ajax-based architecture—launched in 2005—exemplified dynamic, responsive interfaces that updated content without full page reloads, building on Google's earlier Ajax innovations in and to normalize the technique in portal design and inspire similar implementations in competing services. Post-iGoogle's gadget model, industry adoption of open APIs surged, with serving as a foundational standard that enabled several social networks and portals to host compatible applications by , fostering an ecosystem where developers could create once and deploy widely without proprietary lock-in. This shift marked a broader trend toward API-driven , reducing barriers for content syndication and third-party integrations in web portals. Culturally, iGoogle left a lasting imprint as the archetype of a "digital dashboard," a frequently invoked in technology literature to describe integrated, user-centric aggregation tools that centralized web experiences. Its emphasis on modular customization resonated in discussions of early ideals, positioning iGoogle as a seminal example of how portals could evolve into personal information hubs, influencing subsequent conceptualizations of dashboard-style interfaces in both consumer and .

Post-Discontinuation Alternatives

Following iGoogle's discontinuation in 2013, Google promoted Google Now, launched in 2012 as part of the Android operating system, as a key alternative for delivering personalized content. Google Now provided context-aware "cards" with information such as weather updates, traffic alerts, and news feeds tailored to user location, search history, and interests, accessible via the Google app or search page. This service evolved into Google Feed and eventually Google Discover in 2018, which offers a swipeable, algorithm-driven feed of articles, videos, and recommendations based on browsing behavior, integrated into the Google mobile app and Chrome browser. Google Discover emphasizes real-time personalization without requiring manual gadget setup, filling the void for dynamic content aggregation. Third-party services quickly emerged to replicate iGoogle's gadget-based customization. Protopage, praised for its clean design and feed integration, allowed users to create modular homepages with widgets for , , and bookmarks, positioning itself as a direct successor. Netvibes offered advanced features, including multi-tab layouts and streams, specifically marketing a "G Refugee" mode to ease iGoogle transitions. These platforms adopted iGoogle-like systems, enabling users to import feeds and themes for seamless continuity. In 2022, experimented with reintroducing widget-like elements on its desktop homepage, testing customizable info cards for , , and below the search bar. This trial, observed in early 2022 and expanded by August, aimed to blend personalized snippets into the core Google.com experience without a full portal revival. Post-shutdown analyses indicated users increasingly shifted to browser extensions like Awesome New Tab Page for Chrome, which replicated gadget functionality, and mobile apps for on-the-go personalization by 2014. Contemporary reviews noted a trend toward these lighter, integrated tools over standalone portals.

References

  1. https://googleblog.blogspot.com/2005/05/method-to-our-madness.html
  2. https://googleblog.blogspot.com/2007/04/youve-got-gadget-mail.html
  3. https://googleblog.blogspot.com/2007/10/get-your-igoogle-in-42-languages.html
  4. https://googleblog.blogspot.com/2008/10/whats-new-with-igoogle.html
  5. http://googlesystem.blogspot.com/2008/11/google-chat-in-igoogle-and-orkut.html
  6. https://googleblog.blogspot.com/2009/03/igoogles-got-game-themes.html
  7. https://googleblog.blogspot.com/2009/08/i-scream-you-scream-we-all-scream-for.html
  8. https://blog.google/inside-google/company-announcements/spring-cleaning-in-summer/
  9. https://www.cnet.com/tech/services-and-software/google-introduces-personalized-home-pages/
  10. https://www.nytimes.com/2005/05/20/technology/google-moves-to-challenge-web-portals.html
  11. https://betanews.com/2005/05/20/google-offers-personalized-homepage/
  12. https://techcrunch.com/2005/12/14/googles-ajax-desktop-is-now-extensible/
  13. https://searchengineland.com/igoogle-personalized-search-and-you-11109
  14. http://blogoscoped.com/archive/2007-04-30-n90.html
  15. https://techcrunch.com/2007/04/30/rebrand-new-features-google-ig-to-relaunch-as-igoogle/
  16. https://www.informationweek.com/it-leadership/google-to-launch-igoogle
  17. http://googlesystem.blogspot.com/2008/07/googles-services-converge-in-new.html
  18. https://googleblog.blogspot.com/2011/10/fall-sweep.html
  19. https://www.techpartner.news/news/google-updates-igoogle-for-iphone-and-android-handsets-147583
  20. https://googleblog.blogspot.com/2007/10/api-gadgets-and-tabs-oh-my.html
  21. http://googlemobile.blogspot.com/2008/06/mobile-search-access-gets-faster.html
  22. https://googleblog.blogspot.com/2007/02/personally-speaking.html
  23. https://developers.google.com/workspace/sites/gadgets/site_gadgets
  24. https://googleblog.blogspot.com/2007/06/ga-ga-for-gadgets.html
  25. https://www.eweek.com/it-management/google-buys-game-maker-labpixies-to-boost-igoogle-in-emea/
  26. https://www.cnet.com/culture/goss-new-linux-os-embraces-google-applications/
  27. https://www.findmysoft.com/news/google-rolls-out-digg-reminiscent-igoogle-gadget-what-s-popular/
  28. https://www.pcworld.com/article/524900/first_look_igoogles_new_social_gadgets.html
  29. https://developer.atlassian.com/server/framework/gadgets/hints-for-developing-in-igoogle-sandbox/
  30. https://www.youtube.com/watch?v=H6KVwATfCdM
  31. http://googlesystem.blogspot.com/2008/03/search-for-igoogle-themes.html
  32. http://googlesystem.blogspot.com/2007/12/igoogle-winter-theme.html
  33. https://blogoscoped.com/archive/2007-10-30-n63.html
  34. https://www.nytimes.com/2008/06/01/magazine/01wwln-medium-t.html
  35. https://googleblog.blogspot.com/2009/01/making-your-personalized-homepage-even.html
  36. http://googlesystem.blogspot.com/2008/05/igoogle-more-profitable-google-homepage.html
  37. http://googlesystem.blogspot.com/2008/06/google-tests-new-igoogle.html
  38. https://techcrunch.com/2008/10/16/igoogle-goes-wide-introduces-canvas-pages/
  39. http://googlesystem.blogspot.com/2008/10/new-igoogle-publicly-launched.html
  40. https://www.wired.com/2008/10/igoogle-redesign-triggers-user-outrage/
  41. https://www.10zenmonkeys.com/2008/10/19/the-great-google-rebellion/
  42. https://shindig.apache.org/
  43. https://bitbucket.org/atlassian/apache-shindig/downloads/?tab=tags
  44. https://shindig.apache.org/about_shindig_overview.html
  45. https://stackoverflow.com/questions/3506455/igoogle-platform-for-intranet-page
  46. https://whimsy.apache.org/board/minutes/Shindig.html
  47. https://attic.apache.org/projects/shindig.html
  48. https://phys.org/news/2012-07-igoogle-axed-shakeup.html
  49. http://googlereader.blogspot.com/2013/03/powering-down-google-reader.html
  50. http://googlesystem.blogspot.com/2012/08/no-more-mobile-igoogle.html
  51. https://www.ghacks.net/2013/11/01/goodbye-igoogle-time-come/
  52. https://www.change.org/petitions/google-don-t-kill-igoogle
  53. https://www.seroundtable.com/igoogle-sunset-revolt-15388.html
  54. https://www.cbsnews.com/news/google-phasing-out-igoogle-homepages/
  55. https://www.ghacks.net/2012/07/03/google-to-retire-igoogle-on-november-1-2013/
  56. http://googlepress.blogspot.com/2007/11/google-launches-opensocial-to-spread_01.html
  57. https://www.zdnet.com/article/googles-opensocial-apis-pick-up-steam-myspace-and-bebo/
  58. https://arstechnica.com/uncategorized/2007/04/google-releases-ajax-api-for-rss-mashups/
  59. https://www.heise.de/en/news/20-years-ago-AJAX-revolutionizes-web-development-10285844.html
  60. https://core.ac.uk/download/pdf/250105114.pdf
  61. https://vdoc.pub/documents/fundamentals-of-information-systems-41g3i0mdfm10
  62. https://arstechnica.com/information-technology/2013/04/google-now-may-actually-be-the-igoogle-replacement-youve-been-waiting-for/
  63. https://gcemetery.co/igoogle-alternatives
  64. https://www.theguardian.com/technology/askjack/2013/nov/07/igoogle-alternatives
  65. https://arstechnica.com/gadgets/2022/02/google-search-channels-yahoo-com-tests-news-and-weather-on-the-homepage/
  66. https://www.androidcentral.com/apps-software/google-search-desktop-widgets-test
  67. https://www.cnet.com/tech/services-and-software/best-igoogle-alternatives/
  68. https://www.computerworld.com/article/1389598/5-great-replacements-for-igoogle.html
Add your contribution
Related Hubs
User Avatar
No comments yet.