Reflection 2
Progress at its Finest
Embedded Files
Reflection #2 — Progress at its Finest
---
Reflection #2 — Progress at its Finest
(Resilient, Persistent, and Adaptable Achiever & Insightful and Strategic Researcher)
After I finished my first reflection, I started to prepare the basic layout of my app. Initially, the realms of Thunkable's app design tools were far more perplexing than I expected. To be fair they are still quite confusing, so I usually have to act in accordance with a given Youtube video in order to figure out how to produce the specific feature I am trying to make. Nevertheless, I understand the basic ways of how Thunkable's tools and measurements work. Nevertheless, I did manage to make major progress in the project because, when I did find these videos on how to make different features on my app, I was able to implement them into the app's design well.
This really goes to show that my skills of being an Insightful and Strategic Researcher are developing, and well. At the beginning, when I was first figuring out how to find tutorials and use tools, all I really wasn't able to explain to Google what my mind was referring. I found it difficult to find what I was looking for exactly and that slowed my progress down a lot due to the simple fact that I wasn't able to find what I was looking for. For instance, when starting the project, I was trying to find a video on how to enter text into Thunkable in order to write a heading. I was getting all these results that mentioned a Thunkable feature where a user can enter text into app and, in turn the app will preform the function; However, that was not what I needed, I later tried simply searching main words, "Thunkable text" and low and behold the exact video that I needed came up. From that moment on, I use, and will continue to use, only the critical words when researching any topic.
Following that, I do want to mention that sometimes I did not realize I was following the wrong video until the final steps of of the procedure. This is clearly represented in the picture to the left. Me, with my lack of previous knowledge regarding app design, didn't understand that for each page you want to have in your app, you would need a different screen on Thunkable. Instead, I decided to follow a video (which I unfortunately didn't save) that apparently wasn't trying to achieve the same end result as I did. So, I ended up combining two different pages that I wanted in one screen: the loading page, and the logo page.
However, since I was, in fact, trying to work on my Resilient, Persistent, and Adaptable Achiever skills, I knew I should be resilient and be persistent to do better and achieve the goals I wanted to complete. So, after that substantial calamity, I went over to make two separate new screens that featured the loading symbol and the logo symbol separately. To be fair, this wasn't as difficult to do, due to the fact that I could, for example, simply drag the elements of the old loading screen into a new Thunkable screen. Furthermore, I could even salvage the original screen that had both of the elements because after the loading screen elements were put in a separate tab, I was able to make the size of the loading screen fill the whole screen.
In addition to starting the display portion of my app, I also started the code. I first started the coding part of the project after I was able to make the loading page and logo page, but since then I have been going back and forth between working on the coding and display of the project between classes. I would have to say that the best moment so far during the relatively short interval of time from when I started this particular project was when I wrote my first block code. Sure it wasn't actual lines of code, but it might as well could've been by the given expression on my face when I saw the code allow the app to run properly.
First Speed Read Code.movSince making my first few lines of code — and when I say few I am for sure not exaggerating – I have made multiple more complex blocks of code, that allow the app to do much more than simply switch between screens. For instance, I was able to put together a few blocks of code in order for the computer to display the words on the given screen. Overall, I've been getting progressively better at both the coding aspects and design aspects of App design on Thunkable.
My goals for the next steps of my project is to have the computer display the words that the user enters into the screen one by one and at a certain speed. I know this will be very difficult to figure out, considering it did take me so long to figure out how to simply have the words show up on the screen. However, I am certain that if I delve into the classes of code I'll be able to figure it out soon enough. I plan on it taking me three classes (1 to 2 weeks) in order to put the code together. Next, regarding my LOs I want to develop my researcher skills even further. I have been really underestimating the abilities of Thunkable tutorials and the Thunkable help website. I really want to use the direct resources I can come across to assist me in the Speed Read Project – This will be a long term goal that I will try to carry out. So, in summary, my given goaIs will be to attempt to code Speed Read's most prominent feature, words displaying in the screen at a certain speed and quantity, as well as using the Thunkable help website that is directly supposed to assist creators in their app formation.
Page updated
Report abuse