iConverged

I finally get why people tweet. It lets you speak your mind the way it is, without requiring you to make a paragraph out of it. When I blog, I think, then form, then rehearse then post. When I tweet, I think and tweet. The link between my thoughts and the tweets is more direct. And of course, very often, I don’t have paragraphs to talk about, but still experience exciting new things that can be written in 3 lines. So now I understand the subtle difference of tweeting vs blogging. I’ve wiped the dust off my twitter account. I will use that more often now. I will still occasionally post, but only if I have lots to say.

Follow on at http://twitter.com/arjunrc

After 4 years of serious Blackberry 8700 and 8800 use, my wife convinced me to switch to the sexier iphone. I was pretty wary knowing it is not very good for business usage. However, my wife’s prime interest was to get me off the keypad while driving. To her dismay, I am now an expert fast typist on my iphone virtual keyboard – but I do listen to her and for my own safety don’t thumb responses to email while stopping at a light. Here are my experiences (so far) on what I did to bring my iphone closer to my needs. I have the iphone 32G 3GS. My previous phone was the wonderful, but, well not oomphy BB 8800.

Read the rest of this entry »

There has been a lot of posts and flutter on Google’s new purported Chrome OS and how it will be a great battle with Microsoft, how it will confuse and/or kill Android etc. And also, of course, taking off from the Google Blog on Chrome OS “For application developers, the web is the platform. All web-based applications will automatically work and new applications can be written using your favorite web technologies” people are also throwing in “Web OS” everywhere.

I thought I’d write a post detailing my thoughts (technical) on this entire issue.

Read the rest of this entry »

I’ve always believed the concept of location is important to an application, but it does not really define an application. Continuing that line of thought, I think many companies who join the ‘LBS is a killer Application’ idealogy have it completely wrong.

Location is NOT going to be successful as an Application. It is going to be super successful as a tool. Let me justify my stand.

Read the rest of this entry »

So the rumors of many years ago were true. Google finally did release a browser. Naturally, I downloaded it and took it for a test drive. Here is the short of it.

Version reviewed:

Google may be rolling out updates regularly (For example, I suddenly see evident popup blocking), so to put it in context, this is the version I am reviewing

Installation:

The installer is just around 470K to download, but of course that is the ‘pre-installer’. Once you grab the pre-installer, it downloads the rest of the browser from the net. As of now, in its first release, focus seems to be on super simplicity. It does not even ask you where to install it. I am OK with that, but it really does choose a weird location to install it (in Documents and Settings!)

(click on any image to see a full size version)

Read the rest of this entry »

Image credit

Yahoo recently launched Fire-Eagle, which is essentially an ‘open platform’ that allows two simple things:

A) Users can update the system whenever they want with their location

B) Application Developers can access the system whenever they want to know the location of consumers and do anything with it (i.e. serve any application that can make use of that information)

Of course, ‘Users’ can explictly set permissions on who can or cannot view their location.

For a long time, I have wanted to see such an open and simple platform, where ‘executing a service based on location’ is completely independent of ‘the technology used to provide the location’. Because I believe providing individually accessible repositories of data is the key construct to building a hierarchy of innovative products. You collect data, expose it to others so they can transform your data into information. And your information, is data for the next application. So turns the wheel of the Web 2.0 circle. And a location repository is one key missing element to personalize services.

Read the rest of this entry »

If you are in this emerging ‘applications’ market, and are in the business of building applications for OEMs/ISVs or Service Providers (yes, some Operators actively invest in R&D work), the term ‘Rapid Prototype’ is not new to you. In short, people are always looking at ‘quick and dirty’ demonstration code that shows off a cool concept which they can take to prospective customers as a viable product or service to be rolled out. Customers who ask for this are not sure if that idea will go anywhere, but are willing to test the waters with you (if you are willing). A typical software development organization follows the ‘Build Rome one stone at a time’ model whereas this particular market needs the ‘pre-fab modular home in 1 month’ model and therefore struggles with this particular market. I know of many organizations who  believe this is not an area to be in, because of the limited scope and length of such projects. The problem however, is that they fail to understand that this market is actually very attractive and profitable, but only if you look at it the right way, and approach it the right way. Last week, I was chatting up with a friend on the same issue and was sharing some insights into what one should try and institute to make this model work. He suggested a blog post, so here goes – some common problems, pitfalls and solutions:

Read the rest of this entry »

I had the opportunity to do a sneak preview of Microsoft’s popfly mashup platform a few months ago. Based on the quick look, at that point of time, it was just a prettier looking  version of Yahoo! Pipes. However, another peek a few months later and I am much more impressed. I must admit that till now, of all the mashup editors I have evaluated, Google Mashup Editor has been my favorite. And that was because I truly feel powerful mashups which are globally useful will be written by developers, not my grandmom, so the interface need to provide more powers and not just pretty ‘connectors’.

I must admit, Popfly on second look has good potential.

So here is my quick analysis of why I think it is like Pipes, like GME, like Facebook and somewhat different. In other words, I think Microsoft has been watching how the others do it, and picked some good features from all, along with some very irritating ones.

Read the rest of this entry »

Update: I have now created a sidebar widget titled “Tech Blogs I read” instead of updating this post. Please continue sending me quality tech blogs (with more focus on concepts and less on marketing) as you come across them and refer to the sidebar for updates and not this post – thx.

Total number of ‘market reporting’ VoIP blogs = k+1

where k=number of times you can blink in a day.

However, there are very few blogs that talk about more technology & architecture details and less market details for all things VoIP, SIP, IMS, web 2.0 (with focus on telecom).

So here is a call to unite!

We need a list of what I call ‘geek-talk’ – those that provide more technical insight into how things are.

Here is my list so far. Please update me /comment here with more tech-blogs and I will update this list

Many of these blogs are a mix of techno-marketing, but are written by people who are neck-deep in actually developing/architecting many of the talked about solutions themselves, and hence offer a more detailed insight.

last updated: Apr-30-2008

1. TurnGeek – focus on P2P, SBC, etc.
2. IMS Lantern – IMS architecture related
3. Voice of VoIPSA – VoIP Security
4. IMS Quality – Testing and Monitoring with focus on IMS
5. VoIP Survivor – general voip, with significant focus on their company products
6. TelCAB – IMS B/OSS
7. iConverged - this blog

I recently wrote a paper that investigates how SDP vendors can provide AJAX based telco-aware libraries and mechanisms to interface these libraries with existing telecom application servers. I personally believe that this is a gaping hole in the market. While AJAX libraries have evolved significantly, no one is currently working on adding functionality that makes it telecom aware (in terms of understanding what UI, actions, events are typically associated with telco services) thereby making t he job much harder on developers who are trying to grapple with what it really means to “web 2.0″ their SIP call control app.

Abstract:

With the increasing acceptance of AJAX as a mechanism to deliver real-time user experiences without the need of proprietary local clients and the increasing demand from consumers to have a better user experience with more features, both the Telecom and the Internet world are looking at means to be able to converge their offerings. However, being able to provide converged services is a challenge largely due to the fact that Telecom players already have existing applications they would like to monetize in addition to having limited know-how of Web 2.0 related technologies, whereas the Internet players, while proficient in Web 2.0 technologies have limited understanding of wireline and wireless networks to be able to offer ubiquitous service access. The author believes that middleware SDP providers can help bridge this gap and provide “convergence” building blocks that would allow developers on both sides of the world develop functionality, or integrate existing functionality with ease. Specifically, this paper, proposes the concept of “TelcoAJAX” – a set of building blocks that are aware of telecom primitives and how to represent and interact with users using a browser interface which developers can implement on top of SIP/Presence based applications.

You can download it from here.

(Search for paper titled “A Concept Approach at bringing Legacy Telecom Application Servers to Web 2.0″)