May 20th, 2010 — Development, News
I’m really pleased with the announcement of open access to Wave for all at the opening keynote at Google IO.
The IO team at the fireside.
The part that we are most interested in is that wave is availed on my domain, like all the other Google apps. We covered this earlier on Testing Google Wave for Apps. So that means that everyone can start to use wave for organizing their organization. I really believe that there is a large potential for using Wave in organizations instead of using mail to all communication. I have in countless examples seen email been used where wave would have made decisions would have been made much easier.
With our product caseish, that helps you and your group can get at much better insight on what is going on with your status. We see that there is a fantastic opportunity for selling our application on the Google Apps Market place, because we support organization or groups collaborate better. With the apps market place we are able to monetize our application fairly easy since we just need to connect to the apps market place and then we can start with getting customers aboard. We though still need a little way to go before we are ready to launch to the apps market place.
I had also hoped that there would be an announcement on a Wave marketplace, so it also was possible to sell apps to individuals like games or other features. I talked with the Wave team and found that the issue they had with it was the complexity of how such a market place should work. There are defiantly a lot of legal issues that needs to be addressed before it is possible to sell application for Wave on that account.
There was also all the API changes that I’m going to look into in the coming weeks.
May 19th, 2010 — Development, Enterprise, News
Just checked Google I/O’s Developer Sandbox and it’s great to see that many companies and developers are taking part in further developing better and more helpful applications in Google Wave.
The Developer Sandbox serves as a demo area which allows developers to present new applications and share their ideas to enhance Google Wave.
Here are a few of the companies who will be participating:
Novell is one leading provider of infrastructure software which aims in offering unique solutions to help people create, share ideas and work together easily.
ProcessOne is a company which specialises in developing instant messaging servers – solutions which are ideal for critical business applications.
SAP is a company which delivers useful products and services which cater accelerating business innovations.
Caseish is given the chance to participate. And, with this opportunity, I will be presenting our own applications namely, Google Wave Robots and API to integrate with Wave, AppEngine to control the robot and Google Visualization API to display graphs.
To see all the companies who will be participating, see Google I/O’s Developer Sandbox.
Keep posted for some videos on this event.
May 19th, 2010 — Beginner, News
The last period has been quite hectic. My team and I have been working on creating a release version of Caseish. Unfortunately, we have not yet succeeded in achieving all the goals that we had created. But, we are still on the positive side and there will always be room for improvements.
We have developed Caseish as a tool for organizing your Waves in an easy-to-create way. Here, is a demo of Caseish in the video below.
We will be presenting the application at Google IO developer sandbox. Come by and have a talk about the application and give some feedback on what you think of this tool. If you are not at Google IO, you can tweet us at http://twitter.com/caseish or Wave us at firstname.lastname@example.org.
During my time at IO, I hope to record some of what other developers have already done and share those with you. I’m looking forward to see what is current and what new improvements they are going to announce.
To learn more about Caseish and sign-up for the beta, see http://www.caseish.com.
May 18th, 2010 — Development, News
Other nice features of Google Wave are now released! These are three new features created for Robots API namely: Bundled Annotations, Inline Blips, and Read-Only Roles.
- Allows you to specify both the content to append and the annotation(s) to apply to content itself, all at the same action
- This is a new attribute to the Blip classes to let robots access the positions of inline blips inside other blips
- Lets the creator of a wave set access rights for the other participants as either “full access” (the default) or “read only”
- Read-only participants are forbidden to make alterations on the wave but given the permission to see live changes on the wave and its history
For a more detailed view on these key features, visit announcement wave.
May 18th, 2010 — Beginner, Development, Enterprise, News
I have had the opportunity to try out wave for my domain for the last couple weeks. I have used it on masteringwave.com. It has been a really nice experience and looks like it will propel wave in to the business side.
First Waves has already covered some of the functionality at with their post Google Wave Available to 31000 University Students. Where they talk about a university using Wave and show some screenshots.
I have been using wave to organize my team’s efforts since we got started using the preview version of Wave. But it did lack some features that are really nice in organizational perspectives.
It is still in preview and there will be more changes to the wave system. So it is likely to change in the future.
I really like the way the group function. All your mail groups can be used as groups in wave. It seems like the groups are using groups for apps, if such a thing exists. It is nice that you only have to provision the users on place.
It is possible to see when you are Waveing with people outside of the domain. This is really nice feature, and allows you to see if it is a private conversation you are having.
Also as with Wave you get your whole address book, so you can communicate with the people on your list.
It is of course to communicate outside of your own domain with other domains. I have not yet configured anything in my DNS to allow this type of wave communication. I guess that it has to be configured the same wave you configure your mail domain. But since there are no third party waves out there yet the configuration is probably quite minimal.
We got access to see how it was to develop apps for a hosted wave service. It is quite possible, but we still have some issues that we need to figure out how to manage before we start using it to the public. But basically wave works just the same way, it is just not sure that all participants are from the domain googlewave.com anymore. So if that is hard coded in any robot/gadgets it should be removed.
We used Google single sign on to make it possible to sign-up to log on to our service. For this to work properly, our app needs to be a part of the Apps Marketplace.
When you create a wave in the domain, the wave id will be prefixed with the wave id. The Wave id is then longer then the waves from googlewave.com. It is a question if those waves also will be prefixed to fit into the structure. So, when all waves need to be prefixed with the domains, then all the current waves will not work. I suspect there will be a solution for this.
For the usability part of the application, it is really nice to just have one place where all communication, both for guidelines and day to day communication.
On Google IO we will be releasing our caseish.com app. Stay tuned to learn more on how that will help you.