# How to create nutrition app with ocr scanner?

**URL:** <https://community.thunkable.com/t/how-to-create-nutrition-app-with-ocr-scanner/1113955>\
**Category:** Questions about Thunkable X\
**Created:** [February 21, 2021, 5:28pm UTC](https://community.thunkable.com/t/how-to-create-nutrition-app-with-ocr-scanner/1113955 "2021-02-21T17:28:00Z")\
**Posts on this page:** 1\
**Showing post:** 119

<div class="post-metadata">

**Author:** ![tatiang](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/tatiang/32/55482_2.png) [@tatiang](https://community.thunkable.com/u/tatiang)\
**Post date:** [March 11, 2021, 10:48pm UTC](https://community.thunkable.com/t/how-to-create-nutrition-app-with-ocr-scanner/1113955/119 "2021-03-11T22:48:08Z")

</div>

I think @muneer’s suggestion was to use labels to display intermediate steps in your code. So instead of running the entire set of blocks and wondering why it doesn’t work, you can debug your code by adding “set label’s text to” blocks every so often and checking values that you are getting from blocks (e.g. from JSON, etc.). You can even put Wait blocks and/or Vibrate blocks in so that you know where you are in the code when something does/does not work.

This is what I tend to do in my own projects:

> [@Debugging in Thunkable X (Video)](https://community.thunkable.com/t/debugging-in-thunkable-x-video/849471):
>
> I thought I’d share a process I use for debugging my projects. It involves creating a function that can be used over and over throughout the code blocks in order to help determine where things are going wrong, whether or not certain blocks are ever triggering, and what the values of several variables are. Here’s a screenshot of what I’ve set up: The real power comes from being able to quickly change the delay (and even set it to 0 seconds) or just remo…

---

_[View the full topic](https://community.thunkable.com/t/how-to-create-nutrition-app-with-ocr-scanner/1113955)._