Harness the potential from the generation of tomorrow
Inforum is a promotional content marketplace that aims to market to hard-to-reach millenials/Gen-Z demographics by utilizing network effects on social media platforms such as Facebook, Twitter, and Instagram. On our platform, our users can share offers to their social media for personal monetary benefit, and the banks are able to use our users to promote their offerings to our users’ network via a trusted source, creating a win-win situation for both parties.
| Create campaigns | Browse campaigns | Share campaigns | Track campaigns |
|---|---|---|---|
 |
 |
 |
 |
- Business Pitch
- Inforum App
- Architecture Diagram
- Demo
- Product & Research
- Tech Stack
- Decision Logs
- Team
| The problem | Market analysis | Financials | Business plan |
|---|---|---|---|
 |
 |
 |
 |
- Learn more about our pitch, market analysis, competitive landscape, customer value propositions, and financial modeling at business plan.
Download our app locally at Inforum App
inforum_without_audio.mp4
- Learn more at Demo
| Product roadmap | Product decisions | User research/interviews |
|---|---|---|
 |
 |
 |
- Learn more about our entire design process, including our product roadmap, use cases, user research, and UI/UX at Product & Research.
Languages:
Javascript, SQL
Front End:
React.js, Redux (State management), Facebook Graph API
Back End:
Express.js, Node.js
Data Storage:
PostgreSQL (ORM: Sequelize), Redis
Testing:
Jest,
Exceptions Logging:
Sentry
Deployment/CI:
Heroku, Github Actions
Other Tools:
Figma, Postman, Slack
Design and UI:
From a design perspective, we have decided to prototype our entire UI and high-level architecture using Figma, which is intuitive to use and requires not much technical background. Figma also has group sharing functionalities and will thus allow our CSC454 colleagues to participate in the whole design process.
React, Redux, Express, Node, ESLint, Jest:
We have decided to use this popular stack in web development, because it helps us build a web application from front-end to back-end only using Javascript.
We also chose to use Jest, because both Jest and React are developed and supported by Facebook and will have better compatibility with one another.
Data Storage (PostgreSQL/Redis):
We initially thought of using the popular MERN stack but eventually realized that a relational database (postgreSQL) would be more appropriate for our use case compared to a NoSQL database (MongoDB). As our application requires many different tables (user, mission, post, etc.), relational database will help us enforce data integrity and join tables more easily.
We have also decided to add Redis to our tech stack as an in-memory key-value store for caching purposes, so we can retrieve data such as user-related data in a timely manner.
Facebook Graph API:
We will use Facebook's Graph API, which will provide us with key statistics for each user's post (including the # of likes/comments). This will be used to calculate the points each user will get in our reward system.
Monitoring (Sentry):
We have decided to use Sentry for error tracking and performance monitoring for both the front-end and back-end of our web application.
Communication:
We have decided to use Slack as the primary source of all communication, including video calls and the recording of meeting notes. This is because we want to promote a professional work environment where the slack channel will only be used for work-related discussions.
CI/CD/Version Control:
We have decided to use Github as our version control platform, because everyone on the team has professional experiences working with it and that it is free of charge for teams of any size unlike alternatives such as Azure DevOps.
We have decided to use Github Actions to set up our continuous integration workflow, including building, testing and deployment. This is because GitHub is arealdy used extensively for the entire application development process (commits, issues, branches, etc.).
We decided to use Heroku as our container-based cloud platform to deploy and manage our MVP mainly because it is free of charge and Heroku integrates with Github very well, so we could leverage that for continuous deployments.
Learn more about our team, including leader selection, team principles, and our values at team.