Deprecated: Return type of WP_Theme::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/qdgxdzmy/public_html/atozaatar/wp-includes/class-wp-theme.php on line 554

Deprecated: Return type of WP_Theme::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/qdgxdzmy/public_html/atozaatar/wp-includes/class-wp-theme.php on line 595

Deprecated: Return type of WP_Theme::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/qdgxdzmy/public_html/atozaatar/wp-includes/class-wp-theme.php on line 535

Deprecated: Return type of WP_Theme::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/qdgxdzmy/public_html/atozaatar/wp-includes/class-wp-theme.php on line 544

Deprecated: Return type of WP_REST_Request::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/qdgxdzmy/public_html/atozaatar/wp-includes/rest-api/class-wp-rest-request.php on line 960

Deprecated: Return type of WP_REST_Request::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/qdgxdzmy/public_html/atozaatar/wp-includes/rest-api/class-wp-rest-request.php on line 980

Deprecated: Return type of WP_REST_Request::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/qdgxdzmy/public_html/atozaatar/wp-includes/rest-api/class-wp-rest-request.php on line 992

Deprecated: Return type of WP_REST_Request::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/qdgxdzmy/public_html/atozaatar/wp-includes/rest-api/class-wp-rest-request.php on line 1003

Deprecated: Return type of WP_Block_List::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/qdgxdzmy/public_html/atozaatar/wp-includes/class-wp-block-list.php on line 151

Deprecated: Return type of WP_Block_List::next() should either be compatible with Iterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/qdgxdzmy/public_html/atozaatar/wp-includes/class-wp-block-list.php on line 175

Deprecated: Return type of WP_Block_List::key() should either be compatible with Iterator::key(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/qdgxdzmy/public_html/atozaatar/wp-includes/class-wp-block-list.php on line 164

Deprecated: Return type of WP_Block_List::valid() should either be compatible with Iterator::valid(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/qdgxdzmy/public_html/atozaatar/wp-includes/class-wp-block-list.php on line 186

Deprecated: Return type of WP_Block_List::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/qdgxdzmy/public_html/atozaatar/wp-includes/class-wp-block-list.php on line 138

Deprecated: Return type of WP_Block_List::offsetExists($index) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/qdgxdzmy/public_html/atozaatar/wp-includes/class-wp-block-list.php on line 75

Deprecated: Return type of WP_Block_List::offsetGet($index) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/qdgxdzmy/public_html/atozaatar/wp-includes/class-wp-block-list.php on line 89

Deprecated: Return type of WP_Block_List::offsetSet($index, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/qdgxdzmy/public_html/atozaatar/wp-includes/class-wp-block-list.php on line 110

Deprecated: Return type of WP_Block_List::offsetUnset($index) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/qdgxdzmy/public_html/atozaatar/wp-includes/class-wp-block-list.php on line 127

Deprecated: Return type of WP_Block_List::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/qdgxdzmy/public_html/atozaatar/wp-includes/class-wp-block-list.php on line 199

Deprecated: Return type of WPCF7_FormTag::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/qdgxdzmy/public_html/atozaatar/wp-content/plugins/contact-form-7/includes/form-tag.php on line 396

Deprecated: Return type of WPCF7_FormTag::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/qdgxdzmy/public_html/atozaatar/wp-content/plugins/contact-form-7/includes/form-tag.php on line 388

Deprecated: Return type of WPCF7_FormTag::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/qdgxdzmy/public_html/atozaatar/wp-content/plugins/contact-form-7/includes/form-tag.php on line 382

Deprecated: Return type of WPCF7_FormTag::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/qdgxdzmy/public_html/atozaatar/wp-content/plugins/contact-form-7/includes/form-tag.php on line 400

Deprecated: Return type of WPCF7_Validation::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/qdgxdzmy/public_html/atozaatar/wp-content/plugins/contact-form-7/includes/validation.php on line 78

Deprecated: Return type of WPCF7_Validation::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/qdgxdzmy/public_html/atozaatar/wp-content/plugins/contact-form-7/includes/validation.php on line 72

Deprecated: Return type of WPCF7_Validation::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/qdgxdzmy/public_html/atozaatar/wp-content/plugins/contact-form-7/includes/validation.php on line 59

Deprecated: Return type of WPCF7_Validation::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home2/qdgxdzmy/public_html/atozaatar/wp-content/plugins/contact-form-7/includes/validation.php on line 82

Deprecated: ltrim(): Passing null to parameter #1 ($string) of type string is deprecated in /home2/qdgxdzmy/public_html/atozaatar/wp-includes/wp-db.php on line 3030

Deprecated: Constant FILTER_SANITIZE_STRING is deprecated in /home2/qdgxdzmy/public_html/atozaatar/wp-content/plugins/wordpress-seo/src/conditionals/third-party/elementor-edit-conditional.php on line 22

Deprecated: Constant FILTER_SANITIZE_STRING is deprecated in /home2/qdgxdzmy/public_html/atozaatar/wp-content/plugins/wordpress-seo/src/conditionals/third-party/elementor-edit-conditional.php on line 28

Deprecated: trim(): Passing null to parameter #1 ($string) of type string is deprecated in /home2/qdgxdzmy/public_html/atozaatar/wp-includes/class-wp.php on line 173

Warning: Cannot modify header information - headers already sent by (output started at /home2/qdgxdzmy/public_html/atozaatar/wp-includes/class-wp-theme.php:9) in /home2/qdgxdzmy/public_html/atozaatar/wp-content/plugins/pixelyoursite/includes/class-pys.php on line 199

Deprecated: ltrim(): Passing null to parameter #1 ($string) of type string is deprecated in /home2/qdgxdzmy/public_html/atozaatar/wp-includes/wp-db.php on line 3030
One&Only Royal Mirage Dubai... Or, the Residences. — A TO ZA’ATAR
Deprecated: parse_str(): Passing null to parameter #1 ($string) of type string is deprecated in /home2/qdgxdzmy/public_html/atozaatar/wp-includes/formatting.php on line 4975

Deprecated: strtolower(): Passing null to parameter #1 ($string) of type string is deprecated in /home2/qdgxdzmy/public_html/atozaatar/wp-content/plugins/wordpress-seo/src/generators/schema-generator.php on line 185

One&Only Royal Mirage Dubai… Or, the Residences.

One&Only Royal Mirage Dubai… Or, the Residences.

Have you ever had a dream property in a city?  No?  Just me?  I’ve got a few fantasy destinations picked out in most places and the One&Only has long (loooooong) been on my list for Dubai.  (Also worth noting: the Al Maha Resort and Nurai Island, along with the Chedi Muscat and Zighy Bay in Oman).  With a combination of the need for a staycation combined with our 13th wedding anniversary, I decided this was the time to pull the trigger.  Looking on Booking.com, there were some good deals running (especially as the Eid holiday was about to start last week).  Given a choice, I will nearly always pick a Club Room — we haven’t had a bad experience in one yet.  Having access to a good (free) cocktail hour tends to be a great start to an evening.  Furthermore, booking a higher category room tends to lead to upgrades on arrival.

So, in case you haven’t been to the location, there are actually three distinct properties on the Royal Mirage site (of course, I’d love to stay the Palm property as well, but one thing at a time, people): The Palace (where I originally booked), The Arabian Court, and the Residences.  Upon arrival, we were greeted (with a gong…?) and walked to a posh lounge.  In said posh lounge, we received dates and a welcome drink, along with fresh cold towels.  I dutifully handed over our passports and credit card.  We were enjoying the arrival amenity when we were approached to mention that we were instead going to be placed in the Residences.  Look, this was definitely an upgrade, but I’m not sure why they couldn’t have called me at say 12 PM to tell me to drive over to the Residences.

One&Only Dubai
Posh is as posh does.

While the hotel moved our car, we jumped in a golf cart and headed towards the Residences…for a glass of sparkling date juice (?) and more cold towels.  As we spoke to the team, I checked to see when the cocktail hour would start in the Gold Lounge (back at the Palace).  Apparently, this is not a perk of staying in the Residences (but the entire reason I booked the room category I did).  I politely said as, much and the response was ‘as an exception’ we would be granted access (which we would have to take a golf cart back over to the Palace to enjoy).  Now, this felt a little like being a brunch, choosing the champagne package, but being told you couldn’t have the house beverages.

Anyway…

The room was in one of the outer buildings, at the end of a hall and upstairs (all yay for this gal, who only craves a quiet room — much easier said than done).  Inside, we were presented with a standard Residence Prestige King Room.  And friends, if you’ve been reading this blog, you’ll know I can find fault in pretty much anything, so here are my suggestions for the One&Only:

  • A television that doesn’t have lines (no, really, the TV in the room was pretty much garbage — I know, you do not come to the One&Only to watch television, but sometimes it’s nice to zone out for an hour while you cool down from the pool).
  • An air conditioner that gets cold.  I like to sleep in nearly arctic conditions (18C), and we could not get the thermostat below 22.6C (it mostly stayed around 24C).
  • A much larger ice bucket.  Hubs and I tend to travel with our own beverages, and for love or money, we could not get our champagne to chill in the tiny bucket that was provided.
  • Bottles of water in the room.  I think this was a miss from housekeeping, as every single room I’ve checked into (no matter where in the world) always has bottles of water waiting.
  • I’ll probably get dinged for this one, but as I mentioned, I advised the hotel it was out anniversary.  We received the following:  two bouquets of flowers (that I wasn’t sure if we were supposed to take with us), rose petals, macarons and other sweets, a signed card (which was a picture of our room–?!) and some romantic towel swans.  It basically felt like what someone tells you forces you what a romantic ideal is supposed to look like.  We guessed other (far less cynical) people would be impressed, but for a couple that’s been together 15 years, all we wanted was a bottle of bubbly!
  • Dinner was mediocre at best (and not cheap).

It wasn’t all bad — I promise.  Some highlights:

  • Fabulous Molton Brown products!
  • An absolutely immaculate property.
  • The fact that our anniversary was recognized in some way.
  • A nearly private beach.
  • Access to a more private pool.
  • Friendly and super accommodating staff.
  • A fantastic cocktail hour — the Gold Lounge was a great place to meet other travelers, I really enjoyed the experience (and I would recommend booking a room that allows access).

Here are some pictures of our room (minus the rose that was later sacrifced for petals):

So, rooms like this obviously do not come without a price.  On Booking.com, I was able to secure AED1800 for the club room (which would’ve included a continental breakfast, afternoon tea and the aforementioned cocktail hour).  I know, that’s a lot of money.  Our upgraded room would’ve cost AED2,000+ (and would not have had lounge access, but would have included an extended (and delicious) daily breakfast…?).  Either way, for that kind of money I would much rather be in the Maldives and spending a night over water.

Time for the most important question: would I go back?  Sorry, One&Only, you’re just too expensive for what is on offer.  I should’ve listened to the little voice who told me to go check out the W, or some of the other 5 star properties in town.

Have you been to the One&Only?  Were your expectations met?
[googlemaps https://www.google.com/maps/embed?pb=!1m18!1m12!1m3!1d3613.2017819524094!2d55.14820595147742!3d25.09502998386498!2m3!1f0!2f0!3f0!3m2!1i1024!2i768!4f13.1!3m3!1m2!1s0x3e5f6b45c6d8f933%3A0xd00635d81fcb43de!2sOne%26Only+Royal+Mirage+-+The+Palace!5e0!3m2!1sen!2sae!4v1468554425586&w=600&h=450]

Leave a Reply

Your email address will not be published.