Skip to main content

Mobomo webinars-now on demand! | learn more.

Barg Upender, Mobomo Founder and CEOAffiliate Summit West, the premier affiliate marketing conference, is taking place January 9-11, 2011 at Wynn Las Vegas.

This three day conference includes multiple tracks of educational sessions covering the latest trends and information from affiliate marketing experts. Barg Upender, Mobomo's founder and CEO will be a panelist at the event discussing marketing trends in mobile eCommerce.

Register for the conference here: http://www.affiliatesummit.com/

Categories
Tags
Author

Mobomo was contracted by independent artist Alan J. Lipman to develop a iPad music app as a companion to his website (www.x-patriate.com) and music published on iTunes. The app streams music, provides lyrics, and enables users to purchase music from iTunes and share content with friends via email, Facebook, Twitter, Digg, etc.

X-Patriate iPad App
X-Patriate iPad App
Categories
Tags
Author

The Gartner Group recently published a report that shows the increase in worldwide phone sales and it's significant. For all types of mobile phones, sales went up by 35% in Q3 2010 from Q3 2009. Of that, the smartphone segment had a whopping 96% increase in sales. But what do those figures mean? How can your business benefit from this?

Those numbers might be a bit deceptive, but they do point to an important increase in smartphone sales. That 96% quarterly increase in smartphone sales might only amount to 19% of overall mobile phone sales in Q3 2010, though that translates to nearly 80M new units of smartphones worldwide -- a huge new market for your mobile apps. According to the Gartner Group report, Apple especially benefited in Q3 2010, moving into the top five manufacturers, surpassing RIM. (Apple's iOS and Google's Android are still battling in the top two places for Mobile OS, though Apple's iPhone 4 is dominating in smartphone sales in the U.S.)

Now pair this smartphone sales information with the MMA (Mobile Marketing Association) report, "October 2010 U.S. Mobile Consumer Briefing," whose survey results suggest that nearly 60% of mobile consumers will use their phone for holiday shopping and planning. This includes using their phone for planning holiday celebrations, finding holiday gifts, comparing their spending expectations between 2009 and 2010, making purchases and more. In fact, at least 13% of consumers surveyed also expect to use their phone for gift purchases.

Positive Impact on Your Business
It's true that countries in Europe and Asia have been using their mobile phones for product/ service payments for years, though this is a newer use for N. Americans. Consumers are obviously feeling increasingly comfortable in using mobile phones for shopping-related tasks in general, and with the ability of apps running on smartphones, the consumer shopping experience will continue to improve. As more consumers grow comfortable using smartphone apps for shopping, such apps will be commonplace for more than just holiday use -- especially as the use by retailers of barcode/ QR code-based mobile coupon offers grows.

Mobile apps allow shoppers the convenience of checking for both local and online bargains, comparing, saving details, receiving alerts about deals, and much more. If this convenience is something that you want to offer your mobilized customers, start planning a mobile strategy now, for 2011. Especially consider how your target market could benefit from a mobile app. Start with a fairly simple mobile app and be first in your niche or industry, to gain an advantage over competitors in coming years. Add new features to your app regularly, as its usage grows.

Want to learn more about how a mobile app can help your business? Feel free to contact us to discuss a strategy.

Categories
Author

He first learned to program on the side of an extinct volcano, trained in the Suzuki method from a young age, and describes Ruby as "mana from heaven." This week, in the Intridea Insider, meet Sean Soper, Software Architect at Intridea.

Sean started programming during the time he spent living on the side of an extinct volcano in Naples, Italy when he was twelve years old. "My Dad was a civilian contractor for the Navy. We didn't live on base, but on the side of this old volcano. There were no other kids around." When his parents bought an old Packard Bell PB500, "with a 8088 processor", he spent a lot of time with the computer for lack of other entertainment. "The installed apps bored me pretty quickly so I started writing my own. I probably read the entirety of GORILLA.BAS at least five times, which was significant given that it was about 5000 lines of code."

Aside from playing violin which was Sean's other passion as a kid, he spent a substantial amount of time on the computer. He programmed in Basic, Pascal, and of course his TI-85, before later studying Computer Science, History and Anthropology at Purdue University.

He discovered Ruby and Ruby on Rails a few years later while working in an IT position at a health insurance company in Florida in 2005. "I was told that I needed to re-do their health portal which had been done using J2EE by three previous employees. But I was just one guy, so I started looking at what technology was available, and I stumbled upon Ruby on Rails." After getting approval from management, in just a few months time he had recreated a significant portion of their health portal, and was nearly finished when the company hired new management.

Sean had been patiently persevering through IT positions since graduating from Purdue in 2002. His heart was in programming, but the dot com bust made the software industry impenetrable to him. Discovering Ruby on Rails only made him more tenacious in his desire to do full-time software development. "I was blown away by Ruby and Ruby on Rails. It was pure mana from heaven. I knew then and there that I wanted to do pure software development; like the goldfish that had grown too large for his bowl, I knew that IT would never be enough for me." During this time of frenzied growth as a burgeoning Ruby on Rails developer, he did his best to document his learning process on his blog.

Sean's experience with RoR opportunely landed him a spot at Revolution Health, Steve Case's healthcare reform startup in Washington, D.C. "After the company in Florida changed up their management, they wanted me to go back to configuring installations and working strictly in IT." When he got a call from a recruiter at Revolution Health, he didn't have to give it much thought before jumping on board with the company that was "vacuuming up every Ruby dev on the East coast." He describes working at Revolution:

Sean on Finding Ruby

"I finally felt that I'd arrived where I was meant to be. I was doing pure software development in a company made up of mostly other developers. It was the startup we were all promised we would work at back in the early 2000's in college."

His passion for development was nurtured in this fast-paced startup environment. "My experience there only inspired me to learn more. I started attending NovaRUG and NovaLang. I was introduced to core concepts that for some reason, were not taught in college. When I was in college they had already switched out to object oriented programming, and functional programming was seen as a weird science project. But Ruby by its very nature is both object oriented and functional. I entered this entire universe of programming that I didn't know about before, and I have Ruby to thank for that. It completely changed the way I code."

The Ruby community (within Revolution, NovaRUG, NovaLang and online communities) was a fertile ecosystem that nurtured growing Rubyists. Sean says that he's never found a community like this around other languages that he has programmed in. "When I needed help in other languages I'd stumble upon some expert's exchange post or a forum where people begged for help and maybe, just maybe got an answer. But with Ruby, folks built on those answers. It felt like a real community rather than a mob."

It was difficult for Sean to leave Revolution in late 2008. But with rumors of the company downsizing he turned his attention to BrowserMedia, a gig that gave him the opportunity to learn Objective-C and do iPhone development.

When he transitioned to Intridea the following year, his first project was HowAboutWe.com; "That project was a blast, especially working with Flip Sasser. I thought, 'if everyone is half as cool as this guy, this has got to be the best company ever.'" Sean has moved since into full-time mobile development at Intridea and he loves it. Earlier this year he worked on Oil Reporter, a crisis response app built in just three days, for the Deep Horizon oil spill disaster. His work on Oil Reporter landed him a spot on stage at TEDxOilSpill in DC this summer, where he presented the application to an audience of brilliant engineers, scientists, environmentalists and NGOs. Sean, not normally big on public speaking, was nervous to go on stage at TEDx. And despite some technical difficulties with the wifi during his presentation, his work was well received by the audience - and the confirmation gave him the courage to do a lightning talk at the Ruby Hoedown later that summer.

Sean enjoys going to the big conferences, but he still relies heavily on the Ruby community in the greater DC area. "I look to the small conferences and user groups to see what's coming down the pipe, because honestly, before these guys go to the big conferences they try out their stuff at the small local places. And the DC area is a great place for innovation right now." Now that he works from home most of the time he also depends on sources like RubyFlow and Twitter to stay afloat of Ruby related news. "My twitter feed is full of great local Rubyists who are always tweeting about the latest and greatest stuff. And over the years I've ended up working with most of them too."

Sean was recently married to his wife Sabrina in April of this year. He met her when they both worked at Revolution Health and they bought their first house last November in an established neighborhood in Maryland. They share their home with their cat, Ice. Sabrina works for Comcast along with several former colleagues from Revolution. Their wedding was in Maryland, but the ceremony was inspired by his wife's Taiwanese heritage. He flew to Taiwan last year, along with her family, to get his changshan (??), a traditional Chinese garment, for their wedding.

Sean travels in to the Intridea office 2-3 times a week because he enjoys being in D.C. but says that, "overall, I like working at home. Without the 45 minute commute I feel like I can get 90 minutes more work done!" Sean explains that working from home for a company like Intridea is what you make of it; for him, his work is also his reputation, so if he wakes up on Saturday morning with a solution to a problem he was working on the week before, he won't hesitate to sit down at 7am and start coding out the solution. "In a traditional work setting I would normally say, 'eh, it can wait until Monday.'" But Intridea's developers approach their work with a striking amount of passion, and the lines between work, home, and fun are often blurred.

While Sean certainly works a great deal, he insists that he does have hobbies outside of programming. "My non-computer hobby is canning and preserving. So much of what we eat is all the result of humans trying to preserve food longer than it was meant to be stored." This year he turned the tomato yield from his wife's garden into sun dried tomatoes, and canned a large batch of dill pickles. He also spends a lot of time working on his house with Sabrina. "The house, at 40 years old, is in good shape, but the previous owners stopped updating it during the Ford administration. Think earthy taupe colors. And horribad wallpaper." His current project is installing hardwood floors and recessed lighting in his home office. He's also a political junkie, and spends time on sites like Memeorandum for his fix.

Sean grew up idyllic Carlsbad, California. "Crime was nearly unheard of, the beach was nearby. For many people it was paradise. Yet at times I felt like that small town kid that needed to get out and explore a big city." Now, Sean lives and works in and around D.C., arguably one of the coolest cities in the United States. As for Ruby's role in all of this, he says, "I'd still be writing Java XML configuration files in some backwater IT department if it weren't for Ruby."

The best thing about working at Intridea for Sean, aside from programming, and being able to work from home is the people. "I love the vast collection of talent that I can ping at any moment if need be. I never feel separated from the rest of the company despite that we rarely see each other face to face."

Since Intridea hires some of the best Ruby, Rails and mobile devs across the country, Intrideans all partake in the benefits of being able to work with other talented people no matter where we live. People just like Sean. In a way, Ruby really has been "mana from heaven" for many of us. It has united our individual talents into a collective tapestry, while allowing us to work, live and play from the unique places that we all call home.

Categories
Author

So, yesterday was Microsoft's big launch of Windows Phone 7 in North America, and although official sales numbers have not been published, there is already a shortage of Windows Phone 7 devices in Europe. Mobomo has been working with the device for over a month now and we are preparing to launch a few federal apps before the end of the calendar year.

Recalls App for Windows Phone 7
Recalls App for Windows Phone 7

Our first impressions of the device is that it will be a strong contender. The completely redesigned user interface is pleasant and responsive making it as nice an experience as the iPhone. At the same time, it blends this experience with enterprise e-mail, Microsoft Office, and Microsoft Sharepoint integration competing with Blackberry as a business phone. Finally, Microsofts commitment to integrating Windows Phone device management into enterprise management tools traditionally used to manage desktops will make the Windows Mobile phone appealing to corporate environments in addition to general consumers.

From a development standpoint, the SDK has been easy-to-use and despite the need for some refinement in future releases, is easy for developers to come up to speed on (especially if already well versed in .NET and Silverlight). While developing the Recalls app, we did run into some minor platform configuration issues, but the community is quite active and we were able to quickly resolve issues with the growing population of developers.

Overall, we believe Microsoft has a winning platform with Windows Phone 7 that will enjoy success comparable to Android and iPhone mobile devices.

Our first impressions of the device is that it will be a strong contender. The completely redesigned user interface is pleasant and responsive, making it as nice an experience as the iPhone. At the same time, it blends this experience with enterprise e-mail, Microsoft Office, and Microsoft Sharepoint integration competing with Blackberry as a business phone. Finally, Microsoft's commitment to integrating Windows Phone device management into enterprise management tools traditionally used to manage desktops will make the Windows Mobile phone appealing to corporate environments as well as general consumers. While there are still small nuances with the device, Microsoft has done a great job for the first release.

From a development standpoint, the SDK has been easy-to-use, and it is easy for developers to come up to speed on (especially if already well versed in .NET and Silverlight). During our past month of development, we did run into some minor platform configuration issues, but the community is quite active and we were able to quickly resolve issues with the growing population of developers.

Overall, we believe Microsoft has a winning platform with Windows Phone 7 that will enjoy success comparable to Android and iPhone mobile devices.

Categories
Tags
Author

always-on-venture-summitMobomo founder and CEO, Barg Upender, was a panelist on a very successful Mobile Roundtable as part of the the latest Venture Summit Mid-Atlantic 2010.

The Venture Summit took place this past Nov 3rd-5th, at George Mason University in Fairfax, Virginia. On Friday, Nov 5th, the Mobile Roundtable covered innovation in the Mobile sector for the Mid-Atlantic region.

Topics and issues covered included apps, advertising, platforms, Mobile Service Management, mobile monetization & growth opportunities for investors, and what's to come in the Mobile sector.

For more information on the Venture Summit Mid-Atlantic 2010, please visit the official web page.

Need advice on a mobile apps strategy for your business? Just want to know how you can leverage the mobile platform in general? Feel free to contact us to discuss your app idea or mobile campaign needs.

Categories
Author

In the first two posts in this series, I explained some of the problems that we had with traditional Scrum and then laid out our new Agile process: Forge. In this post, I'm going to share a bit more about implementing Forge on our project and tell you about some of the benefits and challenges that we ran into.

The Benefits

Forge has solved a lot of problems for our team. Here are some of the most significant benefits we have seen.

  • Getting rid of technical debt

    One of the biggest problems with any project is the accumulation of “technical debt” (TD). TD is simply bugs and complexity that get introduced as a project gets larger. Things get even worse if you aren’t starting from scratch and will be working with someone else’s code.

    The advantage of having a finisher (or many finishers towards the end of the iteration) is that you have a dedicated developer whose primary job is reducing TD. Few other processes even acknowledge that you accumulate TD, let alone insist on a mechanism for reducing it. Over time, the net result is a more stable, more maintainable project. Ideally the process will also result in a robust library of modules and/or open source components that you can tap for enhancements and future projects.

  • Developer focus and ownership

    Since each new feature is assigned to a single developer, he/she develops a sense of ownership of that feature. There are several key benefits you get from this. First of all, since the implementation details are left entirely up to your developers, they are granted a level of autonomy and freedom of design that is very rewarding.

    Second, since each developer will begin an iteration as the sole person responsible for a new feature, by the time another developer is available to help carry it to completion, they will be very easily integrated into the task at hand. This dramatically reduces potential conflicts and improves productivity.

  • Clearly defined release feature set

    After a final QA check at the end of each iteration, the product goes through a full release. This process gives the team the opportunity to roll out new features as part of a complete release that can be communicated to users and partners. This vastly improves transparency and gives the customer the opportunity to promote the new release and also alert users of potential downtime.

The Challenges

Despite these benefits, Forge is not a silver bullet. There are several challenges that we have run into and had to either work around or adjust our expectations.

  • Delayed gratification

    One of the biggest roadblocks we faced was that our clients weren’t happy with the fact that they would need to wait for completed features. For example, if Sally completes a new feature four days into the iteration then it can be hard to explain why they have to wait another week for it to go to production. Over time the benefits of having a clear release announcement have outweighed this concern, but it can still be a hard sell for some organizations.

  • Long-running features

    Some features can also be difficult to implement and thus take far too long to tie the delivery of an entire iteration on its completion. For example, if you have six features slated for an iteration and one of them is expected to take four weeks but the timelines for the others are measured in days, then it doesn’t make sense to have most of your development team acting as finishers for three weeks while you wait for the completion of the difficult feature.

    Features that are going to take a long time to complete should typically be known during the planning phases. When one of them is on the list, the simplest thing to do is to let it carry over multiple iterations. When the feature is finally completed, the developer working on it just becomes a finisher for the remainder of the iteration as they normally would.

  • New projects

    Forge was created for a project that we inherited from another development company and so it came with a great deal of existing technical debt. In addition to simple code complexity, we had to deal with a large number of bugs from the first day on the project. This makes it easy to figure out what the finisher should be doing during that first iteration, but most projects aren’t "rescue" projects and the team will be starting from a blank canvas.

    Forge obviously still works in those situations, the only tricky thing is to figure out what the finisher should be doing early on. There are two different approaches that can be taken. First, you can leave off the finisher during the first iteration or two and only bring that role into play once you see yourself starting to accumulate technical debt. This can be risky because you may end up in a situation where the finisher never actually materializes, so we recommend that you explicitly limit the number of iterations without a finisher to one or two from the outset.

    The other possibility is to task the finisher early on with some of the infrastructure-oriented tasks. Configuring servers, deployment scripts, and continuous integration systems are all things that need to be done early on and may be a good place for the finisher.

  • Small teams

    Forge assumes that you will always have one person dedicated to fixing bugs, but on projects with very small teams (e.g. 2-3 people) this can seem like a burden. The truth is that it probably is a burden for those projects. In these situations, you will need to tailor the process a bit to suit the circumstances.

    There are a number of ways to address the issue. Some ideas that pop to mind are only including the finisher role every other iteration or requiring that the first person to complete their task always becomes a finisher instead of rolling on to help with another feature. Each project should address these challenges in the way that suits the team and the client best without worrying about rigidly sticking to a process.

  • Multi-finisher iterations and blitzes

    There were times on our project where we found ourselves falling behind on technical debt, even with a dedicated finisher on each iteration. This was most apparent when a new feature that we released turned out to have unforeseen consequences across the product. We found that sometimes we needed to run an iteration where we were less focused on features and more focused on finishing.

    These special iterations took one of two forms. The easiest form was simply to assign more than one person to the finisher role. When we might normally have five developers working features and one finisher, we would conduct an iteration with only two features and four finishers.

    The other form was what we called a blitz. We would designate an iteration length of a week and put the entire team on a finisher role. Blitzes also served an important planning role. The management team would spend blitzes reevaluating the whole feature wishlist and make sure that we were still on the right track. At the end of a blitz, we would have a fresh start with a renewed focus and direction for the product.

Conclusion

Forge has become a powerful weapon in Intridea’s arsenal. At the core, we are successful because we have extremely talented developers who can work miracles. But even the best developers in the world can run into roadblocks if the process they work under doesn’t help them get their jobs done. Forge helps our developers get the job done by making sure that the raw materials of a project, the ideas, are malleable enough to be worked into a finished product.

Categories
Author

Recent reports about Apple and Google mobile market shares might seem a bit contradictory, but the gist of them is fairly simple: both companies are winning in the mobile space.

According to a recent report from Canalys, Apple has taken the U.S. smartphone share lead for Q3 2010 with just over 26% marketshare -- edging out 2nd-place RIM by only 2%. But in terms of mobile OS, Android maintained its previous U.S. lead, with close to 44% for Q3 2010. However, consumer researcher NPG Group's findings show that Google's Android mobile OS's U.S. share jumped considerably (3% to 44%) between Q3 2009 and Q3 2010, whereas Apple and RIM have fallen in that time period -- RIM considerably, by a drop of 24% in that one year period.

On the flipside, both Apple and RIM won with handsets. Apple's iPhone 4 and RIM's BlackBerry Curve 8500 took first and second spots, respectively, in Q3 2010 as top handsets. High-end Android phones such as Motorola Droid X and HTC EVO 4G, which took 4th and 5th places, respectively, are examples of handsets that have helped Android move into and maintain top mobile OS spot.

Of course, since Android has multiple active versions in the wild and is not limited to one manufacturer's handsets, it's not surprising that this mobile OS is in the lead. Also, it doesn't hurt that there are some pretty sexy high-end Android smartphones competing with Apple's iPhones. I recently purchased a Droid X for Android development and I have to say I'm liking the phone about as much as my iPhone 3GS. I also like the Android experience, though that may change once I get an iPhone 4.

Now the question is, can Android maintain its lead as top mobile OS (at least for the U.S.)? Android apps are available in multiple "marketplaces" (including Google's official one), and that number is going to grow. For example, Barnes & Noble is coming out later this month with their Nook Color, an Android-based media tablet that has maybe not the ability to compete with the Apple iPad but to do well if marketed properly. However, taking a page from Apple's strategy, B&N plans to have its own curated marketplace for Nook Color apps. Similarly, wireless carrier Verizon already has its own VCast apps market for Android.

Whether marketplace, OS version and UI fragmentation is good for Android or not remains to be seen; Google is apparently making an effort to unify the Android UI experience for consumers. The fact is that there's a lot of confidence in the OS. According to Millenial Media's State of the App Industry 2010 Report, a survey of app developers and app publishers suggests that the top mobile platforms for 2011 will be, from highest to lowest, iPhone (30%), Android (23%), iPad (21%), RIM (12%), Windows Mobile (6%), Palm (5%), and Symbian (3%) [via ReadWriteWeb and Venture Beat]. Of course, those numbers might change as Android tablets -- which will on average be lower-priced than iPads -- come to market.

Need advice on a mobile apps strategy for your business? Just want to know how you can leverage the mobile platform in general? Feel free to contact us to discuss your app idea or mobile campaign needs.

Categories
Author

Rails adds a pretty cool Object#try method. From Rails doc:

try(method, *args, &block)

This Invokes the method identified by the symbol method, passing it any arguments and/or the block specified, just like the regular Ruby Object#send does.

Unlike that method however, a NoMethodError exception will not be raised and nil will be returned instead, if the receiving object is a nil object or NilClass.

This is how you use it:

 >> "Don'tRepeatYourselfs ".try(:underscore).try(:capitalize).try(:chop!).try(:chop!) => "Don't_repeat_yourself" >> nil.try(:underscore).try(:capitalize).try(:chop!).try(:chop!) => nil 

You can see it is not so DRY if you want to chain a lot of methods together, as is commonly the case in a Rails app. Inspired by RSpec’s stub_chain method, I wrote a little try_chain method:

 class Object   def try_chain(*args)     args.size > 1 ? eval("self.try(args[0]).try_chain(#{args[1..-1].inspect[1..-2]})") : self.try(args[0])   end end 
 >> "Don'tRepeatYourselfs ".try_chain(:underscore, :capitalize, :chop!, :chop!) => "Don't_repeat_yourself" >> nil.try_chain(:underscore, :capitalize, :chop!, :chop!) => nil 

This is much cleaner and you don’t see the NoMethodError exception for nil:NilClass anymore. A future version will work with arguments as in “Don’tRepeatYourself”.try(:sub, ‘Repeat’, ‘Shoot’).

Categories
Tags
Author

To start, I really want to say thanks to the Rails Rumble organizers; this event gave us an opportunity to practice using Rails 3 and to bring into reality some of the ideas floating around in our minds. It was also a great chance to work with people whom we don't always get to work with.

Unless you are a solo contestant in the Rails Rumble you have some teammates that you'll need to collaborate with. If you're lucky enough, your team members may live close to you, which means that maybe you get to work face to face, coding together, fleshing out ideas together, maybe even eating together. But I think many of the teams are distributed, like ours was. We were each in different places, different cities, and even different countries.

Communication Options

The efficiency and quality of communication becomes an extremely important matter in a 48-hour competition like the Rails Rumble. Since my Rumble team was distributed, we talked beforehand about how we would handle communication during the competition. We considered several communication tools:

  • Email
    Although email was a practical tool to exchange ideas before the competition, it would not have been the best tool during the competition. Email isn't quite instant enough when you need immediate and interactive feedback from teammates. Additionally, using email as a main source of communication means that you have to check your inbox frequently, which is a distraction in and of itself. Sifting through other unrelated emails from friends, family and colleagues would have interfered with our focused attention on the Rumble.
  • IM
    We did consider using an instant messaging service like Skype to build a chat group. Although IM communication is instant, it still was not interactive enough for our needs. Sharing mockups, screenshots and files is a cumbersome task through IM; each time you send a file, everyone has to click to receive it and if someone is away from the desktop at the moment, he/she may miss this file. Moreover, as your conversations get longer over the course of 48 hours, you may find the chat logs are going to be a mess. It becomes difficult to identify which messages are replying to which questions. And there will be times when you really want to go dark and focus on your work. The IM alert notifications can start to drive you crazy, but if you close the IM, you'll probably miss out on important information from you team.

Why did we use Present.ly?

We chose to use Present.ly as our communication tool during the Rumble. Present.ly is a private micro blogging system. It uses XMPP like most IM services use, so it's instant. But unlike IM, the messages are well organized thanks to the way it uses threading to display message replies. Plus, there are no messy chat logs to sift through! We use Present.ly at Intridea every day as our main tool for collaboration and communication across projects, so we were already comfortable with the application and knew how well it would support our unique needs as a distributed Rumble team.

Present.ly In Action

At the beginning of the competition we created a new private group under our Intridea Present.ly account. We stayed on our group's page during the 48 hour event so that we would not be distracted by messages from the main corporate stream and so that our conversation wouldn't interrupt other work going on at the same time.

Personally, I like using Present.ly in Fluid, because Present.ly supports the sound and Growl notification alerts specifically for Fluid. This feature was very useful when I was waiting for time-sensitive answers from my team. But when I didn't want to be disturbed, pressing the 'Mute' button on the page turned off the notification alerts.

Present.ly also enabled us to collaborate efficiently as programmers: we set a post-commit hook, which sent messages to our Present.ly group after each commit. Using the commit notifications ensured that everyone was as synchronized as possible during the competition.

Let me show you some of our real examples during the Rumble:

Here is the post-commit file:

 #!/usr/bin/perl  # change your username and password, then copy this file as .git/hooks/post-commit # then 'chmod +x .git/hooks/post-commit' # it'll run every time you commit (not push, mind you)  $username=''; $password=''; $git_text = `git log -n1 --pretty=format:"#commit (%h) %s"`; $git_long_text = `git log -n1 --stat`; chomp $git_text; chomp $git_long_text; `curl -k "https://intridea.presently.com/api/twitter/statuses/update.xml" -u $username:$password -d status="d imgateway $git_text" -d paste_text="$git_long_text"`;

Here is example of the commit message on presently:

Commit message

Here is an example of the threading view:

Threading view:

Here is an example of file sharing:

Filesharing:

There are a lot of communication and collaboration tools out there. But Present.ly was built by a development team at Intridea that understands the specific needs of real-time communication. So why not give it a try in next Rumble? And if you're not already using it for collaboration in your company, I recommend using it for that as well. It's a free and robust tool that helps to bring the power of real-time communication to teams of all sizes. I'm sure you will love it!

Categories
Author
Subscribe to