Deven Wells
Engineering Design & Engineering Management
Aussie Exchange is a Java-Swing web application that pairs older adults in Japan with friendly Australian visitors for casual conversation, cultural sharing, or guided experiences. The goal: ease loneliness in Japan’s aging population while giving tourists a richer, people-first way to explore the country.
DEMO:
My Roles
Java-Swing Developer
- Implemented language-switching, authentication, and accessibility tweaks
- Refactored UI components after each round of user testing
Project Manager
- Set weekly milestones and kept the team of four on schedule
- Facilitated stand-ups & retros to maintain a healthy team dynamic
Documentation Lead
- Authored the localization summary, usability-test reports & final slide deck
- Ensured all deliverables met course and ISLO standards
The Problem
-
Social Isolation: Japan has the world’s fastest-aging population; single-person households and reported loneliness are rising.
-
Tourism Opportunity: Australian travel to Japan has grown 5× since 2010. We saw potential to connect these two trends for mutual benefit.
The Solution
-
Profile Browsing – Japanese users scroll a card-style list of vetted Aussies.
-
Secure Matching – Requests are encrypted; both sides approve before any contact.
-
Language Support – One-click language swap (日本語 / English); all labels auto-localize.
-
Accessibility First – High-contrast palette, scalable fonts, keyboard-navigable layout.
Cultural Localization Approach
We wanted to build more than just a translated app, our goal was to make Aussie Exchange feel natural and intuitive for Japanese users.
Research-First Process
Started with academic and online research to understand social issues in Japan (like loneliness among older adults) and cultural norms around design, privacy, and interaction.
Interviews with Cultural Experts
We talked with Japanese users and cultural experts to ensure our concepts addressed a real need, not just what sounded good to us.
Usability Testing:
Round 1
Our first prototype (Figma) focused on basic flow and structure. Feedback helped us fix spacing, labeling, and other quality-of-life issues.
Results
Usability Testing:
Round 2
The second prototype was built in Java Swing with full functionality. We tested it with four Japanese users (either native or fluent). Their insights changed everything.
JP Font Matters
Default Java fonts appeared Chinese. We switched to MS Mincho, a Japanese-friendly font, for all localized screens based on direct user feedback.
Replacing Commercial Imagery
Our original login screen used a Mt. Fuji photo that felt too touristy. We replaced it with friendly, human-centered visuals to match the app’s purpose.
Improved Interaction
Users tried clicking on flag icons to change languages, but only the small button below worked. We made the whole flag clickable for easier use.
Sorting Differences
Unlike U.S. apps like Amazon, Japanese users use fewer sorting filters. We simplified our browsing experience based on that preference.
Tech Stack
Frontend & Backend:
Java 17 + Swing
Authentication System:
Custom-built using CSV files and secure password hashing
Version Control:
GitHub Classroom
Create Your First Project
Start adding your projects to your portfolio. Click on "Manage Projects" to get started
Tinker Builder
Project type
Kid's Toy
Date
February 2024
Location
Terre Haute
In my freshman winter term I worked on a project called Tinker builder. The Tinker builder is a magnetic building toy four kids who are less abled. Users use magnetic rods and can pick a variety of different types of magnetic joints to build anything they want. For example, towers, 3-D shapes, static structures, and so much more. In this project we had to design the Tinker builder to be a toy that follows ASTM standards, as well as making sure that it is designed that anyone can use the toy , especially users with disabilities. In this project, we worked with reached services, a therapy center for kids and young adults with disabilities to work on life skills as well as helping them overcome their disabilities as much as possible. Since our project did heavily revolve around making a toy that anyone with a disability can use. We worked heavily with reach to make sure that the Tinker builder was a great and easy toy to play with.
Since this project had initially started earlier in the school year, I joined the team when there was a pretty solid version of it. This meant that there’s less of the idea to tangible product and more of testing and improvements to ensure that the toy was well suited for all stakeholders in mind. Because of this, I did not take much of a fabrication and designing role but in more of a leadership and tester. Due to our group having a good flow, we didn’t really need a huge leadership role however, I tried my best to make sure that the team was getting all the documentation and testing of our test results and new production of our improved toys. Additionally, I was the main person in charge of testing the Tinker builder and the variety of test we had to perform to make sure that it followed ASTM standards. Throughout this portfolio entry, you will see the tinker boat and how we tested some of the parts.
Even though I did enhance my technical skills on creating and designing parts in this project, I learned a lot more about the management of documentation and making sure there was a healthy and positive working environment. I also learned how to be creative and the way we can test a product to make sure that it is safe for all circumstances based upon ASTM standards. This project was a great opportunity and I am happy to be a part of the Tinker Bell team and make it into a toy. That users can love and enjoy.
