Eddie's Experience with Loco
Hi, I’m Eddie and welcome to my Ted Talk. I am a junior in college majoring in Psychology on the pre-med track. I’m here to share my experience learning to use Loco for the first time. Although Loco requires absolutely no prior coding experience, I do have a little. I took two AP Computer Science classes in high school as well as two more computer science classes so far in college.
The first time I used Loco I started by making a timesheet app for employees to log their daily hours worked. I got this idea from the “Weekly Employee Shift Tracker” app in the app library because I noticed that this app doesn’t keep track of the actual shifts worked or log employee hours. So, I decided to make my own app that did this.
Here are the steps I took:
- I took the useful parts of the Weekly Employee Shift Tracker which I decided to be the decks
- I added properties to the decks knowing I could come back and change them at any time
- I added secondary decks to mimic the current timesheet app I use at work
- Finally, I started creating rules
Creating a rule was the part I found most challenging, so I will go into a little bit more detail on how I went about it. My goal for creating a rule was to allow someone to select that the week was complete which would trigger a rule that totaled the hours worked for all the days of that week. I actually started writing the rule about 3 different ways before I decided on the method I liked the most. I ended up putting a finish week button on each daily log card that when checked would create a weekly log with the total hours for that employee during that week.
For me, the most challenging part of creating my timesheet app was just getting started using the different features. I was initially confused about the relationship between cards, decks, and sets but after experimenting for about 30 minutes I became pretty comfortable with using them. Another area that was initially difficult was creating a rule. As I said, I first started creating about 3 different rules to do the same thing in order to figure out what worked best. I discovered that the best way to become comfortable with creating rules was just to start trying to make something simple and slowly work through all of the difficulties. This took a little longer, but after about 2 hours I felt that I knew what all I could do with the rules and how to actually make them too.
For all of the challenges I had, I believe that I could’ve gotten everything done with much less difficulty if I had someone to ask questions to while doing it... having someone that could quickly answer my questions would’ve made the process a lot smoother and faster, which is especially noteworthy considering how quickly I was already able to successfully create an app on my first try. After I got used to using all of these basic features, adding more functions and complexity to my app was extremely easy and I actually had a lot of fun doing it!