Week ten, our final week, I stayed up late most nights trying to make the mobile application perfect. I was determined to replicate the final prototype by our presentation date. Small details in sizing, color and positioning were now my primary focus. It was amazing how much time could be spent on these changes. Repositioning the UI elements over and over started to seem excessive but I needed them to be as perfect as possible. 

The day of our presentation I was extremely nervous as I was concerned about presenting. I am usually not the best at speaking in front of people. Luckily we had a demo in the paleo exhibit beforehand. I loved interacting with the staff and guests. The children had so much fun and took to the applications well. We instantly saw some struggling with application navigation that we didn't expect. Shreyas was able to implement some quick changes during the demo that would alleviate those issues.

Our presentation went great. The audience was attentive and afterward asked many questions. We guided the audience downstairs to test the applications. There was so much to talk about, so many more questions and ideas, it was inspiring to hear the feedback and suggestions. I really had a whirlwind of a time.


Although I am getting the visual side of Xcode figured out, I spent most of this week upset that I didn't understand the coding part still. The feedback I have received from others is that it will take a long while to learn Xcode. I can definitely see why. Charlie implemented some coding into my app as well as some notes to work with. I really want to figure this part out, but I am still a bit lost. Due to the new prototype I had to import all the new assets and create new constraints for those objects. I enjoyed this part because the design was much more sleek and consistent. All week I worked on the redesign along with googling the code part to death.

By Thursday I was able to finish the app without the QR code and dinosaur recognition functionality. We were ready to present to the museum and it felt so good to get to this point. On that Thursday though it did not go well. We were getting several different error codes coupled with a million password requests. Even though I saw all these error messages appear, I knew this was good. We could fix this so it doesn’t happen again.

Week 8: July 19th - July 25th

Wednesday, July 18th - I met with Shreyas at the office to discuss the coding aspect of the project. We planned a cram session.  Taking the  information we learned, we started on the visual side of the application. We pulled the visual piece of the app together, but with some trial and error. The most difficult part was trying to understand AR implementation, camera access, how to read a QR code, and 3D models. I googled this stuff for hours and I am  still completely lost. There was not one video or tutorial with a decent explanation. Shreyas and I stayed in the office very late. Hopefully I can better understand this when Charlie comes back into the office.

On Thursday it was a very busy day. We interviewed Jonathan Lazar and met with John Golden of Crux Collaborative. They had such great feedback for our projects. I felt very lucky that we got to interview both of them. Jonathan brought a really interesting point forward. His advice was to get to know the people you will be working with, in a more personal way, as in understanding their sensitive points, what pet peeves they have and what they like etc. This really makes sense, not only should you get to know users in this way, but also the ones you will be working closely with. 

John Golden walked us through the process that Crux Collaborative uses. His suggestions were great, which ultimately led us to initiate a redesign after our meeting. He described how we should not lead the user directly. We want the user to make mistakes to see where the real problems are. 

This week was very beneficial for us.

Week 7: July 12th - 18th

July 12th was a very busy day this week, not only was it the day that we had our group meeting, but also the day for Minnedemo 29.

That morning we questioned the flow of our apps. One app is for those without access to AR, and the other for those who can access AR on their personal devices. As a team we worked out the different steps, what would happen at each step, and what that screens would look like. We developed both paths in between meeting with Anna for our 1 on 1's.

The 1 on 1 meetings were planned in advance as a check-in point for each of us. Although I had millions of questions, I tried to narrow it down to questions regarding my near future. The meeting went well, yet the stress from the project started to weight in. I wanted to work on all aspects of the project, but this was not realistic. The readings and videos I watched about swift were not coming together for me, and I hoped this would clear up in the coming weeks.

It was raining very hard in the evening. The final minutes of my 1 and 1 with Anna were  pushing against the time that we had to leave for Minnedemo 29. Due to the rain, most of the team decided to head back home. Sandy and I decided we would go ahead and attend anyway. I was really impressed by the event. The people were very excitable, friendly, and interesting. It was well-coordinated and well-staffed. The presentation were inspiring. I definitely want to continue attending these events.

During this week I mainly tried to understand swift. As I am reading basic information about the program I am having a hard time understanding where it will apply, I also feel like this is going to be very challenging. 

Week 6: July 5th - July 11th

Thursday, July 5th. The interns had a video chat to discuss the prototype. It was a late call, and we realized it was best that we separate and work independently. We wanted to meet up in person, but by the end of the discussion, it was clear that we all had to narrow our focus on our individual tasks.

Friday, July 6th. Today we were lucky enough to host Ali Biro from LymanDoran. Ali’s visit to the Praxik office was to inform us about how we could improve our LinkedIn profiles. Since I am new to LinkedIn, I listened very closely. All the advice she gave was super helpful.  Ali had a warm personality, and she was easy to follow. Her advice was very transparent. She expanded on the importance of a clear heading, and how you can use a summary to your advantage. Other tips included the use of bullet points, what to exclude from your LinkedIn, and whom to include in your network. 

Thursday, July 11th. This was our day to revisit the science museum. We were all a little anxious as we had to present the prototype. As I sat at the meeting table I noticed that there were more people joining us - Annie, Trygve, and Manuel. We had some cord issues at first, but once resolved, Liam leaped in right away to explain our prototype. The meeting was overall a success. I felt that everyone, including those who joined in today, had so much input. The museum team was so innately creative and thoughtful.

During the week I read more swift tutorials and watched videos, the basics seem too simple, but I know it will get difficult very quickly.

One important topic that came up during the week was museum lighting. We were informed that AR can only work in well-light areas. This was something that never occurred to us. The paleo exhibit is rather dim, so for our next museum visit, we set aside 30 minutes to scout out lighting. 

In the meantime, I worked on the weekly blog and prepped for my 1 on 1 meeting with Anna. 

week 5: June 28th - July 4th

Thursday -  Best Buy Headquarters. This week we started off by visiting Best Buy Headquarters. Fred Beecher, Senior Manager of Experience Design Operations,  was kind enough to guide us through the building and speak informatively about UX at Best Buy and how it might relate to what UX might look like in the future for us. I realized that I didn't know all different user experience roles that existed. It was so helpful and a bit overwhelming. I just wanted to dive in and learn more about each of these UX roles, but we were running on a tight schedule already. We were guided through multiple floors where we meet with two different teams. Again, so much information! I thought everything was interesting and very inspiring. I am very excited to pursue UX.

This week we nailed down ideas for the prototype and defined our roles for the upcoming weeks. Our concepts had goals such as socially engaging, age inclusive, and accomplishable for our time frame. We need to be able to build it quickly and test it quickly. We listed features that we wanted to explore and ran them by the Praxik team. Some features such as animation and location-based AR would be more difficult. From here, we started to define roles and work with what was realistic for the time we do have. My focus will be on swift. I am cramming information about swift so that I can learn how to code this app. I have to relinquish other responsibilities to do this, but I am grateful for this opportunity to learn something new.

Now that our roles are more defined, I am focused on understanding the resources that Praxik provided. I will need additional material since this is very new to me. On the 4th and 5th, I spent the majority of my time bouncing between different materials. Charlie helped me with the concepts I couldn't understand. He is very patient with me, especially since I speak pure alien and am super awkward. 


Week 4: June 21th - June 27th

Thursday June 21st – Group Meeting. As a team, we re-worked and solidified questions that would structure how we gathered our observation data. Some questions were cancelled out due to information received from the science museum. Even after cancelling those out, there were several questions left over. Some pertaining to emotions, others how people interacted, and some regarding time in each exhibit area. In the end, we narrowed our questions based on correlated concept. At the end of the day it was discussed who wanted to learn coding. I definitely want to learn coding. I have no idea if I would be good at it or not, but I really want to take the opportunity to learn when I can.

Sunday the 24th - Observations. Observations day. Liam, Carson, Shreyas, Sandy and I met at the science museum for observations. We split up, each working on a particular set of data. I was timing each family at the different displays. Only after a couple of observations did I notice a pattern. The rest of my team spotted it too. Depending on what side the guests entered the exhibit, they, for the most part, had a similar path through the exhibit. I took additional notes, and was able to watch the habits of particular age groups, and listen to some of the reasons they decided to leave the exhibit. All of this information I thought would be useful to our prototype.

This week we focused on our professional resumes. As an introduction, Anna displayed her CV with airdrop on a large screen. We were all able to look at her CV and explain what we saw, what was unique. Her CV was so developed, meticulously put together, and informative. It made me realize that it would take me many years to accumulate a CV that was barely similar, let alone, understand where my resources were to do so. Anna gave us useful tips on CV development. Tips such as updating your resumes and CVs on all platforms, not just one. To update as frequently as possible. For example, our internship. We should have already included this in our resumes.

Week 3: June 14th - 20th

Friday, June 15th, our team had the opportunity to interview Jeff Johnson. On the video call we asked Jeff questions from a list that we prepared. I was excited to hear what Jeff had to say. He had so many tips and scenarios that he was able to provide us with. I wanted to ask him so many more questions, but felt so lucky to have the information he provided us with. He had great points to make, one being always keeping the eyes of a new user so that you don't become comfortable with the design and overlook the flaws.

On Tuesday June 19th, Sandy and I met up early  to have another look at our research questions. Although the questions seemed strong,  there were some we had to eliminate because they were already answered through our research or in  documents provided by the Science Museum. 

Anna helped us by identifying our questions as exploratory. She also noted that we did not have an overarching question. Sandy and I brainstormed to identify a strong overarching question and then wiped out  the rest of the questions we had except 3. From there, we reworked our questions, and started to explore the idea of using a survey.

I am trying to learn about how to navigate and create mock-ups in Adobe XD. Anna informed us this is something that we need to start getting familiar with. The videos Adobe provides on XD helped me understand the layout of the program, as well as what it can do in it. I noticed that I was intimidated when faced with a blank board, but I am hoping to find creative ways to work in the program. 



Week 2

This week our team focused on research methods. Research methods are very new to me. I didn’t know anything about research methods except for formulating a hypothesis and testing the hypothesis.  From the readings, I learned about cognitive walkthrough, heuristic evaluation, and model-based evaluation. 

Anna met with us to go over our schedule. She discussed with the group what we should be expecting over the next few weeks.  A timeline is needed to keep us on track, as well as research questions so that we can answer important questions that will help shape our prototype.

On June 14th, Thursday, I was able to attend a UXPA meeting because Anna gave me her ticket. I was excited to go but did not know what to expect. The meeting was held in Minneapolis. Code 42, a software company, hosted the event. A few of the code 42 employees were able to discuss their experiences during the software creation process. Since, their software backs up and recovers data, the theme of the UXPA meeting was security. 

Multiple interesting points came up regarding the difficulties of their project. Personas were hard to nail down, there was backtracking, and security professionals had little time to spare for them. One point brought up, was that, you aren't just selling to the user, but also the buyer, and while designing you have to take that into consideration. Not everyone will be able to navigate the same interface. 


The first week of interning at Praxik, I was immersed in research. On our first day, Anna revealed our client (The Science Museum of Minnesota) and made clear what we were to accomplish this week. Several articles were assigned which we started reading immediately. Midday each intern discussed their goals with the team. This was our first assignment due before our first meeting. During this discussion, I reevaluated my goals, some goals were unrealistic, some misdirected. Anna introduced us to augmented reality. Throughout the week, the assigned articles started to give me a clearer picture of what to expect, and what information our group should gather to create a prototype. Research is an extremely valuable part of this process. I feel that there is so much to learn. It will be essential to keep researching throughout the project, as familiarizing myself with terms and concepts will need repeated exposure to understand what the most beneficial information for designing the process and prototype.