All posts by Deleted User

Special user account.

SparkApp !

Spark Logo transparent

Concept Description :

The aim of SomeJam was to use the means of digital technology to build up concrete ways enhancing the wellbeing of youth. We created a web application, named Sparkapp, which would generate a random activity for the user to try. SparkApp helps people to take part in surprise events. Users can customize event notifications on the basis of price range, duration, adrenaline level, physical activity level, time window, do-good (charity) activities etc.

The app was mainly designed for people between 12 to 65 years of age. We were aiming to focus on the Greater Helsinki area in the first development stage

( and got 63 survey responses from our friends. Result of our survey was as follows

  • 74% claim they like trying out new things
  • 92% think new experiences are important
  • Still 71% say, they could improve at trying new things more often

As we can see from results, the majority claimed that with a little nudge, they would get more active and do new things. So here we come in to provide that nudge !

We believe SparkApp can benefit its users in various ways :

  • As it is said an empty mind is devil’s workshop, SparkApp helps it users by engaging them in constructive hobbies.
  • Learn new things.
  • Overcome social phobia
  • Become creative and positive
  • With this app, it is possible to take part in charitable activities and hence enjoy the fun for helping others

Apart from bunch of benefits discussed above, SparkApp provides special values by opening up new horizons of random constructive activities which user may not have tried before. This may also help users to realize their hidden talents which they otherwise thought was not meant for them.



Prototyping :

12 3






















We have uploaded our working paper prototype at

After we clarified the main functions and features that SparkApp would provide, we built a paper prototype which included the user interface according to each function and feature which could be found at paper prototype link above.

The paper prototype helped us to visualize the application and makes it easier to deliver the idea to developers as well as audiences. When designing the paper prototype, we found that it would be more convenient for the user to customize event notifications by using double-end sliders for scales, such as “adrenaline level” (from fully relaxed to Indiana Jones) and “physical activity level” (from easy going to athletic hardcore).

We also made a video in which the main concept and the process of the application was explained. Video also contains story of Steve, who was bored by his daily life and wanted to try something new and how SparkApp could help him in overcoming his boredom and engage him in something constructive . Please check out our video 

Technical description:

    • Development tools used:
    • Stage of implementation:
      • Lots of back-end logic implemented. Front end HTML/CSS was also produced and integrated with the back end, but it was not good enough for submission. We integrated the system with Facebook, making login with FaceBook possible, and collected local events’ metadata from external sources.
    • Are you satisfied with the architectural choices your group made for the software? If yes, why? If no, what would you have done differently
      • Yes. Our Architecture remained at such a simple level since only mostly back-end logic was focused on. Everyone agreed on the development process in a beautiful harmony.
    • Repository

Team members :






    • Axel Wallin (programmer, innovator, designer)
    • Evan Miller (programmer)
    • Mikko Rinta-Homi (programmer)
    • Annette Mili Kemppi (programmer, innovator, designer)
    • Shubham Kapoor (programmer)
    • Yan He (programmer)
    • Evgeny Kamardin (visual artist)
    • Batman (emotional support)

During the weekend we spent in Somejam2016, we were able to collaborate, gain unique development experience and Win an electrifying hackathon environment. Our project idea was well praised by judges but lack of front end developer and technical practicalities (For ex. We could only access Facebook users personal data after a week developer has registered himself to FB)  limited our practical practical demonstrations. If given new opportunities to showcase our project we would try to overcome these limitations and also include a nice front end developer in our team

Antti-Social Network

Team members:

  • Martin Radev – Programmer
  • Nidia Obscura – Innovator/Analyst
  • Fiyinfoluwa  Soyoye – Programmer
  • Angel Gallegos – Programmer

Screenshot from 2016-03-29 12:55:13

Concept description:

We came up with a solution to solve the problem of youth distraction by specific social media sites. We looked at statistics on the usage of social media by young adults and  we discovered that people under the age of 30 use social media for up to 4 hours a day and teenagers use these media for an astounding 9 hours a day.

While this was disturbing enough, we realized that it wasn’t the main problem. The main problem was that 13-year-olds can check Facebook alone up to 100 times in a single day. This implied that youth check social media so often that they never really focus on a specific task such as studying or even having fun with their friends.

Our target was the youth who were getting so easily distracted and unfocused because of such destructive habits, including ourselves. Actually, the idea came up after talking about our own personal problems with the nowadays technology.

We aimed to solve the problem by creating an web app that could easily be installed on a web browser and track the usage of the most commonly abused social media. From our own personal experience, we knew that most people don’t realize that they use Facebook or Twitter as much as they do.

The special value of the app was that we didn’t try to limit people’s access and usage of social media. Instead, we provided them with concise and clear data on their personal usages. We believe that limiting people will only lead to them trying to beat our system and ultimately uninstalling the app. By simply providing them with helpful knowledge, they can take this knowledge and change their own habits, improve their lives and have more meaningful interactions with the world.


PrototypingScreenshot from 2016-03-29 12:55:45

Our prototype was a complete chrome app paired with a functioning server and a website that displayed personal usage data.

When designing our prototype, we came up with a use case called Antti. Antti is a 19-year-old boy who was having trouble getting good grades in his first year of university because he could not focus.

He would spend hours studying but realize that it was all a waste. By using our app, he quickly noticed that when studying, he checked Facebook every 6 minutes. With that realization, he was able to train himself to concentrate and ultimately do better at university.

Below, we have included pictures of the website that we designed and the graphs displaying real usage data.

Website homepage:

Screenshot from 2016-03-29 12:45:27

User statistics example:

Screenshot from 2016-03-29 12:47:15

Technical description:

In our implementation we decided to split the work into three main parts: Creating a browser extension for logging the user behaviour, a server that collects all users data for further processing and a web interface that shows the user their user statistics and habits.

The browser extension logs the web domains visited by the user, device or browser used, and the timestamp of the time he started and finished using it. At this point of the implementation, the extension was only implemented for Firefox but planned to be implemented also in Chrome browser and in the future even on Android so the app covers the main devices used by young people.

On the server side, we created a dummy server in heroku that received the logs extracted by the extension and store them into a database. The server was available to any user at the end of the hackathon but it was missing a login implementation, therefore, it only was able to create statistics for one user.

Once we collected and created some dummy readings from the user, we process them and show them into a bar and pie charts for the user. The user visits his main page where the user is supposed to select a timeframe he/she is interested to know about. For instance, it can be a day, a week or a month. Once selected, the server collects the related registries for the timeframe and create the charts. The bar chart shows the main domain activities during the timeframe, for instance, in a day it shows the domains where the users spend their time the most during every two hours. The pie chart shows the domains where the user spent the most in the given timeframe.
On the data processing, we only were able to implement simple time analysis but it was expected to include more complex analysis. Such analysis includes the times you are using the most some domains, the mean intervals between each visit, for how long you visit them, etc. Once included, it would allow the user to infer why such behaviours and why during those times. Also, it would allow us to give some feedback if the user is expecting to get rid of some bad habits. For instance, if he wants to reduce the time he spend in “Facebook”, it would be possible to show him/her the progress on this task.

Screenshot from 2016-03-29 12:56:40

The tools used were:

  • Heroku
  • Flask
  • Python
  • Javascript
  • ChartJS

The implementation we tried to use tools that we were familiar with but we did not know in detail. That is, our purpose was to learn something at the same time we were creating our solution. For example, the initial plans include using libraries from python we know but, we did not know how to use it on a web-server. We decided to use flask framework since we have heard about it but not use it in detail. We also decided to use Heroku since we needed to have available the server from any device and deploying our implementation to Heroku allowed us to do it. At the same time, we initially expected to create the extension for Chrome but since it seemed easier to do it in Firefox, we went that way.

Technically, the most important decisions were defining the scope of the project due to time limitations. For instance, we expected to implement it in a web-browser and android but, we decided to have it working at least on the web browser before moving on to a mobile device. Also, we started creating a login page for allowing different users to have their statistics but, spending much time on it would be useless since it was only a prototype.

Volu venture

Näyttökuva 2015-03-17 kello 11.09.51

Introduction of the team members

Anne, youth work professional

Tiina, artist

Jarkko Lagus, programmer

Lari Saukkonen, programmer

Jyri Saukkonen, programmer

Concept introduction

Idea was to rebrand volunteering work (in Finland) and to make an app that connects volunteers and organisations in a meaningful way. We decided to make platform to aggregate the supply and demand of voluntary work and change the overall attitude about voluntary work in finnish culture.

Screen Shot 2015-03-15 at 15.38.41


3 important user stories


Lifestyle: skater, lives with parents, doesn’t care so much about school, dreams making it in the skating business.

Attitude: free soul, doesn’t know yet what he wants to do in life, lives in the moment

Gain from voluventure: explore different kind of work possibilities, likes to work with children and other teens

Could have potential in youth work in the future


Lifestyle: vegeterian, into arts, has strong opinions issues in society etc. goes to kallio school of arts, into acting etc.

Attitude: determinate young person with lots of optimistic dreams

Gain from voluventure: can have impact on society through own actions, likes animals etc. so could help in rescuing animals and so on..


Lifestyle: parkour instructor and a professional stuntman, urban person who likes to participate in all kinds of charity events and happenings around the town

Attitude: Fearless opportunist who likes to try out new ideas.

Gain from voluventure: Can make, organize and participate in volunteer events.

What did we learn about the service design process?

We learned how important it is for a successful service design process to include the professionals from the specific area of expertise to be able to understand the underlying problem. When designing a platform for young people it is not enough to have the information and means how to technically produce the generic product but how to make it adapt the specific field of business.

What became your solution architecture?

MEAN-stack: MongoDB, Express, AngularJS, Node.js


MEAN-stack and Heroku were already familiar with us so that was a natural solution for our project’s starting point. We didn’t have any major setbacks using the stack and we could operate it efficiently. Overall we recommend the MEAN-stack and Heroku for anyone already familiar with the technologies but if starting to learn them in a hackathon-like fast pace environment is not advised because they take some time to master.

What development tools did you use?

Hipster logo generator Amazing professional tool for all your graphical needs.( Forget about photoshop and use this instead.

GIMP, photo editor

Webstorm, IDE

Sublime text, text editor

What advice would you give for a person planning to participate SomeJam 2016?

In our opinion SomeJam is more about innovation and prototyping than just hardcore coding in a dark room without communication. We think that for success it is essential for the group to have an open communication between software developers and other professionals.

Almost 50 Shades of Your City


Want to hang out but don’t know your city? Let us introduce you to “Almost 50 Shades of Your City”!

During the weekend we were lucky enough to participate in SomeJam 2015. An event where you are among great minds. We had 48 hours to implement an idea which should help people, specially the youth. Beside all the intensity to implement something useful in 48 hours we also had much fun and great food. It all started when the three of us couldn’t find any group in line with our interests which lead to forming a team ourselves.  Since we were all computer scientists, Martin Radev, Farbod Faghihi and Ankit Kariryaa,  we wanted to use advanced knowledge in computer science and not only a normal service.  Since we were interested in Location-based Services and Machine Learning concepts we came up with “Almost 50 Shades of Your City”.


There are times that one is lonely and cannot find their desired places to go and like minded groups and related events are not found easily. As a new student you want to know more about different regions in the city in order to find desired places to hang out or as a person who is moving to the city because of his or her new job you want to know which regions contain events in line with your interests. As an agency working for improving the city, you want to know which parts of the city are deprived of cultural, technological or social event, so that we can work on these areas and making such events available to a large population. So we decided to get all the information from the services that organizes event such as Eventbrite and Meetup to make people more familiar with their city. The idea was to find out that what kind of events are held at which regions of the city. We have an intelligent user interface that provide the user with different levels of abstraction relative to the area that the user is viewing in the Google Maps. So as the user zoom in or zoom out we would classify different regions on the map into corresponding type of event that is happening there. For this goal we use clustering methods such as K-Nearest-Neighbors.

So here you can see three different figures, each with a different level of detail. The first one shows the Europe which we can see that the dominant event is business. In the next figure we went further and you can see a view of Berlin which is interesting because we can see the we have three separate areas with different kind of events. It shows that in the south west we have technical events while in the center the dominant type of event is business and finally in the south east music events dominates the events in that area. You can go even further, in the third figure you can see one of the Berlin neighborhoods with lower level of abstraction.






We divided the challenge into 3 sub tasks, Martin was responsible for gathering data about events around the world, Ankit was responsible for the clustering of the data  and Farbod took up the job of visualizing the data. We went through different event hosting sites and decided to use as our first source of events and then expand further if time would allow. For clustering the data, we decided to use,  K-Nearest-Neighbors clustering algorithm, here class labels are determined by a majority vote in its K-Nearest-Neighbors. In this way we were able to determine the most popular event in a certain area. For visualization, Google Maps API was selected and marker were used to display the finding of the clustering method.

We implemented the back-end i.e. the web scraping technique and clustering in Java. The front-end was implemented in JavaScript. We used for source code management. We are happy with our choices as it worked out very well in the end (Yes we were one of the winners! 😀 ). We really enjoyed participating this event and would like to greatly thank everyone responsible in organizing the event.

A Life-lasting Experience: SomeJam 2014

Experiences from 2014 hackathon


A Great Weekend

The weekend started on Thursday (13th March 2014) by a series of talks by some young entrepreneurs at the Linus Torvalds auditorium (Exactum building, Kumpula campus of University of Helsinki). We learnt some key facts and points about lean startups and also characteristics and goals of prototypes.

The Joy Began

Next day (Friday), SomeJam hackathon officially began at the Happi Youth Center, with some initial speeches about the fundamentals and practicalities. Then we teamed up, and the organizers started to ignite the creativity rocket of participants by showing some objects and asking us to guess what it is, and how it can be used. Then we started to think about and come up with some ideas to solve the loneliness problem of youth. After some minutes of brainstorming in groups, all groups presented their ideas.

Finally, we had a freestyle opportunity to come up with some novel ideas and present them. First, I came up with a great novel idea (related to youth) and presented it, but since we only had 48 hours to build the prototype, I thought more time is needed to build a working prototype of my idea. Then I noticed another great idea proposed by Maninder Singh, and I joined the team. Then Lei Wang and another anonymous teammate joined our team.

The idea was to provide a service to lonely people and those who are new in a city, especially youth, to find and join events based on their interests, make new friends, and have fun. After joining the team, we started to discuss about the details, and we came to an agreement for the programming language and technologies we wanted to use. We chose the Grail framework because we all knew Java, and Grails was a great framework for Java programmers, because it is relatively easy to learn, developers can develop their solution quickly using scaffolding facilities, and it’s almost hassle-free. I already knew Spring framework and Maven, and it helped me to learn the new framework rapidly.

Welcome to The Dragon Team!


Friday night, we started to brainstorm more and then collaborate to draw our initial model on a big piece of paper. We managed to come up with a model that satisfied our initial requirements. It’s worth to mention that this model might not be complete in the first iteration and can be improved over iteration (like in lean and agile processes), but we tried to consider and model the fundamental building blocks accurately.

We created a paper prototype demonstrating the features and functionality of our intended service. We also created a central repository on Github to facilitate our teamwork for implementing the service initially as a web-based service. Since the IntellijIDEA IDE offers out of the box support (code completion, server management, etc.) for Grails, we used that IDE for our project. After working till 4 AM on the backend and a part of frondend, we left Happi to have some rest at home.


On Saturday, we get together again at midday because we had to pitch and defend our idea and project in a tough jury meeting.


Fortunately, we managed to defend our idea, and of course we got some precious suggestion and advises that we considered for improving our service. After the meeting, we continued to work till late night.

Time to Wrap Up


On Sunday, we got prepared to present our software product (working prototype), and I believe we did it pretty good. You can watch the footage on YouTube.

Eventually, the amazing weekend came to an end, but the inspiration did not. I learnt a lot in the first SomeJam.


The Guru!

I believe the following advices may come in handy:

1. Don’t miss this kind of events! When I got the email regarding this course, I thought I’m not going to participate because I was busy, but it turned out to be one of the best courses I have ever had.

2. It’s great to have some novel ideas to solve our problems, but since these kind of hackathons are quite short, bear this in mind that you must be able to implement a prototype in a short time. So don’t consider ideas that need a week or two to build even a prototype.

3. Although prototypes are there to quickly show the concept, but they should impress/persuade the investors/partners/business angles for investing in your idea. So take this into account before going to the pitching meeting.

4. If you didn’t face a good reaction/feedback from the potential investors, don’t be frustrated, the objective of a prototype is to assess if the idea is worth to put more effort in order to implement it. Instead, think about other novel ideas.

5. You can predict the reaction/feedback of your potential investor to some extent. Try to ask yourself:

– How are we going to have our first user/customer?

– How can we extend our user base, and how are we going to keep them motivated such that they continue to use our service?

– What value(s) does our service offer to users?

-Can we imagine of a Persona for our users?

– Is there any similar service out there? If yes, how does our service differ from those similar ones?

– Does the project need significant investment to set up? What about the maintenance costs?

– Can we generate a revenue stream?

I learnt all of these in this intensive event. Thus, in the end, I would like to express my gratitude to dear Hanna Mäenpää, dear Emilia Hjelm, dear Marcus Lundqvist, other organizers, and my teammates for creating this great experience.

SomeJam Project: Happy Hangup

HappyHangup is a platform which provide solution to the lonely people in a country. For a new person in a country or lonely people in country, its hard to find friends. We provide group activities to involve people with others. Its going to be unique platform where youth organization can generate innovative solutions and execute those innovative ideas by involving youth of the country. It provide a unique interface where youth can interact with each other and find new friends. It a platform to have a fun whiling hanging and being a part of learning environment.

This idea is come up by our group member Singh Maninder.  The following paper is his initial idea. After Maninder‘s presentation,  Javad BohJannis Seemann and I joined the group.

The following chart is the Singh Maninder‘s original idea.


Then, we start to figure out how to go specific on this idea together. The following figure is our discussion result about what specific feature we need to realize.



The final presentation of our project on Sunday is

Github repository:

Open source license: MIT

We use the grails for web development framework and gsp for front end design.

The following pictures is our website ‘s snapshots.

Main page of our work.



Interests list of users



coming activities list



involved Company list



Details of Activity




We have a really happy experience together to complete the whole project, and we also want to get comment from users.

Let’s Do It project group

It was quite interesting to attend SomeJam and to innovate things as a practical developer. The working environment was quite enjoyable and comfortable, with a lot of space.  Staffs were quite considerate and the food was nice.

Our schedule for the SomeJam -event was generally like this, on Friday evening we first had an introduction to the event and self-introduction of everyone. Then we were randomly divided into groups and had games to inspire us to solve problems. On Saturday afternoon we had our first pitch with board members and got feedback to improve our future work. Then on Sunday afternoon, we did the final pitch among all the other teams.

In terms of team work,  we all thought that our team worked really well together. All of us were developers so we were instantly on the same page in terms of what was doable in the scope of 48 hours . We also had similar ideas about how we should start implementing the project. After the initial planning phase we decided to divide into two groups, so that we could have a nice mock-up done for Saturday’s board meeting but also immediately start work on the Rails prototype.

It was quite useful and interesting to pitch, as majority of our group members didn’t have real pitching experience yet. We gained valuable experience on how to form a good idea and try to sell it to business investors. Working as group and solving a problem together in real life was very interesting. We all learned a lot not and hoped to enjoy the next SomeJam event.

SomeJam 2014 – HateSpeech detector

Software development team members

Martin Radev

Describe your software concept shortyly:

To develop a tool that recognises hate speech based on a cumulative database of hate speech cases. The database will contain cases of different kinds of hate speech (e.g. hatred based on ethnic background, sexual orientation or gender identity, religion or disability). The more the programme knows, the better it recognises new cases.


What became your solution architecture?

Java for the socket server. PHP for connection between http server and socket server. JavaScript for the connection between the website and the http server. MySQL for storing the training examples. For recognizing the topic of the text it was used a text-mining library and most accurately the LSA algorithm.

Are you satisfied with the architectural choices your group made for the software?

No, because there were issues getting jsp working locally. We had to go with the java app to listen on a socket and receive the data via the latter. Then, we had to send the post requests from the website to a php script and then send the data to the main program via a socket connection. The initial idea was to make it as a standard webapp and deploy it to heroku.

Team Getogether



Just moved to a new city and don’t know anybody? Or are you feeling lonely in company cause none of your friends really get your passion for My Little Ponies? No matter what your interest are, there are people with the same passion out there. FIHMY will help you to find these new friends! The web service is super easy to use, also with mobile devices. With just a few clics you are able to mark your interests and see how many registered users are interested about the same things in your area. Then you can jump in the events organized by other users around an interest. Or you can set a date and invite eg. other local My Little Pony fans to meet you. When you meet face-to-face, you will all know that you have something to babble, rally or gossip about. And that, dear folks, could be a start of a beautiful friendship.

Link to the presentation:


Back-end: NodeJs + ExpressJs + MongoDB

Font-end: AngularJs

The back-end solution worked well, NodeJs allowing for quick and dirty solutions to be made which sped up the production.

The front-end was a learning process… The only experienced AngularJs developer in the team had to leave and the two others had to wrangle with it the rest of the project. But it worked quite well in the end. AngularJs is like magic, with its automatic dependecy injections and two-way data binding. What made the AngularJs development process easier was the desicion to use a Yeoman generator for the project. It allowed us to ignore many aspects of how AngularJs works, and concentrate on the essentials.


  • Keep it Simple, Stupid (KISS). Kill features, kill some more features and then cut the features in half.
  • Do not think about code quality. Just hack it together and get things done. It doesn’t matter if the server crashes when the client gives the wrong data, as long as it works during the demo.