Shortlist for App Features
Posted by Briony Gray in Design, Engineering, Structure and Story on 07/03/2015
The group is now in position where a wide range of background research has been conducted. This takes the form of Similar Applications, Market Research and Literature reviews for specific features. Consequently, determining a short-list of features which the TravelSafe app will utilise is the next design and engineering step of the project. As the project has the final objective of producing a fully researched and designed idea which is then ready to be subjected to qualitative and quantitative testing (which will require more funding and time than a group project is able to), we have enlisted the help of individuals who are considered experts in their field. In order to objectively evaluate the short-list of app features we have used purposive sampling to select a number of experts from ranging backgrounds. These include Engineering, Web Applications and Solutions, Web Master, and Senior Technical Advisor. This is a guidance solution regarding how we should structure and decide on the features of the TravelSafe app without breaching extensive qualitative and quantitative testing.
The experts were identified as being useful or relevant to our project interests, and then were contacted via email. This provided an easy medium for conversation without being formal. Initial contact with the expert explained our project scenario and requested that, if they were willing, should read the short-list of TravelSafe feature apps and answer 4 short questions regarding these. In addition we strongly encouraged any other thoughts or guidance throughout. Each expert gave permission to use their name, job title, expertise and answers in our portfolio. The feedback received can be found in the Expert Opinions post.
The short-list which the experts were presented can be found below:
1. Safest Route Generator – This generates three safest routes from point to point in real-time
2. Area Information Safety Rating – This is used for areas using open data crime statistics and social media
3. Local Travel Information Updates – This provides local bus and train times, locations of these, and weather information Weather updates.
4. Safety Information – This is generated from locational based RSS feeds from embassies, social media and news feeds.
5. Emergency Contact Information – This is done through user input which an individual stores travel information such as flight numbers, travel insurance, credit card numbers, and emergency contact details.
6. Downloadable Resource Pack – This allows the user to choose a location and download above features (such as travel information or safety information) which can be accessed while offline. This combats roaming charges while travelling.
7. Blogging Features – e.g. photo and video with GPS location – Links to social media e.g. photo and video
post uploads, blog posts.
8. Family Alerts – This features a danger button to send location to designated contacts, and/or emergency services or the police.
9. Flight Information – This provides information from airport/airlines with notifications for specified Pack offline.
This post also represents that the group has chosen appropriate design and engineering choices that directly link to the marking criteria, which are vital to understanding which features that the product will have. These are based on Contextual Factors such as market analysis, evaluation of existing products, and identification of app features. There is evidence that the design and engineering steps (app features) have been chosen intelligently (by reference to literature and analysis) to produce a conclusion of professional quality, leading to a successful product.
In addition there is evidence of Structure and Story, as the post explains why these were chosen, how they were chosen, and that these will shape the development of the project.
Written by Briony.
Meeting Summary 05/03/15
Posted by Taekyun Kim in Meeting Summary, Structure and Story on 05/03/2015
Meeting Summary 05/03/2015
During this meeting the group met and discussed the project with mentor Rob Blair for the first time. This included showing the progression the group had made since the initial meeting and the next steps which had been decided. Based on Rob’s feedback the group came to the conclusion that a number of planning and research posts would be useful in the development of the project.
1. Create planning layout for the project. This could include other media such as a gannt chart. It should also allow an extra line underneath the predicted time so we can record the accurate timings, compared to the times we set for each task. This requires planning out each of the tasks step by step before making the chart. This is important for the project as time management and the identification of tasks is vital for the completion of tasks in the time scale that the group has set.
2. A blog post about methodology we are going to use for meetings and producing work (for example, agile/scrum/life cycle). This should explain that we have looked at these and have selected one according to our task and how best we work as a group. We are currently using an agile methodology as we all discuss and contribute ideas/research rather than one person focusing on a large part. This is an important consideration as it may dictate the success of our project depending on how best group members work, therefore it should be identified early on in the project.
3. A blog post about the target audience, identifying specific types of people who would find it the most useful (for example, tourists/students/people new to an area). Using literature and market research the post should identify which types of people would be willing to pay for it a safety travel app and why. It should also consider whether every user has the same needs from the map/other features. It should conclude that based on the market our app should be free. This is an important contribution to the research as the success of the product may be depended on understanding what the target audience may want from our product which isn’t already on the market.
4. A blog post defining our success criteria. This should be a list of our goals and objectives based on the marking criteria. For example we aim to produce a project that should take X amount of time. This is important to the planning stages of the project as it will provide continual structure to the narrative and will ensure that the work out-put answers the marking criteria.
This post represents that coherent structure and story are present in the portfolio which uses the entry and tags mechanism of the blog system. It tells the story of the project by explaining individual roles clearly, explaining why these were decided, and what outcome they will produce later on in the project.
Minutes by Briony Gray
Similar Applications
Posted by Emily Pearce in Contextual Factors and Research, Innovation and Creativity (Idea) on 05/03/2015
As part of the research the group conducted into the market and the features we wanted to include, the group wanted to find out what is already out there. There are huge numbers of articles referring to the best travel apps, but below is a breakdown of some applications available on different platforms and that each have a different feature that is going to be incorporated into TravelSafe. At the bottom of this posts are links to related articles from a number of different sites and contributors identifying the top travel applications.
Journi [1]
- social network for sharing posts (pictures and notes with geolocation) to a shared timeline
- can invite friends and family and send them automatic updates in real-time via web/app/email
- further sharing to Facebook and Twitter
- Apple only, Free
- weaknesses: lack of geographical ties or tagging, no offline resources, no travel information.
StaySafe [2]
- GPS tracker app that emails or texts the users exact location to emergency contacts if you don’t check-in (e.g. after working, socialising, travelling alone)
- Works with “sessions” – need to have checked in by end of session
- Apple and Android, £4.99
- weaknesses: No offline resources, no user input to improve safety ratings, expensive.
AroundMe [3]
- finds nearest restaurants, banks, gas stations, book hotels
- Apple and Windows phone, Free
- weaknesses: No real time updated information, no travel information, no offline resources.
EmergenSee [4]
- With just a click of a button, you can transmit video, audio and GPS to your selected friends and family so that they can hear, see and track what’s going on. They can alert authority if you can’t
- Apple and Android, Free
- weaknesses: No user input to improve datasets, no travel information, no offline resources.
TripIt [5]
- consolidates all your travel reservations (hotel, air, car rental etc.)
- Can share itinerary with friends and family
- Apple, Android, Blackberry, Free
- could link this to travel alerts and updates?
- weaknesses: No specialised travel tool such as a route generator, no safety ratings.
AllSubway [6]
- maps for subway and metro in cities around the world
- Apple only, 79p
- weaknesses: No safety information or tips, no offline resources, competes with paper copies in a city.
Road Buddy [7]
- checks publically available police data on criminal damage, drugs offences, public disorder and violent crime and then plots a route avoiding as many as possible on Google Map
- Firefox OS only but planning to expand
- weaknesses: No offline resources, no user input to improve datasets.
SafeRoute [8]
- US only
- Android only, 60p
- provides GPS enabled crime statistics and safety levels for every city in US providing there’s enough crime data
- Provides safety levels for each zip code in some major cities
- Also has comments from users section
- Removed from app store due to pending patent infringements
- weaknesses: Not an original app, no user input, no offline resources, no travel information.
Conclusions
It is apparent through market analysis that a majority of travel and safety apps either do not charge for use, or charge a minimal amount. Therefore in order to keep within the trend of this market TravelSafe should do this is also, which will ensure that it fits the needs of the target audience. Another key trend with the apps evaluated is that often the name of the app corresponds to the basic concept of the project in a few words or less. Again, this is another consideration for the group’s own project, which the current name TravelSafe reflects well. Finally, a noticeable trend with the apps reviewed is that none of them feature more than a couple of definable features, such as emergency contacts input or travel information. This is where the TravelSafe app will find its niche market as it will combine multiple features where existing apps only combine two or three. In order to decide on these apps however, the group has asked for expert advice to help guide the project as the success criteria dictate that the project must not be subjected to extensive qualitative or quantitative tests at this stage.
Based on the weaknesses of these apps, the group are now in a position to create a short-list of app features which other apps in the market to not appear to fully meet. A large consideration for this list is for the TravelSafe app to utilise multiple features. The combination of these features will ensure that TravelSafe is unique, and offers something more than the others on the market.
This post represents that the group has chosen appropriate economic and social Contextual Factors that directly link to the marking criteria, and are vital to understanding what requirements the product will have. These take the form of market analysis, evaluation of existing products, and identification of app features. There is evidence that these have been chosen intelligently (by reference to literature and analysis) to produce a conclusion of professional quality, leading to a successful product.
In addition there is evidence of Innovation and Creativity which is shown via tailoring the group project to address existing weaknesses of app’s in the target market. Subsequently this shows that the product has gone beyond expectations by meeting a genuine gap in a market, which leads to a commercially viable product idea.
News Articles
“The World’s 50 Best Travel Apps” – David Clack (http://www.timeout.com/travel/features/1169/the-worlds-50-best-travel-apps)
“10 best travel apps for iOS and Android” – Jessica Naziri, 2014 (http://www.techradar.com/news/phone-and-communications/mobile-phones/best-travel-app-1278014)
“Best Travel Apps for 2015” – Alexandra Talty, 2014 (http://www.forbes.com/sites/alexandratalty/2014/12/11/best-travel-apps-for-2015/)
“Top 20 best travel apps: recommended by SkyScanner” – James Teideman, 2013 (http://www.skyscanner.net/news/top-20-best-travel-apps-recommended-skyscanner)
Written by Emily.
References
- Journi, 2015, Travel Blogging rediscovered [Online] [Available at: https://www.journiapp.com/] [Last Accessed: March 2015]
- Safe Apps Ltd, 2015, Stay Safe – Smart Personal Safety [Online] [Available at: http://www.staysafeapp.com/staysafe-personal/] [Last Accessed: March 2015]
- Flying Code Ltd, 2015, AroundMe – Because you’re going places [Online] [Available at: http://www.aroundmeapp.com/] [Last Accessed: March 2015]
- EmergenSee App, 2015, EmergenSee Personal Security System [Online] [Available at: http://emergensee.com/] [Last Accessed: March 2015]
- Concur Technologies Inc., 2015, Tripit – All of your travel plans on-the-go! [Online] [Available at: https://www.tripit.com/uhp/mobile] [Last Accessed: March 2015]
- AllSubway, 2015, AllSubway [Online] [Available at: http://carmat.altervista.org/AllSubway.html] [Last Accessed: March 2015]
- Warman, M., 2013, Road Buddy mobile app plots safe routes to walk home, The Telegraph [Online] [Available at: http://www.telegraph.co.uk/technology/news/10047029/Road-Buddy-mobile-app-plots-safe-routes-to-walk-home.html] [Last Accessed: March 2015]
- GeoOasis Inc, 2011, SafeRoute, [Online] [Available at: http://www.geooasis.com/SafeRoute/] [Last Accessed: March 2015]
Project Requirements
Posted by Emily Pearce in Contextual Factors and Research, Design, Structure and Story on 04/03/2015
Requirements Gathering
As the group has undertaken the research and design aspects of this project first, with the aim of completing market research and expert opinions before implementation, requirements gathering was undertaken in group meetings by developing ideas about the potential users of our application and the functionality that would be included in the TravelSafe application. Due to the way that this project has been undertaken, these requirements are to provide an idea of the functionality and limitations of our application and may change during the market research stages. This has been influenced by background research that includes the evaluation of Similar Applications. This lead the group to conclude the most important functional and non-functional requirements for the project, which are stated below.
Functional Requirements
The system shall be able to:
- allow a user to search and select a location based on GPS data
- allow a user to select a location from a list of saved locations
- For each location, it must be able to:
- generate three point to point safe routes using area safety ratings
- provide a safety rating of a user’s surrounding area based on publicly available crime data
- provide travel information from publicly available times and map
- provide safety tips using open data from Government and police service
- provide an updated news feed from RSS feeds of news source
- download a pack of the above data that can be accessed and used offline from on-device storage
- allow users to access and search through a list of Frequently Asked Questions (FAQs)
- provide translation functionality through use of Google Translate API
- have a section dedicated to user-input information as free text
Non-Functional Requirements
The system should:
- be a web-based application
- provide a comprehensive list of help and instructions for use
- use a consistent style, layout and colour scheme throughout the application
- take all reasonable steps to improve accessibility
- be intuitive for use
- be compatible with Internet Explorer, Google Chrome, Mozilla Firefox and Apple Safari to ensure compatibility with mobile browsers
Constraints
The application will be limited by/not be able to:
- the accuracy of the GPS hardware within a mobile device
- provide external backup of data
This set of finalised criteria were chosen from the extensive discussion of the merits and drawbacks of the potential features, combined with the research into similar applications as well as project constraints such as the time available and the skillsets of the developers within the group. The group feels that the finalised requirement are representative of the type of application that is being suggested, with the quantity of features providing the unique selling point to allow the group to target a niche in the market identified during research utilising both development and time management skills of the group as a whole.
This post represents that coherent structure and story are present in the portfolio which uses the entry and tags mechanism of the blog system. It tells the story of the project by explaining individual roles clearly, explaining why these were decided, and what outcome they will produce later on in the project.
This post also represents that the group has chosen appropriate economic and social Contextual Factors that directly link to the marking criteria, and are vital to understanding what requirements the product will have. There is evidence that these have been chosen intelligently (by reference to literature and analysis) to produce a specification of professional quality, leading to a successful product.
In addition design considerations for the project have been addressed in this post. This is evident through the layout of steps that the project should include, how these have been decided, and how this will be implemented to solve a problem.
Written by Emily.
Project Planning
Posted by Ayoub Elgassier in Design, Media Use, Structure and Story on 03/03/2015
Project management tools are vital for a successful project (Bakouros, Dr. Yannis, 2000). Likelihood of proportion of occurrence of mistakes would be reduced by implementation of these tools (Bakouros, Dr. Yannis, 2000). The project environment has a high chance that unexpected conditions might occur. For example, unpredictable results might be found. These might be a reason for failing the project, or it might reduce the quality of the project. Therefore, utilizing the techniques and tools of project management could be a key to overcoming these issues. Advantageously, the former offers a project team the chance to identify uncontrollable tasks as well as controllable ones (Bakouros, Dr. Yannis, 2000). Consequently, The One Percent team decided to choose a Gantt Chart as a suitable project management tool, as it provides features (discussed later) in addition to ease of usability.
The Gantt chart is a “project planning tool” offering chance of tracking tasks and activities of the project(Durfee, 2008). The reason behind chosen this tool is the simplicity of construct the tasks and tracking tasks and sub-tasks (Durfee, 2008). Gantt chart can be used to order and schedule tasks and activities of a project, each of which is pictured in horizontal bar over time (Durfee, 2008). each task takes a place in a row where Date takes a place in a column (Durfee, 2008). Start date as well as end date are recorded in order to compare whether goal is achieved or in a risk. To implement Gantt Chart, the online Smartsheet application is used. This smartsheet offers features as follows:
- Simplicity of use in terms of tackling icons, drop and drag, and also import and expert features. In addition, it can be incorporated with google sheet.
- It allows you to have a cooperation with other participants. It provides, for example, alert feature which it can send over an email to them for reminding.
- Completion feature, which is calculate the proportion of accomplishments out of 100 and also number of days that have been spent, is useful.
- It can be also set a rule in order to specify each member’s tasks with using a certain color.
There are three main phases in TravelSafe project plan, each of has sub tasks assigned to a team member. The phases are:
- Planning phase consists of six task each of which has sub-tasks.
- Design phase consists of six task as well.
- The final phase is future works which are survey, focus group and testing the application.
The following pictures illustrate a part of planning stage of our project using Gantt chart. To read full plan online visit the following link: (Full project plan) and to download PDF version click on Full Project Plan PDF.
In conclusion, this blog aims to show the importance of project management tools to improve project time management. Therefore, this project lists the Smart sheet named Gantt chart which is being used in The One Percent project.
This post represents that coherent structure and story are present in the portfolio which uses the entry and tags mechanism of the blog system. It tells the story of the project by explaining individual roles clearly, explaining why these were decided, and what outcome they will produce later on in the project.
In addition this post represents Media Use by incorporating a gantt chart as a method for time and resource management.
This post also represents that the group has chosen appropriate project steps that directly link to the marking criteria. The project steps were chosen intelligently to produce a project of professional quality, leading to a successful product.
References
Bakouros, Dr. Yannis, D. V. K. (2000). Project Management, 0–32.
W. Durfee, Oct 2008, Project Planning and Gantt Chart
Success Criteria for our Project
Posted by Briony Gray in Design, Structure and Story on 01/03/2015
An important aspect to take into consideration for this project is that we will not actually make a final functioning product that will be distributed to the public. As this project is a group coursework that is part of an assignment we must instead set out some parameters for success that are dictated by the assignment specification, and do not end in the commercial distribution of a product. To ensure that our project is on course and will fulfil the assignment criteria we have written out some ‘success criteria’ that we will aim to complete by the end of the assignment. These are taken directly from the marking scheme, and also our specifications of our project. Our portfolio will address these issues throughout:
- To have submitted a project brief (approx 200 words) that summarise our project and how we will go about organising its different stages.
- To have kept a running blog (portfolio) of our activities as a group throughout the assignment process, on which each member will post work and research associated with the project.
- To have evidence of participating in meetings with their appointed project mentors, and with other members of the group throughout the assignment process. These can be found throughout the blog entitled ‘Meeting Summary’.
- To have submitted a reflective summary by each member of the project team at the end of the project.
- To present a summary of our project followed by a Q&A session at the end of the assignment.
- To have a project that uses design appropriate social network solutions and interface or extend the designs of existing social network infrastructures.
- To have written evidence of being able to identify and analyse social network characteristics in the portfolio.
- To have written evidence of being able to identify and interpret domain and societal requirements for the deployment of social network solutions in the portfolio.
- To have evidence of group work and group organisation throughout the entirety of the project.
- To have evidence of clear stages of planning and research throughout the project, with equal contributions from all members in a number of topic areas that may include design, research, graphics, and technical issues.
- To produce a finalised description of our project at the end of its course, which includes explanations of its different features, the methodology used to select these features, and a realistic prediction of how this product may be used by the target audience.
- To have clear evidence of market and user research which have been used to underpin the design and technological choices of the project.
- To have clear evidence of tailoring our project based on research undertaken, literature reviews and expert opinions.
- To have submitted a portfolio that demonstrates a social networking solution to a gap in the market which has been undertaken in a professional and well organised manner, and in an original way.
- To have a product that has been developed to the point of needing further testing and qualitative research (which requires funding more than our means, and more time). This means that the product, at its completion, will have extensive background research, design stages, and engineering designs and may only be improved through further testing to the wider public which we ourselves are unable to do. This is a realistic goal for our project as it demonstrates an ability to produce and work on a product to a high standard, but also realistic time management as this product has a limited time and is run alongside other courses and coursework.
These success criteria will be revisited at the end of the project, entitled Success Criteria Revisited, and an analysis matrix will be added to show which criteria have been met. This will provide a clear indication of the aspects we will aim to provide throughout the assignment process, and will help to guide our planning, research, and final product.
This post represents that coherent structure and story are present in the portfolio which uses the entry and tags mechanism of the blog system. It tells the story of the project by explaining individual roles clearly, explaining why these were decided, and what outcome they will produce later on in the project.
This post also represents that the group has chosen appropriate criteria for the success criteria that directly links to the marking criteria, and subsequently shapes the steps and outcome of the product. The success criteria were chosen intelligently and realistically to produce a project of professional quality, leading to a successful product.
Written by Briony.
Choosing an Idea with an Analysis matrix
Posted by Briony Gray in Innovation and Creativity (Idea), Structure and Story on 28/02/2015
After our initial meeting we decided to go away and individually research a possible idea for our group project. We wrote out 15 criteria that these would be marked against by using the assessment criteria listed in the module’s resource specification. In the next meeting we pitched each idea to the rest of the group, and discussed our thoughts and considerations on a number of topics. For instance, if there was a limitation to someone’s idea we discussed a way in which it could be improved or changed to better meet our deciding criteria before deciding on a project. Once each idea had been pitched and discussed we wrote an analysis matrix, plotting each of the ideas against the criteria and one another. This allowed us to clearly identify stronger ideas based on the assessment criteria, and is shown in the table below. Taking each score into account we also held a group vote so that each member’s concerns and preferences could be taken into account. The list of our 6 ideas are explained below:
- Meeting scheduler
The number of back and forth emails that have to be sent to decide on a convenient date for both people, with tools and technologies available to us, planning a meeting should be a lot easier than it is. Existing technologies like Google, Apple and Microsoft calendars haven’t made this easy on a large scale, however smaller versions and applications exist. Therefore I propose a single page app that that allows users manage and schedule meetings; including meeting places and times. The main Technologies is will use are HTML 5 geolocation, Email API, Google MAP and Places API, and a Calendar. Useful features may include the use of common types of meeting Templates, frequently used days, time and places, meeting with multiple people, a Mobile app version and a possible business case. It would benefit members of a business, friends, family, and institutional staff.
- StudnetLinks
Although this idea is widely known and fairly popular it still poses a problem for students. This idea addresses the limitations in the article “Can social network improve project management”, and can be tailored specifically for group coursework for university students. The key areas it addresses are students complain that “group coursework” assessment is not fair sometime, despite of distribution of marks, and international students facing social and communication problems because of originating from a different education system. The focus therefore is workgroup assignments and final projects, aiding all types of students from different backgrounds in order for them to feel like the work has been fairly distributed. The features of this are as follows:
– All modules have their own page each of which can allow students share their profiles. This is in order to help students get each other and each one knows others’ skills.
– Each student posts their skills, his/her background and area interested in.
– After students grouped up a close and secrete should be created.
– Each group page should provide area for update codes, Q&A as well as enables students to schedule tasks and alert them at the deadline for each one.
– At the end of coursework, a report on proportion of student’s contribution should be issued (AS GITHUP)
– An area for posting stuff related to the modules (AS A DISSCUTION AREA IN BLACKBOARD)
– With regard to subject of dissertation, some of projects are varied. For example, the final project would be on disabilities, so I do need writing about laws of disabilities and I don’t have any idea about. Thus, I need to contact with laws’ students to explain some critical points and where I can find that. This is just an example.
– Search for students in particular department would be easily.
- Travel Safety app
This idea is a travel safety app which alerts travellers about tourist black-spots and suggests detour routes to avoid going unsafe areas The information is contributed from the social network and other reliable media. The app may have the features as follows:
– It can suggest the most safe route, and give useful guidance/tips (ie. be careful to the pickpocket before taking the train in Paris)
– It will make use of social networks to connect travellers and its news
– Verification of taxis/ tour guides/ hotels/shops/restaurants/police office (prevent illegal operators, black taxis or being overcharged)
– Alert travel updates
– Detect user’s current GPS location and provide suitable emergency contact.
– Provide corresponding embassy details, credit card lost emergency call, insurance company details and claiming procedure
- Tool to improve existing group sites in academia
Based on the literature I have been reading it suggests that group study for university students in particular could greatly be improved by better management tools, as in most cases students prefer to use social media as a lack of any other competitive options. Specifically I think it should target existing student-based sites that aim to help project management, such as Medeley, and identify how they could be improved. Often this will be something along the lines of ‘it doesnt have an option to invite others to meetings’, or ‘for a project papers that the group are reading can’t easily be stored in the same place for all to have access to’. We can then propose key changes (or a new site entirely) that improves the weak areas, I.e. a group discussion area in blackboard, paper sharing, meeting planning, and personal deadlines all in the same space.
- Online Memorials
This idea is based upon the collection and presentation of personal information after someone has died. In many cases when someone dies their social networking profiles remain, but act as a place for friends and family to visit to remember them or leave comments. However, a majority of people actually have more than one profile on social media sites, and these aren’t linked up. For example if you gave a family member permission to change your account if you have died, they would not have the same permission on another social networking platform, so your profile on one site may be a cut-off memorial that not everyone can access. This idea is for a tool that scrapes information from each of these platforms (once a family or friend has permission to do so) and displays it on one profile/site, thus making it easier for everyone to see.
- Charity Crowdsourcing
My suggestion for our social network was something that combines crowdfunding and charity donation sites like JustGiving. This idea is that people can have a profile, show interest in charities/causes etc, create events for fundraisers that people can join in with or do at the same time elsewhere (for example, how Macmillan coffee morning takes place in lots of different places, run by lots of different people but all on the same day) – basically a platform for allowing this.
In conclusion we have picked idea number 3, the travel safety application, as it fits both the most criteria in the matrix, and each member was happy with the idea. Further research and a gantt chart mapping out the stages of our project will follow shortly.
This post represents that coherent structure and story are present in the portfolio which uses the entry and tags mechanism of the blog system. It tells the story of the project by explaining individual roles clearly, explaining why these were decided, and what outcome they will produce later on in the project.
In addition this post represents Innovation and Creativity by identifying a project idea in a novel and well-informed manner.
This post also represents that the group has chosen appropriate criteria for the comparison of ideas that directly link to the marking criteria. The analysis matrix criteria were chosen intelligently to produce a project of professional quality, leading to a successful product.
Written by Briony.
Introduction to Our Project
Posted by Briony Gray in Contextual Factors and Research, Innovation and Creativity (Idea) on 27/02/2015
Welcome to the blog of Group 4 in The Science of Online Social Networks!
As our introductory post we would like to explain how the first few weeks of the course have shaped and produced an intriguing project idea, and the future steps we plan to take to develop it further. We would also like to introduce our ‘company name’, based on the internet culture and lecture topic of the 90 – 9 – 1 percent rule (Hargettatai and Walejko, 2008):
We are ‘The One Percent’.
The purpose of this blog is to have a professional digital narrative of our project, which includes all of the choices and decisions that we have made, and the outcomes these have produced to our idea. Consequently this is a great resource for the members of the group who can access data and information quickly and easily. It is also a great tool for understanding our project – it allows the reader to follow the process of our project at each and every stage. Not only does this include all of our research, designs and engineering development: it also shows you the aspects that rarely cross over into fortfolios. For example, the problems that we faced throughout, a sense of the group dynamic and productivity, and the human discussions that were present in meetings throughout.
Over the previous few weeks we have been brainstorming thoughts, producing innovative ideas and addressing the existing weaknesses of social networking websites and App’s. These include the expectations vs reality of online privacy (Gilbert et al., 2011), a limited number of app features per project (Gavalas, 2011), and language barriers for a an increasingly global technological trend (Godwin-Jones, 2011). Our ideas covered a wide spectrum of potential projects: ranging from sites for improved group project management for university students, a site for arranging meetings using personal preferences of local areas, charity fundraising combined with crowdsourcing, to the scraping and storing of personal data across platforms to create an ‘online memorial’ for those who have deceased.
Despite many promising propositions, we have selected our final project idea which takes the form of an app designed for safer travel. This was done by creating an analysis matrix, which compared each idea to a number of criteria, which included the marking criteria of the project and what we personally felt the idea must incorporate in order to be innovative and successful. You can find the analysis matrix here. But what use is an idea without any in depth background research?
The next week was spent researching a number of aspects regarding the app, which included:
- Identifying a set list of features it was going to have based on a market evaluation of similar travel apps. The features we have selected, although a majority of which already exist, do not feature in one single app for easier use (Gavalas, 2011). Fully researching and designing how they may work and interact with one another is therefore extremely important for the production of an app which is original in the safety market by having multiple features.
- Our target audience, a vital consideration for much of the design-work. Both surrounding literature and market evaluation suggests that there is not an age group most likely to travel, and so our app must be user-friendly and easy to use for a wide range of ages. This represents vital market information from which we may learn a lot, and in turn tailor our own application for greater success. For example, through this we may identify a target audience for safety applications, and in response we may incorporate this audience into our own project projections.
- Economic and social factors that require consideration, for example should we charge money for our app? This may be vital market research as knowing the economic background of the market may dictate whether the public perceives charging to feel safer as morally viable or not. This would ensure that our pricing choice coincides with the trends in the market we aim to be a part of.
- Identifying potential datasets we could use for certain features, for example the use of governmental open data crime statistics to generate a ‘safest’ route for a traveller. This again represents vital background knowledge which will contribute to a smoother running application. In addition to this, it may further help determine the pricing of our app as open sets may keep set-up costs low, allowing us to reduce app cost should we feel this ties in with our market analysis.
This research has produced an initial framework for our app, and a themed name which is ‘TravelSafe’:
TravelSafe is a mobile application for anyone travelling anywhere in the world, whether at home or abroad. The application will consist of a safest route generator, which generates three safe routes from point to point, as well as a safety rating of areas within a given city which are both generated using open data and crime statistics. It will also provide travel information, such as bus and train times, locations and maps as well as weather information including severe weather updates and safety tips compiled from embassies, the World Health Organisation and social media and news feeds. Other functions will be the ability for the user to input information such as their travel insurance, flight details and important numbers, such as a lost credit card and incorporation of translation functionality. Finally, there will be a resource pack available to download which will provide a summary of the information and can be accessed offline to avoid roaming costs. The app features will be developed and researched later in the portfolio. You can skip to determining app feature research, expert opinions regarding features, and specific feature posts beginning with the Safest Route Generator onwards.
In the upcoming weeks we have a planned out a number of stages that will develop our project further, these take the form of:
- Designing interface and graphics of the app
- Demonstrating examples of code that are linked to certain features of the app
- Examples of the datasets that will be used to produce personalised information within the app
- Platform considerations
This post represents that coherent Structure and Story are present in the portfolio which uses the entry and tags mechanism of the blog system. It tells the story of the project by explaining individual roles clearly, explaining why these were decided, and what outcome they will produce later on in the project.
In addition this post represents Innovation and Creativity by demonstrating ideas that are original and beyond the expected thinking for this assignment – this is clear by the niche product design that is commercially viable in its target market.
This post also represents Contextual Considerations that take the form of background research, social and economic considerations, technological considerations, and most importantly using the research learnt to shape the development and outcome of the product.
This post lays the foundations for strong design and engineering steps later on in the project.
References
Gavalas, D., & Economou, D. (2011). Development platforms for mobile applications: Status and trends. Software, IEEE, 28(1), 77-86.
Gilbert, P., Chun, B. G., Cox, L. P., & Jung, J. (2011, June). Vision: automated security validation of mobile apps at app markets. In Proceedings of the second international workshop on Mobile cloud computing and services (pp. 21-26). ACM.
Godwin-Jones, R. (2011). Emerging technologies: Mobile apps for language learning. Language Learning & Technology, 15(2), 2-11.
Hargittai, E., & Walejko, G. (2008). The participation divide: content creation and sharing in the digital age 1. Information, Community and Society, 11(2), 239-256.
Meeting Summary 26/02/15
Posted by Taekyun Kim in Meeting Summary, Structure and Story on 26/02/2015
Meeting Summary 26/02/2015
During this meeting we addresses the ethical issues of the app’s pricing that were raised during the previous meeting. This meant considering whether it was morally right to charge people in order to feel safe. Each member conducted market analysis of similar applications, and came to the conclusion that a majority of app’s within the safety market do not charge, and therefore we should not either. This is an important consideration for our product, as it may determine how many users user our product over others.
Furthermore based on this market analysis the team have identified features of app’s on the market and the potential weaknesses that these have. During the meeting this was discussed in further detail, and the group came to the conclusion that our product should build upon the weaknesses of existing apps which would therefore create a niche market for our product. This has allowed the group to scope out a short-list of app features which were lacking or inconsistent in other existing app’s.
For the next meeting
The group decided that as the success criteria dictates that extensive testing will not be included in our project, we should decide the app features by acquiring expert opinions, group discussion, and literature reviews. Alongside this the group will research engineering choices in order to decide whether the app should be mobile based or web based, as choice of platform may dictate the usability of the app, the technologies involved to create it, and what different means of testing it may require in the future.
This post represents that coherent structure and story are present in the portfolio which uses the entry and tags mechanism of the blog system. It tells the story of the project by explaining individual roles clearly, explaining why these were decided, and what outcome they will produce later on in the project.
Minutes by Briony Gray
Meeting Summary 23/02/15
Posted by Taekyun Kim in Meeting Summary, Structure and Story on 23/02/2015
Summary of first meeting 23/02/15
This meeting was the first in which all members of the group had been present. As a result, much of the discussion was based around discussing some initial project ideas, reading through the marking criteria, and deliberating which group names would convey the message we wanted to put across throughout our portfolio.
Deciding on a group name
The group decided that the name should be based upon several lectures that the group had received during the course of module, thus tying the group in strongly with the themes discussed and presented which would ultimately shape the course of our project. Each member suggested several names, and a group vote was taken to ascertain which was the most appropriate. Categories which dictated the appropriateness of a group name included: whether the name was broad and general enough to cover any idea that we later chose for a product, whether the name had positive connotations, whether the name was easily memorable or not, whether the name was applicable to all members of the group, and whether the name related to the subject material from the module lectures.
Suggestions for the name included Deliberate, Spiel, Prototype, Theory of Trust and The One Percent. The group came to the conclusion that the name The One Percent fit the majority of the categories previously mentioned, and this was decided as the group name.
Deciding on a group project
In the same manner as choosing a group name, a group project idea was decided by the democratic voting of all of the group members. Each member personally researched and presented an idea to the rest of the group, with some initial background research. An analysis matrix was drawn up which pitched the ideas against the marking criteria, and a score for each idea was tallied at the end. The idea which fit the most criteria, and which all members of the group were happy with, was a travel safety app put forward by Kaley.
For the next meeting
In order to proceed with the project development each member will read around the project area and find any applications that offer one or two similar aspects to our proposal. A post regarding similar applications on the market will be produced to illustrate common trends in the market area, and to highlight potential weaknesses that our app may seek to rectify.
Each member will also consider what aspects would contribute to making this app, for example what are the easiest types of map to read, what safety concerns people are the most worried about, what datasets can be used in the app etc. These will be vital in the shaping and success of the design and engineering of the project.
Finally each member should consider whether we think the app should generate a profit or whether it should be free (ethical issues), based on the market research we have conducted. This should fit in with the target audience and pricing range highlighted to ensure that our app will be successful.
During the next meeting
During the next meeting the group will write the 200 word abstract that summarises our project ideas and the considerations we have thought about in selecting it. This will include the background research we have collected throughout the week stated above.
This post represents that coherent structure and story are present in the portfolio which uses the entry and tags mechanism of the blog system. It tells the story of the project by explaining individual roles clearly, explaining why these were decided, and what outcome they will produce later on in the project.
Minutes by Briony Gray