Wednesday, March 26, 2014

Team agreement for project 2

Project 2 Team Agreements

Antonio Bahena and Linsie Figueroa will communicate with each other on every aspect in project 2. We will share the workload in designing the website for The Goldfinch by Donna Tartt. Linsie will work on the development and design the layout of the page. Antonio will help with the wireframe design and wording for the site. We will work together on the research of the books audiences, author information and anything related to the book itself.

So to review the team agreements.

1.      Work together

2.      Communication with each other


3.      Help when the help is needed. 

Tuesday, March 18, 2014

Unit 9 Reading Response


The first reading talked about a basic set up for the ioS7 format for apple. It tells use how to set everything up and how each on of those elements will react in the IPhone set up and the I pad set up and as well as how it will look like when the devices in up right and on its side. The other reading for the week talked about the things that a designer is defiantly NOT supposed to when designing a site or app. One always has to plan out what they are going to do in the design. Have everything planned out and what is going to be done in the design. Make all the buttons links big enough to hit without having to zoom in on the site. Make sure that all images on the site are of high quality and work your way down from there or just use a vector graphic to design the site or app. Don’t over do it on the information that is on the site or app.to much information or images will overload the user and make them not want to use the site or app. So spared things out and give it room to breath. Make the app or site as easy as possible to use because not everybody uses an app or a site the same way at first. Just have to keep it simple. 

Related Links




Project 2 Issuu

Week 10 P3 Prelim Crit notes

1- We were told by the other group to go with the different green colors for the home page with the text instead of the icons but its nice to have the icons as options. The other group did like are font that we decided on for the app.

2- To add more color to the logo to give it more contrast and depth in the hands.

3- They asked why we decided on green for the app and we really did not have an answer for they on the color. We just thought it would be a good color for the app.

Tuesday, March 11, 2014

Application Definition Statement


The features that the user will like on the app

1.     Translate button.
2.     Settings
3.     Type and voice record
4.     Video records.
5.     Switch between the two different sign languages

The user

1.     Social workers
2.     City workers like paramedics, police officers and so on.
3.     People that have someone in the family that only communicates with sign language.
4.     Teachers with a student that signs

The main features of the app will be the record that will translate the person signing and tell you what they are saying. As they user uses the app they will slowly learn sign language as they continually use the app. The app will brake down the sign language and tell the user what they are saying and what motions are saying.

Week 9 Team Feedback

The changes that we got on the feed back was to make the app more of a learning app. We planned on selling the Open CV program as the main thing that would put the app apart from the rest of them. Now we will sell its as a learning app first and a communication second.  One of the things we were told to add is a feature in the record that will show what words and letters are as the person signs in front of you as you record. The learning feature was the only real thing that we should app for the app so it is a learning app and a communication app as well. When we do a light version the light will limit the features of the app not the language of the app.  

Things to add
- Learning feature
- Step by step in the record process that tells you what somebody is saying 

Template resources for project 3






Sunday, March 9, 2014

Unit 8 Reading Response

Tale of a top-10 App, part 1: Idea and Design, and Tale of a top-10 App, part 2 Marketing and Launch.


In this week’s reading we look at two different internet articles written by Jeremy Olson. The articles are about the highs and lows of app design and all the work that goes into having a successful app. The first thing after coming up with an app idea is to come up with a reason for that app to exist. Without a good reason for an app to exist, then that app is doomed to fail. The two articles were about the beginning stages of the app process to the end where they finally make it big and hit the apple app store. It felt that the main focus of the articles was on how Jeremy Olson got his name out there and made his contacts to help him achieve his goals for his app. To join as many clubs, groups, functions and social media sites as possible to get your name out there. To make sure that you take all possible chances early on to make as many friends, contacts and so on. These connections will help you later on down the road in your career. Stay in contact with those connections as often as possible with random emails to have a conversion with them and see how they are doing. You can also complement them on projects they are working on or have been working on because who doesn't like to have their ego stroked once in a while. Start to market the app in a variety of different social network sits to help get the word out about your app before you launch it. So when the day come for your app to hit the open market, you will cross your fingers and hope for the best.

Related Links

6 simple ways freelancers can meet people and make connections

20 social networking tips for web designers


How to design a mobile app

Tuesday, March 4, 2014

Unit 7 Reading Response


Chapter 10 Mobile: It’s not just a city in Alabama anymore
In chapter 10 it goes over designing for mobile devices. He also did talk about how we can do so much with are phones and having the internet with use at all times gives use the opportunity to find information anywhere we are. So when designing for mobile we are working with a much smaller screen then we are used to when we are designing for a desktop. One has to try and fit so much information on such a tiny screen. We want the mobile version to match the desktop version and that is just impossible. That’s why when we make a mobile design it needs to have what is important to that site at the time. In a mobile version we lose a lot of fetchers that we have in a desktop version. One of them is the hover aspect over a link. So in a mobile design we just have to assume that everything is clickable. Sometimes some of the links are not as clear as they would be in a desktop version. Those same links need to have some kind of dead giveaway that they are link and not just more content on the site.
We need to give the user an option of using the mobile version or the desktop version on their phone. Sometimes the user needs to find more information or something that is not in the mobile version of the site that the desktop version will have. I know I have. 

Links to related information for Chapter 10

Ten best practices for designing mobile websites

Mobile Web Mastery: 25 Tips on Designing for Mobile Devices

Mobile Responsive Design 101
10 Rules Of Thumb to Design a Successful Mobile-Friendly Website
Read more at