paulinreese

[paulinreese]

WEEK 14 : Present sa UI progress

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.

This week was a mix of pride and humility. We got to see our design come alive, but we also saw how much better it could be. More than anything, we’re learning that great design isn’t just about looks—it’s about clarity, function, and teamwork.

[paulinreese]

Week 13 progresss

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.

This week hit me with a reality check. Learning isn’t about being fast or perfect. Sometimes it’s just about showing up, breathing through the anxiety, and doing what you can. Maka-pressure man, but I realized nga stumbling doesn’t mean I’m failing. It just means I’m still in the process. And somehow, despite the stress, I actually had a good time.

[paulinreese]

week 12: laban mga et

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.

This week was definitely a reminder that progress isn’t always linear. Sometimes we just do what we can, and that’s okay. Here’s to coming back stronger next week.

[paulinreese]

Week 11: revising this messsss aaaa

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).

It wasn’t the most exciting week, but honestly? Seeing the paper look this much cleaner feels amazing.

[paulinreese]

Week 10 – Chill Week (Holy Week vibes 😌✝️)

This week was super chill since we had no face-to-face classes and it was Holy Week. No pressure to be on campus meant we had time to rest a bit and catch up on our manuscript. We used the downtime to review our current progress, tweak some parts of the paper, and make sure our flow and diagrams still made sense. Nothing crazy, just slow but steady progress behind the scenes. I even posted about this update late because of the short break( nag extend 8080) .

[paulinreese]

Week 9: Just keep swimming ang atake

This week was pretty chill because no face-to-face session with this class, so we used the extra time to continue working on our manuscript and keep pushing forward with our methodology. Since we didn’t have to go on campus, it gave us a chance to catch up, review what we’ve done so far, and add more content to the paper. We made sure everything was still aligned with our goals and that our system flow and diagrams still made sense.

Most of our time went into polishing the written parts, like refining sections we already started and drafting new ones. We also made some small adjustments to our visuals and started organizing the final layout of the document. A few of us even started thinking about the presentation . I knowww we’re not there yet, but we’re getting close. It was more of a behind-the-scenes kind of week, but progress nonetheless.

We also started preparing some of the parts we’ll need for our final paper, like drafting summaries, fixing up older sections, and checking if our diagrams are all consistent. A few more ideas were thrown around for the UI too, just in case we have time to mock some stuff up.

[paulinreese]

Week 8: Back at It (Fr This Time)

After surviving the midterm chaos (barely), we finally got back into the progress with Shoe Stride. This week was all about getting our stuff together, especially our Use Case Diagram. I made this using draw.io.com We cleaned it up and made sure it actually made sense. It now clearly shows what customers, admins, and sales reps can do in the system. Customers can register, log in, browse products, place orders, track them, update their profile, and pay. Admins handle managing users, inventory, and deciding which orders go through. Sales reps help with approving those orders too. We also added things like “Add to Cart” and “Manage Offers” to make the whole thing feel more complete.

Aside from the diagram, we also tackled our paper. Our instructor gave some feedback and told us to avoid using “we” and replace it with more formal stuff like “the researchers” or “the team.” So yeah, we had to go back and fix a lot of wording. We also narrowed down our objectives to just three solid points because the original list was kinda doing too much.

Not gonna lie, editing the paper was not that stressful since there were not a lot of corrections. To make it sound smart but still clear, it took a lot of back-and-forth. But trimming down the objectives was harder than we thought, it’s tough to cut stuff without feeling like you’re leaving things out. But we managed.

[paulinreese]

Week 7: We Had to Chill (Kinda)

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.

Next week, once we survive these exams (fingers crossed), we’re diving back in faster. But for now? We’re just trying to make it through without completely combusting.

[paulinreese]

Week 6 of Building Shoe Stride

So we’re six weeks into developing Shoe Stride, and honestly? It’s been quite a ride. We’ve been deep in the System Development Life Cycle (SDLC) using the Modified Waterfall Model, which basically means we had a clear plan but enough flexibility to tweak things as we went. And trust me, we needed that flexibility. At its heart, Shoe Stride is more than just a store; it’s a whole experience for runners and fitness lovers. We wanted to create a space where people can buy running shoes and accessories and even register for marathons without jumping through hoops. Sellers can list their products or events, either directly or through our marketplace, while customers get a smooth browsing and checkout process, whether online or in-store. Payments, pickups, deliveries- it’s all coming together in a way that just makes sense.

Looking back at the past six weeks, I can see how much we’ve built but also how much more there is to do. It’s wild to think that this started as just an idea, and now it’s actually happening. There’s still a long way to go, but we’re getting there as our motto is one step at a time.

[paulinreese]

Shoe Stride Progress

5TH WEEK : Successful Interview & Progressing to Chapter 3

This week, we had our much-anticipated interview, kinda nervous at first but glad that it went smoothly. The insights we gathered were valuable and will greatly contribute to our research. The conversation provided us with a deeper understanding of our topic, reinforcing key points and giving us new perspectives to consider. With the interview completed, we are now shifting our focus to Chapter 3. Our next steps include analyzing the information, organizing our data, and ensuring our findings align with our research objectives. This phase is crucial in building a solid foundation for the next chapters.

We’re making steady progress and are motivated to keep pushing forward!

[paulinreese]

SHOE STRIDE PROGRESS

4TH WEEK: Waiting for Interview Confirmation

This week, we focused on securing an interview with our chosen interviewee. We sent a formal request, explaining our project and why their insights are valuable. Now, we’re waiting for their response and hoping to secure a time slot.

While waiting for confirmation, we’re checking our questions and refining our approach. This phase requires patience, but we’re ready to move forward as soon as we get the go signal.

[paulinreese]

Week 3 progress of Shoe Stride

#week 3

This week, we focused on refining our research to ensure ShoeStride meets the needs of both runners and sellers. We began working on our manuscript, outlining the purpose of ShoeStride, its target users, and key features. This serves as our project’s foundation, keeping everything structured as we move forward. To support our research, we conducted a Review Of Related Literature, exploring studies on online shopping trends, running shoes, and e-commerce platforms. This helped us identify knowledge gaps and ensure our platform offers something valuable and unique. Then after reviewing our initial set of questions, we made a few adjustments to make them clearer and more effective. Our goal is to gather meaningful insights from both sellers and runners, so refining our approach was important.

With our manuscript and RRL taking shape, and our interview questions finalized, we’re now preparing to begin interviews and analyze the responses. These insights will play a key role in shaping ShoeStride moving forward.

[paulinreese]

SHOE STRIDE PROGRESS

#2nd Week

In our second week of development, we took a significant step toward shaping ShoeStride by preparing to gather real-world insights from the people who matter most runners and sellers.

Understanding the needs of both runners and sellers is crucial to making ShoeStride a valuable platform. This week, we focused on developing a set of well-structured interview questions. For sellers, we aimed to learn about their challenges, customer preferences, and expectations from an online platform. For runners, our questions centered around their shopping habits, pain points in finding the right gear, and what they look for in quality running shoes and accessories.

To ensure a smooth and professional process, we drafted a formal letter requesting permission to conduct these interviews. Once finalized, our instructor reviewed and signed it, allowing us to move forward with our project.

[paulinreese]

The Birth of Shoe Stride

#First Week

So for the first week, we brainstormed ideas for our proposal. We first thought about Threads and Treats but unfortunately, it was rejected by our instructor since he saw no future for this or it is not really unique. We understood and accepted his criticism beacuse it was for the better. With the help of his critiques and suggestions, we were able to come up with Shoe Stride.

ShoeStride began as an idea for a local store platform but evolved into a specialized hub for runners. After refining our concept with our instructor’s guidance, we plan to create a web-based store offering high-quality running shoes, accessories, and care products.

More than just a shop, ShoeStride provides expert recommendations, authentic reviews, and connections to local stores, helping runners make informed choices. We aim to enhance performance and support the running community one step at a time. Stay tuned as we continue to grow!