Two months ago I posted about an AngularJS side project that I had planned to begin working on. Over the past 8 weeks I have broken ground and launched an initial 1.0 app. I have gained an understanding of AngularJS, built a website that I am proud of, and had fun along the way.
GymNear.com is a simple to use and effective app that helps users find a gym or fitness center near them. Users enter in a location and the app responds back with a list of gyms nearby.
In my original post I wrote about how difficult it was to find a gym when google searching. I went as far as to say, “Scouring Google search results for ‘gyms near Reston, VA’ always proves a waste of time.”.
Which is ironic, because I am now entirely relying on the Google Places API to serve content.
I ditched the idea of scraping the internet to create my own database of gyms and fitness centers. Instead I went with Google’s API. Google has a fantastic database with more information then I would have ever been able to successfully pull together. The issue Google faces is when it comes to displaying that information to the end user.
A google search of “Gyms near Reston, VA” will still be a waste of time. Intermixed with the good results are advertisements and unrelated content. With GymNear.com the user is presented with 20 of the closest gyms, that is it.
Essentially, all I have done is made a simplified Google. It works, it is easy to use, and it provides immediate value, I am really happy with where it stands.
I decided on a minimalist design for GymNear. When looking at competitors I thought there was a great opportunity to differentiate GymNear with clean, simple design.
Other websites that offer the same functionality look like they are from 2002…
With GymNear I knew I wanted something that looked both modern and simple.
In the spirit of not having to make the user think (thank you Steve Krug), I have limited GymNear’s functionality. The only thing a user can do on the site is enter a location and click on a link.
Initially I wanted to include reviews, ratings, directions and any other information that I could find when returning results. I decided against this, at least for now in an attempt to make GymNear as easy to use as possible.
Join hundreds of others!
Get notified of new posts.
By providing bare-bones functionality the user gets exactly what they expect, while also leaving the window open for future features to be added.
Creating GymNear with Google’s API has allowed me to bypass nearly all “back-end” development. The entire application is built in Angular, and I have not yet set up a node server on the back-end.
Currently GymNear works by sending an API call to the Google Maps Place Service with the user entered location. It returns an array of objects which I then display on the page. When a user clicks on more info I pass that specific gyms place_id to Google’s Place Details API which returns another object with a ton of relevant information.
Essentially, what I have made is a website that makes a ton of requests to Google.
In addition to configuring Prerender I am also planning on implementing UI Router. I would like to create 50 or so pages that serve content for specific locations. For example, gymnear.com/boston, or gymnear.com/atlanta. I think creating webpages like these would work well and help Gymnear rank higher for specific search terms.
Hopefully between Prerender and Angular UI Router GymNear will be able to get picked up by search engines.
Building version 1.0 of GymNear has been a blast. I will continue to post updates as more people use the application, and as new features and technical updates are made. If you are going to teach yourself a language or framework, this is the way to do it. Find a project and simply plug away.