Notice: register_rest_route was called incorrectly. The REST API route definition for contact-form-7/v1/contact-forms is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for contact-form-7/v1/contact-forms is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for contact-form-7/v1/contact-forms/(?P\d+) is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for contact-form-7/v1/contact-forms/(?P\d+) is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for contact-form-7/v1/contact-forms/(?P\d+) is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for contact-form-7/v1/contact-forms/(?P\d+)/feedback is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for contact-form-7/v1/contact-forms/(?P\d+)/refill is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for wc/store/cart is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for wc/store/cart/items is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for wc/store/cart/items is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for wc/store/cart/items is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for wc/store/cart/items/(?P[\w-]{32}) is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for wc/store/cart/items/(?P[\w-]{32}) is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for wc/store/cart/items/(?P[\w-]{32}) is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for wc/store/products is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for wc/store/products/(?P[\d]+) is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for wc/store/products/collection-data is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for wc/store/products/attributes is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for wc/store/products/attributes/(?P[\d]+) is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for wc/store/products/attributes/(?P[\d]+)/terms is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for content-forms/v1/check is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for themeisle-sdk/v1/checksum is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for themeisle-sdk/v1/checksum is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for themeisle-sdk/v1/checksum is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for content-forms/v1/submit is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for themeisle-gutenberg-blocks/v1/save_post_meta/(?P\d+) is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for themeisle-gutenberg-blocks/v1/save_block_meta/(?P\d+) is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for themeisle-gutenberg-blocks/v1/get_plugins is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for themeisle-gutenberg-blocks/v1/get_plugin is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for themeisle-gutenberg-blocks/v1/fetch_templates is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: register_rest_route was called incorrectly. The REST API route definition for themeisle-gutenberg-blocks/v1/import_template is missing the required permission_callback argument. For REST API routes that are intended to be public, use __return_true as the permission callback. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: rest_validate_value_from_schema was called incorrectly. The "type" schema keyword for id can only be one of the built-in types: array, object, string, number, integer, boolean, and null. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225

Notice: rest_sanitize_value_from_schema was called incorrectly. The "type" schema keyword for id can only be one of the built-in types: array, object, string, number, integer, boolean, and null. Please see Debugging in WordPress for more information. (This message was added in version 5.5.0.) in /var/www/wp-includes/functions.php on line 5225
GRIT by Brit Mobile App Launch – GRIT BY BRIT

GRIT by Brit Mobile App Launch

Share on facebook
Share on google
Share on twitter
Share on linkedin
Hey friends! I’m so excited to announce the launch of my official mobile app – YAY! Now you can have me in your pocket, literally, with on-the-go workouts and daily inspiration.

Hey friends!  I’m so excited to announce the launch of my official mobile app – YAY!  Now you can have me in your pocket, literally, with on-the-go workouts and daily inspiration.

Since I opened my boutique fitness studios, GRIT Fitness, I haven’t blogged as much as I once did   So I was determined to find a creative way to:

  1. Stay connected with my beloved blog followers who live all over the world
  2. Provide home workouts and inspiration to my GRIT Fitness members who live Dallas (so they can sweat when they can’t make it to the studio)

Over the past several months I’ve been working diligently to create the content, test the functionality and execute all of the small details required to develop my very first mobile app!  I think this is a first step to something HUGE!  It’s been such a challenging and engaging experience, much like 4 years ago when I created my first workout DVD (remember that?!)  I’ve really enjoyed the process as it’s truly a labor of love.  I hope you love the app as much as I do.

Throwback! Launching the GRIT by Brit Workout DVD in 2013

So now you’re probably wondering, what’s in the app?  Well here’s a run down:

  • My personal  21-Day Fitness challenge complete with workout calendar and nutrition tips
  • Several on-the-go workouts categorized by focus (arms, legs, abs, cardio, etc)
  • On demand workout videos featuring my original workouts
  • Inspirational pep talk videos from yours truly!

GRIT by Brit Mobile App Coming Soon!

Because I’m so excited about this new creation, I’m making it FREE to EVERYONE for one day only – August 21, 2017.  Once you download it, you have it FOREVER – so I suggest you save the date and get ready to download.

To download the app, just got to the app store and search “GRIT by Brit” – the app will be available on both iOS and Android.

Thanks so much for your continued support.  Get ready to get GRITTY!

xo,

Brit

Brit Rettig

Brit Rettig

Leave a Reply

Sign up for Brit's Newsletter

Let’s keep in touch! Get alerted when a new blog is released.