Evaluation & Learning Outcomes

This will be the final Blog post as part of The Magna Carta Translation Application. Today we have finished and handed over the project to the client alongside this we are concluding the assignment in terms of submission of all appropriate material.

We started this project back in March where we was introduced to the design brief and project requirements. Since then we have developed as a group/agencies learning skills that will be vital to progressing into the same client based projects outside the university. Starting with no prior knowledge of applications, how they were developed or the work that needs to go into producing a successful application, delivering the application shows how far we have come.

Completing the application has allowed us to gain swift coding, design, client communication, team working and documentation skill in connection with a client lead project. Throughout the project we have tried to remain transparent by communicating information, issues and requirements to the client as to keep the project as progressive and slic as possible.

Our Application

The Final Application we feel has been a huge success. We have achieved many things we didn’t expect to from our outset, initially we were sceptical about producing and information based application however this made us focus much more on delivering a professional application for the client.

With clear communication and presentation the the client we proposed and application that they felt fitted a very functional and specific requirement. Initially there was ambitious ideas thrown around by the client that we framed proposing and application that fitted both parties expectations and needs. One main achievement was overcoming a client proposed idea of The Magna Carta image as a form of navigation between clauses with the document. We initially felt this was slightly ambitious as our knowledge of Swift and application programing was very basic but with some support from tutors we managed to formulate an understanding of Swift which then allowed us to create this application.

Some other successes with programming was gaining and understanding of iPad specific application building and Split View Controllers, that allows 2 different types of view controllers to run within a single view. This is something even the tutors were mystified by initially but we managed to negotiate it well creating a useful feature of the application.

Working With Live Brief

Creativity and Professionalism is part of any client based interaction work no matter the product in production or timescape of project. Creativity is need  throughout all aspects of the project weather is designs, innovative ideas or pitches/discussion with clients. Creativity not only is the ability to produce ideas Remaining professionally throughout the project even when tricky and potentially problematic situation arose. Client negotiation is one situation where we had to remain professional, taking on board their ideas and feedback working with them to develop a product that they wanted and we could build successfully. Secondly when issues surrounding content and from the cathedral and 3rd party sources it was essential to remain professional and taking control of potentially problematic situations.

The Team

As part of a team we have work effectively and efficiently through good communication and organization of the work and timings. Using a social media site we were able to communicate effectively to each other gaining quick responses from all members of the team. Because of it ubiquity meant all members were quickly notified of discussions and organisations of meeting meaning workflow wants hindered or disturbed but miscommunication or un attendance as a point of contact was readily available.

Facebook Group
Facebook Group

Trello was used in organizing the workflow and delegation of tasks similar to that of a scrum board. all members had access to a live scrum board where they could interact with tasks that needed to be completed within the project. This highlighted if there was any issues or backlog with work as it was regularly checked and assessed by all members of the team.

Trello
Trello

Google Drive was used to shear and distribute files between members of the group, Being able to upload revisions of files ment there was less confusion and the the project documents were kept in the same place.

Google Drive
Google Drive

A Git repository was used in the development of the application also to track the development of the application, allowing merging between programmers files and back logging where needed. The git repo additionally gives any developer who needs to pick up the application after handover the ability to see how it was made and where specific changes took place. This is a great form of documentation for the client as it gives them a breakdown of how the application was made and the process that went through its development.

BitBucket
BitBucket
Keeping to Guidelines 

During the project there was a series to guidelines of which we had to follow and be aware off.  Firstly the design guidelines given to us by Salisbury Cathedral and RedBallon that we had to keep to pedantically making sure we always referred to there style guidelines. These outset design guidelines were colour, font and style based and it was necessary to keep to their exhibition they have recently built tieing the application and exhibition together.

Secondly keeping to apple guidelines with programing and styles of elements within the application. Specifically we looked at the design guidelines paying particular attention to sizing, icons and gestures that meant the application fitted smoothly within an apple device using its ubiquitous apple.

Summary

Through this live brief we have produced professional application fitting clients requirement learning lots of vital skills along the way. Handing the application over to the client now it will be great to see it working within the desired location helping and informing tourist visiting the Salisbury Cathedral for filling its purpose.

Advertisements

Programming: Final Changes

As we come up to the final week, we’re just adding the final touches to the application to make sure that it is the best product we can provide for the client.

Last week we were given the final translations and contextualisations to use in the app from the client, so the first step was to add these into the code. After we did this, we noticed that they were significantly smaller than before. Because of this, the detailView seemed far too tall compared to the text inside it.

Originally the detailView was 500 high. This value was just an estimate size as it stuck throughout most of the development. First we tried lowering this down to 300. This worked well with some of the shorter clauses as the box didn’t drown them, but with the preface and suffixes, it seemed to be far too small and required too much scrolling. We went for the final option of 400 high. This was a good middle ground between being small enough for the shorter clause translations and big enough for the larger ones.

While doing this, I went through and cleaned up the code. This meant adding comments to functions and deleting excess line breaks to make it neater and easier to read. Commenting the functions and code is essential when handing the project over to someone else, and is always good practice to do just for myself. It is a way of always knowing what the code does and why it works/ was included. Sometimes what seemed like a simple thing to write at the time can seem complex and difficult to understand a week later. Commenting the code speeds up the workflow and is a good professional practice to get into so the code is clear and easy to read, edit and understand.

I also removed the swiftyJSON.swift file from the code. This remained in there from when I experimented with using JSON to get the translations into the code. There were also some old image files left in the project folder from when I was testing for the best solution and images to use. It is good practice remove excess files and text to keep file sizes to a minimum. Its not good to bulk out the project with assets and code which aren’t even being implemented as it makes it cluttered takes up unnecessary space.

Stating the Final Idea

In recent weeks we have had lots of discussion with our client on an effective solution to their proposed application project. We have partook in several negotiations ( Presentation 1 & Presentation 2 ) with the client discussing ideas, designs, audiences and concepts. There have give us feedback on several occasions (Feedback) of which we responded to in quick and effective manner. From this we set out expectations of the product/app in our MoSCoW to identify key features connected to our concepts and ideas

Our final idea is as follows

We will be creating an iPad application using an image of Magna carta as a navigation interface, this app allows the user to zoom into and explore the intricate details of the document. The document will have overlays on each clause with a tappable hotspot to let the user see more detail about the selected clause. The clauses will be filterable by category to allow the user to see the specific clauses which interest them.

We have decided as a group to progress with this application because we feel that it meets the clients requirements for the project and is slightly different to what other groups proposed as it’s more to fit a specific need/purposeful for the cathedral. Also,  taking on a less optimistic application means it can be developed and refined to a high professional standard.

Meeting the brief 

For 2015 BU’s RedBallon Agency has been commissioned to create a app for SalisburY. Cathedrals Magna Carta exhibition in 2015. The app has been conceived/proposed as a series of exploratory interactive and educational works that can be accessed while walking round Salisbury Cathedral

As discussed with the cathedral our application will be fulfilling the outlined  of providing an interactive document for tourists to use and explore the clauses within the document and take a better look at the document digital through the use of a super high res image that will allow extensive zoom capabilities. The app plans to provide an informative and interactive to take a look into a rigid document that is difficult for the majority of audience members to understand its importance but, particularly what it says and what this means.

How we have or/plan to meet learning Objectives 

  1. An ability to control and creatively exploit the associated hardware and software; –  Build an application that is intuitive and adds an aspect to audiences experience that non digital or the cathedral cannot provide
  2. Originality, creativity and professionalism in the interpretation of a live brief, production conception, pitching, management and realisation of interactive media artefacts; – Within our presentations we have remained professional, throughout our presentation of ideas and dialogue with them in regards to ideas using their feedback to fore most develop our idea to there satisfaction.
  3. The ability to work effectively as an individual as well as part of a production team; – Remaining professional at all times we aim to work effectively to produce an professional application that for fills the needs of the client furthermore improving the experience for audiences at the cathedral.
  4. The ability to evaluate work undertaken in a reflective manner with reference to appropriate debates and conventions. – Working together as a team where we will self evaluate and group evaluate our progress, work skills and products to push forward the project.