The purpose of this post is to explain the privacy issues that are considered in designing LeapIn.it system. The following sections demonstrate the privacy related issues from five perspectives which are the personal information, information security, visibility of profile pages, privacy policy and cookie policy. Personal information In LeapIn.it, no personally identifiable information is collected from the users except their… Read more →
LeapIn.it will allow people to “leap in” to rooms based around niche interests simply by scanning barcodes (or QR-codes) that may be found on relevant material (such as books and posters). However, it is reasonable to expect that one subject may have multiple barcodes. For example, the DVD and Bluray releases of the film Inception may have different barcodes. In this case,… Read more →
LeapIn.it has been designed as a mobile app. This post will give some consideration into how the app will be accessed. As we discussed previously, LeapIn.it will be developed using HTML, CSS and JavaScript. This will then be packaged as a native application for iPhone and Android using Apache Cordova. Thus, there will be two forms for LeapIn.it: A website… Read more →
This post will consider how people share content on social networks. This will provide the background necessarily for designing structures to enable content sharing in our social network. A study that was conducted to observe the way in which people share knowledge and participate in one of the largest forums, Yahoo Answers (YA), is highly relevant to our project; what… Read more →
This post will detail the basic components and architecture of the planned system. Web as a platform LeapIn.it is aimed primarily at mobile devices. A major issue with developing for mobiles is the proliferation of mobile devices – to reach 90% of active mobile users, more that 330 devices must be considered. The differences between these devices include screen-size, inputs, programming language… Read more →
The class diagram below illustrates the data structures which will be used on the client and server. These models will be made available over REST, which is discussed here. The Enhanced Entity Relationship diagram below shows the schema of the database. The tables and relationships between the tables are illustrated.
This post will illustrate two user scenarios of LeapIn.it. The first scenario illustrates how a new user can register to Leap in it! social network, customizes his/her own avatar and choosing which rooms that match his/her interest from the public room. The second scenario shows how the user is taken from the real world to… Read more →
In designing our social network, we will consider how we intend to facilitate communication between individuals. One important consideration is: who will be communicating to who? This post will identify who people will interact with and why. One way we can study this is by considering the models of homophily and heterophily. Rogers and Bhowmik (1958) discuss the concepts of… Read more →
The name of our social network is LeapIn.it. There are several motivations behind this name: It describes our social network. Our social network allows people to go to virtual rooms to discuss real life things. Using a smartphone camera, a person can scan something they’re interested and “leap in it” to interact with others about it. It’s a short and… Read more →
During our development of the LeapIn.it prototype, we have used a number of design patterns, libraries and API’s. This post will give an overview of the most crucial of these. Server The server is responsible for creating a REST interface for database access. As mentioned in our post on architecture, we have chosen to use RedBeanPHP to communicate with the… Read more →
