My Internship Blog

 Today, I finalized the decision on which model to use for our chatbot feature. After thorough research and consideration, I proceeded with integrating the chosen model into the application. The process was quite challenging, especially in setting up the initial integration and ensuring it worked within our existing system. Despite the struggles, I’m glad to say I was able to complete the integration. However, I recognize that the chatbot still needs refinement to improve its accuracy and relevance. We'll need to train it further to align with the kind of responses we want it to provide to users.

 Today, I worked on adding a new feature to our app—a chatbot. I spent most of the day studying how chatbots function and how they can be effectively integrated into our application. This included researching various models and frameworks that are commonly used in chatbot development. It was an insightful experience as I explored different options to determine which model would best suit our system’s needs. Although the chatbot is still in its early stages, I’m excited to see how it can enhance user interaction within our app.

 Today, I successfully finished applying the skeleton loading throughout the app. The task went smoothly, especially since I reused several components I had already created. It feels great to see a consistent and user-friendly loading experience across the entire app. After that, I worked on and completed the QR code generation feature. Since it only involved displaying the user’s information, I was able to implement it entirely on the frontend. It was a straightforward task, but still satisfying to complete and see working properly.

 Today, I focused on applying a consistent loading experience across the entire app. One of my teammates initially used a spinner loader in certain parts of the UI, but to maintain a unified and cleaner look, I started replacing it with the skeleton loader that I previously implemented. This not only improves visual consistency but also gives users a smoother experience during data fetches. I'm currently halfway through integrating the skeleton loading across all necessary components. Although it takes a bit of time to adjust each section, the progress is steady, and I'm hoping to wrap it up soon.

 Today, I implemented a skeleton loading effect to enhance the user interface while data is being fetched. I chose skeleton loading for its simplicity and because it aligns well with the design system of our app. It provides a better visual cue than a spinner and gives users a glimpse of the layout they can expect once the content loads. At first, I struggled a bit with getting the skeleton shapes and layout to match the actual components accurately. But after some trial and error, I managed to make it look more refined and consistent. I'm really satisfied with how it turned out—it definitely makes the app feel more responsive and polished during loading states.

Today, I focused on improving the user experience by implementing a loading state while retrieving data from the backend. Previously, the app would show either an empty "No Data Available" message or a blank screen during data fetches, which could be confusing to users. To address this, I decided to introduce a proper loading indicator to make the transition smoother and more intuitive. I spent some time researching the most effective approach to achieve this and explored various loading animation styles that would best fit our app’s design. After testing a few options, I found a clean and simple loader that complements the overall interface. This small improvement adds a more polished feel to the app and enhances usability. 

 Today, I focused on integrating more backend functionalities into the feature I’ve been working on. I reviewed the existing API endpoints and carefully mapped out how the data should flow from the server to the frontend components. I encountered a few mismatches between the expected data and what was being returned, but after some debugging and testing, I was able to resolve the issue. Working on this integration has helped me better understand how to handle dynamic data, loading states, and proper error handling. It’s challenging, but it’s also rewarding to see the app come together as each piece starts functioning as intended.

 Today, I continued working on the feature I’ve been assigned to, focusing more on polishing the frontend and testing its functionality. I spent time debugging minor issues and ensuring the layout remains responsive and user-friendly across different screen sizes. I also reviewed my previous code to make it cleaner and more readable. As we move forward, I’m now becoming more comfortable switching between frontend and backend tasks. This experience has been helping me grow both in skill and confidence, especially in understanding how different parts of the system work together.

 Today, I only reported for half of the day due to a scheduled company visit required by our school. Despite the shortened time, I still managed to contribute to the ongoing project before heading out. It was a productive half-day that helped me stay aligned with our current progress. What surprised me was the unexpected visit from our Practicum adviser’s company. They checked on our performance and asked how we were doing. It was reassuring to know that our well-being and development as interns are being closely monitored and supported.

 Today, I focused on refining the feature I previously integrated with the backend. I spent some time checking how the data behaves in different scenarios and made slight adjustments to improve the user experience on the frontend. It was important to ensure that the data loaded correctly, even when the API response was delayed or empty. I also reviewed some parts of the codebase with my partner to make sure everything remains consistent across components. We discussed how to better structure some logic for maintainability as we move forward. It felt great to see the feature becoming more polished and functional.

 Today, I continued working on the backend and frontend integration. I focused on another API connection that was needed for the feature I previously completed. It took some time to understand the logic behind the response structure, but once I figured it out, I was able to map the data correctly into the UI. I also encountered some small issues during the process, especially with how the data was being rendered in certain components. Thankfully, I was able to debug them with the help of console logs and some guidance from a teammate. It’s been a productive day of learning and applying, and I feel like I’m becoming more confident in handling both sides of development.

 Today, I was able to successfully connect some of the backend APIs to the frontend. It felt rewarding to see the connection work and data flow as expected after several tests. I spent time reviewing how the backend routes are structured and learning the correct way to use them on the frontend side. One important takeaway from today was understanding that it’s not just about calling an API — I also need to be clear about what parameters the backend requires and what kind of data should be sent or retrieved. That knowledge helped me avoid common errors and made the integration process smoother.

 Today, I began connecting the backend to the frontend part of the feature I previously completed. I focused on understanding how the routes from the backend are structured and how to properly call and use them within the frontend. To get more familiar with the process, I did several tests using sample data and observed how the responses were handled. It was a productive day filled with learning. While it took some time to grasp the flow of data and how everything ties together, I’m starting to build confidence in integrating backend logic into the app. I'm looking forward to refining this further in the coming days.

 Today, I completed the frontend part of the feature I was assigned to. After polishing the UI and refining the flow, I spent most of the time testing it using dummy data to make sure everything worked as expected. Thankfully, the layout and logic responded smoothly without any noticeable bugs or issues during testing. With the design and functionality now stable, I’m preparing to move into backend integration. I’m hopeful that once it’s connected to real data, the feature will still function properly, though I’m also ready to make adjustments if needed. This phase will be important in ensuring the feature operates seamlessly in a real environment.

Today began with my usual cup of coffee – it’s a simple routine, but it helps set the tone and gives me the energy I need to focus on my tasks. With that, I started diving back into our project. We are currently working on one of the main features of the mobile application, and this part is crucial because it involves several components that need to work together seamlessly. The feature we’re building was discussed in detail during our meeting yesterday. During that meeting, we aligned on the user flow, the structure of the data, and how we want the interface to behave. We also made sure to assign tasks properly to keep the development organized and efficient. I really appreciated how collaborative the discussion was—it made it easier to visualize what we need to accomplish. Today, I focused primarily on the frontend aspect of the feature. Since I specialize more on the frontend side, I made it a point to ensure that the UI is clean, responsive, and aligned with our Figma design. So fa...

Today, we focused on developing one of the main features of the app. To ensure a smooth implementation, we conducted a small meeting where we discussed the flow of the feature, how it should function, and the best approach to integrate it efficiently. Having this discussion helped us align our ideas, identify potential challenges, and plan our workflow better. After finalizing the structure, we started working on the development process, gradually bringing the feature to life. (📸 Daily selfie outside)

Today, we worked on our daily progress report, which we need to submit to our company. It’s a way to track our tasks, challenges, and progress throughout the internship. While writing the report, I realized how much I’ve learned and improved over the past few weeks. From struggling with setting up my environment to now confidently working on features, it’s been quite a journey. Aside from documentation, we continued working on our assigned tasks, ensuring that we keep up with the project timeline. (📸 Daily selfie outside)