Hello.

I'm starting a project to document web technologies that didn't become mainstream. For every success story, countless others fade away. I want to explore these untold stories, starting with my own experience with Web Intents. I aim to understand why some projects thrive while others don't, and share these learnings with the community. If you have a similar story, please reach out!

The pace of change in web development, particularly with APIs and browser updates, is overwhelming. The constant deprecation and breaking changes cause friction and highlight a lack of empathy for developers struggling to keep up. While frequent updates are important, the current model, exemplified by Chrome, feels too aggressive. This blog post will explore this tension, examining whether we've pushed developers too far, and discuss strategies for a more sustainable pace of change. It will also touch on platform-specific resources like web.dev and the challenge of balancing innovation with support for the broader developer community.

The web's organic growth, with examples like Google Maps' early API and widespread embeddability, leads to questions about its current design. Would we recreate this structure today? Likely not. This suggests a need for change and migration, but how can this complex transition be managed effectively, especially considering the scale and interconnectedness of the web?

Apple has a clever naming strategy with "The New iPad." Customers naturally ask for the "new" version of products, avoiding confusion and instantly clarifying which model they want. This approach bypasses complex product names and generations. I predict Apple will continue this with other products like the iPhone, simplifying their branding and customer experience.

I've always been a fan of Yahoo's developer APIs due to their generous usage limits and flexible terms. However, recent changes to their T&Cs are concerning. They now prohibit displaying ads alongside Yahoo API results unless they're Yahoo Ads, and they forbid showing Yahoo search results next to other search engines' results. This impacts sites like Topicala.com and gada.be, as well as many example applications using Google AdSense. While their RSS feed search terms seem more lenient, allowing aggregation with other results and ads, the overall tightening of restrictions stifles innovation. I've updated Topicala.com to use the RSS feed as a workaround. I'm disappointed with Yahoo's approach, as proper attribution should be sufficient, especially when sites like mine prioritize Yahoo results. Until the licensing becomes more flexible, I can't recommend Yahoo's APIs.

In this installment, I reflect on the limitations of Blogger.com as a blogging platform. Despite its user-friendliness, several features fall short of my needs. The "Blogger For Microsoft Word" integration isn't particularly helpful, the WYSIWYG editor is inconsistent, and the available tags seem outdated. I crave more innovation, especially regarding feed customization and ping configuration. While AudioBlogging.com intrigues me, its practicality for someone in the UK is questionable. Ultimately, I desire greater control and configurability, but acknowledge Blogger's value as a free service.

I believe retailers need to embrace open APIs to their product catalogs and ordering systems to reach a wider audience. While I agree with Robert Scoble's view on the transformative potential of developer APIs in retail, I'm concerned about the slow pace of change. Costly per-call charges for APIs like eBay's hinder experimentation and development, especially for independent developers like myself. It's also difficult to find retailers who openly offer APIs. Amazon's free access model is a good example of how APIs can drive revenue. Are there any UK retailers offering cool, accessible web services?