Skip to main content

Burrow is superior than AirBnB

Our team has developed Burrow, an online rental booking software in line with AirBnB (AirBnB clone).

Ever since, we're asked to build a better rental booking software, we've thoroughly studied every websites on the domain including: 9flats.com, myfriendshotel.com, crashpadder.com, istopover.com, roomorama.com, metroflats.com, vrbo.com, couchsurfing.org, globalfreeloaders.com, Stay4Free.com, lodjee.com, evergreenclub.com, sublet.com, homeaway.com, onefinestay.com (and, now Wimdu.com)

Though AirBnB was popular and gaining news, we noted that AirBnB's UI is a great pain and it lacked many necessary features available in other similar sites. Our team has thoroughly analyzed the project and applied all necessary knowledge that we gathered from our FPPlatform product (that powers most of the Fiverr alternative sites).

Recently we keep noticing that AirBnB is chasing Burrow's calendar UI, referral concept, flagging option and review rating. Ironically, I think, it would be wise for AirBnB to buy Burrow and save the chasing cost instead!

Burrow's every piece is well architected and designed to scale high traffic sites (with gzip based file caching mechanism)

Here's the comparison document I have prepared sometime ago Burrow Vs AirBnB; note that some comments may be outdated as many new features have been added in Burrow since then.

Burrow can be customized to fit in to similar domains: renting office spaces, renting vehicles, etc

Comments

Popular posts from this blog

Open source PHP frameworks and problems

I was using CakePHP for sometime and proposed CakePlus , another UIMS toolkit on the top of CakePHP but also altering some problematic core of it. The thread should explain the outcome of the post. And, then I noted Akelos framework has most of the things built in. Issues with frameworks esp. CakePHP Scalability not a priority - Developers aren't aware that we can't throw more and more hardware Excessive use of regular expressions Evangelist isn't aware that the framework throws many queries unnecessarily More memory consumption - 100M would never be enough for a simple project Poor coding standards and practices - Prolong use of extract() often leads to more memory consumption Can't use the native approaches or baked codes. The override approach always lead to hard to debug codes Poor architected codes and no clear defined approaches. People belong to the cult drives the direction and often throws unprofiled codes. No native provision to share codes between M-V-C and...

Interview question #2

This is related to PHP's array . An array has number of elements. All elements are integers and unique, which means there is no repetitive integers. (e.g.) $foo = array(7, 5, 9, 13, 2, 8); You have to sort the array, provided: You should scan the elements only once. You're not allowed to compare the elements when sorting. (i.e., you're not supposed to use any comparison operators) Sorted resultant array may not be the source array. How will you do that?

What's wrong with delicious.com?

The recent UI changes of delicious.com is quite confusing and smells suicidal phase. I have noted that, after Joshua Schachter sold it to Yahoo!, it's going crazy changes. Probably, it's because a Yahoo! company now or Engineers don't get the real idea? Some crazy moves: del.icio.us to delicious.com change; probably to reach countries that censor .us TLD? delicious.com to www.delicious.com; unjustified Perl to PHP switch; why? for:handle geekish way to share to separate box; crazy but ok. Looks like, the new Yahoo! guys don't know how to make it a cult following like how twitter popularized @handle Recent broken UI