Week 14 was all about finally presenting our Graphical User Interface (GUI) design in Figma for the ShoeStride project. After weeks of brainstorming, aligning ideas, and obsessing over little details, we got to show off our landing page, login layout, and the overall vibe of our brand. Seeing it all together—with that sleek black-and-gold sneaker and bold typography—felt surreal. It really brought our vision to life.

Melanie led the initiative on creating the GUI, and we were super lucky to have her at the front of this task. With her experience in design, she helped guide our ideas and translate them into something visually cohesive. It made a huge difference. Her inputs kept us on track, and at the same time, we were learning a lot from how she worked—from layout decisions to button placements and visual flow. It wasn’t just about getting the work done, it was also a learning moment for the whole team.

During the presentation, Sir Earl gave his feedback right after, and as expected, it was a mix of compliments and constructive criticism. He appreciated some of the aesthetics and the effort we put in, but he also pointed out areas that needed refining. Alignment issues, inconsistent buttons, and some design elements that were unnecessary or confusing.

We took note of everything, especially the part about simplifying the interface, removing redundant stuff to make it cleaner and easier to navigate. He also reminded us to prepare four separate GUIs for each user type: buyer, seller, admin, and event organizers. That reminder helped us see the bigger picture and gave us clear next steps.

Week 13 was a rollercoaster that started with me nearly hyperventilating before our Project Management oral recitation - I'd memorized (well I tried ) every detail about System Architecture, UI Design, and all those charts until my brain hurt, only to barely pass in the end, but the actual recitation turned out surprisingly okay, with some unexpected laughs that made me realize my anxiety was worse than the reality

Later sa week, we worked on Sir Earl’s activity. Progress was slow, bit by bit, pero at least dili sayang. Every small step we took felt like a win.Aside from that, we also started working on the UI design for ShoeStride. Wala pa kaayo na-finalize, but we were able to throw around some ideas and sketch out a rough layout. It’s still a work in progress, pero at least naa nay direction. Slowly but surely, we’re building something that might actually work.

Not gonna lie, this week wasn’t the most productive one for the ShoeStride project. I didn’t really get much done on the manuscript side of things. It happens, right? Life kind of got in the way.

That said, I did try hehe note "try" to brainstorm some ideas for our UI design. Nothing solid yet, just some rough thoughts floating around. I’ve been thinking about making it look clean and intuitive, but I’ll admit it still needs more work.

Most of my energy honestly went into prepping for oral recitations. It’s been intense, and my brain’s been living in study mode for most of the week. Still, I know I’ve got to bounce back and refocus on the project soon.

Okay, so this week was all about taking our Shoe Stride paper from "okay na to" vibess to actually making it more formal and professional. We got feedback from our instructor and there were a lot of tiny things we didn’t even realize were problems. But hey, that’s why revisions exist para ma change angg need e change

First up: the Table of Contents. Turns out, we’d totally forgotten to add page numbers. Like… how?? It’s literally called a table of contents, and yet ours was out here looking like a vague outline with commitment issues. So we went through every section, manually checking where each one started and adding those little numbers like our grades depended on it (because… they kinda do).

Then there was the Abstract. Apparently, our keywords were just hanging out in the middle like they owned the place, but the formatting rules said they belong at the bottom. So we kicked them down there real quick—no hard feelings, keywords.

The biggest change? Section 1.3 (Objectives). Originally, it was this long, overly ambitious list like "we will solve world hunger AND invent time travel"—but our instructor reminded us to keep it focused. So we trimmed it down to three clear, realistic goals that actually match what we’re doing. Less daydreaming, more "this is doable in one semester."

we also:

Double-checked all our headings to make sure they matched the style guide (turns out bold vs. italics does matter).

Fixed some wonky spacing between sections (why does Word hate consistency?).

Read the whole thing out loud to catch awkward sentences (and laughed at how robotic we sounded in some parts).

Week 14 was all about presenting our Graphical User Interface (GUI) design in Figma for our project. After weeks of planning, aligning ideas, and fine-tuning elements, we finally showed our landing page, login layout, and the overall feel of our brand—Shoe Stride. 💥👟

Our landing page featured a sleek black-and-gold sneaker and bold typography that screamed modern and strong. Honestly, seeing our design come to life made all the hard work feel worth it.

Sir Earl gave us his feedback right after the presentation. He appreciated some of the details, but as expected, he also pointed out areas for revision and improvement—especially with alignment, button consistency, and unnecessary design. At first, it felt like “huhu not again 🥲,” but in hindsight, it was helpful. He really wants us to polish things, and that pushed us to do better.

We went back to Figma, checked every frame, and worked on the suggestions. It was tiring, but we started to appreciate how every tiny fix made the UI cleaner and more user-friendly. Bit by bit, the interface began to feel more professional and presentable.

This week reminded me that design is not just about creativity—it’s also about feedback, patience, and constant revision. Nakakapagod, yes, pero fulfilling. 😮‍💨💡

Week 14 = Revisions, Realizations, and Respect for the process.

Week 11: Polishing the Path – Manuscript Revisions for ShoeStride

This week marked a crucial phase in the development of the Shoe Stride project as the team shifted focus to revising the research manuscript. After receiving valuable feedback from our instructor, specific corrections were carefully implemented to improve the overall quality and structure of the paper. One of the key revisions addressed the "Table of Contents", which initially lacked page numbers. The team ensured that each section was properly linked to corresponding page references for better navigation and a more professional presentation. Another significant correction involved the "Abstract" section. Originally, the keywords were not positioned correctly; the updated version now places them at the "lower portion of the abstract", following proper formatting standards. Additionally, section "1.3 – Objectives of the Study" was restructured for clarity and conciseness. The original objectives were refined and reduced to "three main objectives", aligning better with the scope and goals of the project. Phrases such as "we aim" were removed and replaced with formal terms like "the researcher aims” or “the team seeks” to maintain a more objective and scholarly tone. These revisions not only enhanced the manuscript's academic tone but also reinforced the importance of precision and adherence to guidelines in research writing. Week 11 served as a reminder that attention to detail is just as important as innovation in ensuring a successful and credible capstone project

Honestly, this week, Shoe Stride took a backseat because midterms are trying to kick us in the bum (si OA). There was no way we could juggle shoe stride development and studying without completely losing our minds. So, we had to slow things down a bit.

But we did not ghost theproject. Even in the middle of this academic madness, we still stuck to our Methodology, just at a slower pace. We still kept tabs on everything, made sure there are no issues so far , and even threw around some ideas for when we get back at it. Lowkey, it was kinda nice to take a breather and just observe instead of constantly building.