Hello!

This blogpost will be the one on this blog. And what would be the best way to end writing the blog than telling more and summarizing our group project.

When we started to do the app, we first aggregated the ideas of what we might need and use for the app. We designed the app to respond to our needs because it also answered to the many other people needs. That is how we ensure the app is for everyone interested in finding a friend to do sports with or wanting to find free sports events. We thought that because our app idea is so generally it is easy to make to meet the needs of many people. The app’s layout makes a user to feel peaceful and avoid frustration by providing an easy-to-use and simple app.

At the project I was team leader and make sure that we made everything on time. It was easy to remind the team about the deadlines, but it was hard to decide the time to meet the team. That was hard because we wanted to meet live when us schedule was different, so we had to make a time for the meeting. But this became easier as we switched to distance learning when we had much easier to find the best meeting time via Zoom. I lied if I claim that the global coronavirus pandemic did not affect to our project, because it affected us by making our schedules completely new.

How cliche it is but the project with the innovative team taught me that doing something together with different minds is not always effortless, but it is worth it. Why I say that is that many different thoughts make together a wonderful idea – or very stupid idea, which obviously does not agree with us. I am so proud of my team’s members because everyone participated in the design of the app with their ideas and did their job with honor. I have a mind image that we did the job equally.

Thank you for your time and goodbye!

Hello!

At the English course we had to read a chapter or two from the book. I read chapter 2 How we really use the web from the book Don’t make me think, revisited: A Common Sense Approach to Web and Mobile Usability by Steve Krug. I chose the book because when I looked for the book, what I want to read, I saw that the book had also some pictures and the text was not very formal. After reading I felt that I really understood the text and Krug has a point. In the chapter Krug tells how we use the web, why we use on that way and how web sites creators’ perception of user behavior differs from reality.

The chapter goes deeper about using web telling three most common way to use web. Partly I agree with Krug because those two ways are also same how I use the web. Usually, I scan the web sites and choose the first reasonable option. But the third way to use web is not same way how I use, because usually I read the introductions and other info to how to use the web unlike Krug tell.

Well I did not learn new information from the chapter but I got an important reminder. When we are doing our group project we should remember how differently the users of app think. Because usually users do not read everything, we should think and analyze precisely the place of the text and other important notes on the sites of app so that users notice them.

I think that someday I will read the book to the end because it seems very interesting and funny. I recommend the book anyone who is interested in web and mobile usability, and remember the text is not very formal.

Have a nice reading!

Hello!

In this post will I tell you about our group’s project. Additionally, I will tell more about how we address of system software. Maybe you do not know what system software is, but do not worry, I will tell you that too.

About our project

In our project we will make a mobile application, which idea is finding a friend to do sports with and finding free sports events. By free sports event I mean for example a football game for everyone who wants to play for fun and without commitment. The app is especially targeted at handicapped users. We have not made the app yet, but we have started to think how we are going to implement that.

Now I tell you about system software. When I started to think how to tell you about our app’s system software, I was not sure what system software meant. So, I had to seek more information about it and I found a succinct explanation. The system software can’t be uninstalled without affecting the functioning of other software. Also, this can help you to comprehend it: the system software provides a platform for other software and the operating system is part of the system software.

Because we have not done the app yet, I can’t tell very specific information about our app’s system software. We will build the app using MIT App Inventor, because it has ready code blocks and it the is only implementation that we know. The use of MIT App Inventor limits our app’s operating system to Android. I hope that we can make the app work on other operating systems as well.

I do not know what and how much memory our app will require from the device. What I know is that the app will use at least RAM. All mobile applications do use RAM, do not they?

EDIT: It may be possible that I had understood term system software wrong.

Hello everyone!

My name is Niina and I am 19 years old. I study Information Processing Science in University of Oulu. When I started my studies I did not have any experience in coding. Before my studies I thought that the most challenging part of my studies would be English. I don’t think my strength is in English skills.

If you never try you won’t ever win,

is my motto.

During my studies I have noticed that we have to read a lot of English texts and articles. Sometimes it is difficult to figure out the main point of the text. I usually try to understand the main point of the text first and if I do not understand I ask my friends for help. I think the problem with my English communication skills is vocabulary.

What is the project I am the most proud of? I think it is our homework on a programming course. On that course we learn to program in c language by programming an ATM. That was not a team project, but we got to work together and helped each other in all the challenges we could not solve alone. It was nice to solve the problems together. The most challenging part was solving problems and understanding the assignment. That project taught me to be thorough and persistent and to ask for help when having problems. Because that was my first and only project in programming, I am proud of it. 

We had six milestones in the project. First we had to analyze the operation of the ATM and then we made a harsh version of the code. Third, fourth and fifth milestones went step by step deeper into the code. Final, we made a report that included information about the program and test results.

I hope keeping this blog helps me learning to communicate in English.