You can see here, we have a simple design because we know it’s hard to think when you’re hungry. So, quickly check your wallet and see how much money you have. Then how adventurous are you feeling? A quick walk? A short ride? Or maybe a trip up to Kaysville, that’s your call. Or if those questions are too hard, then just go ahead and hit that Find Me Food button, and it will make that decision easy.
Also, if you have a slight idea where you want to eat, maybe Chinese or Thai, you can select those in Popular Cuisines.
Or, if you’re suddenly thinking Arby’s, then go ahead and search for it. It’s as simple as that.
As the dynamic lyricists Journey once said, anyway you want it, that’s the way you need it. Anyway you want it.
Now that you know how we’re making your lives easier,
Gavin, could you come over here and talk about what’s going on behind the scenes?
We’re focused on providing the best user experience possible, which is why we’re using the best food database on the planet: Google. In order to work with and help format the data we implemented the google_places gem. Then we sprinkle in another little gem, geocoder which takes your location and converts it into usable data, then we do some math and add in your food choices. The final result is a highly optimized food choice that is perfected to satisfy your hunger.
When working through this idea, we wanted to challenge ourselves. So we decided to not use Materialize or Bootstrap for styling, but rather we used Skeleton to give us the basic grid and then styled the app ourselves. One of the main reasons we chose Skelton was that is was lightweight which would speed up our apps loading, and also it was a mobile first platform, and we wanted to cater to that section of our users first, while still giving a good feel to our parents at home on their desktops :)
Also, Test Driven Development is what we tried to follow when building this app, and while not all of our tests were written before the code, it was something we were cognizant about. And we are happy to say we have finished with over 95% test coverage on Belcher.
Okay, Justin can you come and finish these cats off.
As hungry as I’m sure you are at this point in the night, we do have a couple additional topics we’d like to discuss. When determining what tech to use building Belcher, we decided we didn’t want a new page reloading with every button touch, and that’s where React came in. By using React we’re able to limit our reloads and as you’ll find out using belcher on the way home tonight, the only
