..

portfolio

This portfolio showcases a collection of my previous projects, each accompanied by their unique stories and insights.

+-+-+-+-+-+-+-+-

This is Moeen Mohamadi, 23. A generalist! Have been working on variety of projects as a front-end dev, back-end dev, ui/ux designer, server admin, product manager, hr coordinator, design thinker, product ideator, … . You can call me “a maker”
Email Twitter +-+-+-+-+-+-+-+-

Table of contents

NinjaGo (Author)

What is it?

NinjaGo was a free, open-source website designed for anyone interested in learning the Go programming language.

How it started?

Go has always been my favorite programming language because of its power, speed, scalability, clean syntax, and versatility (especially for server-side web development). I started NinjaGo for two main reasons:

  1. To deepen my own understanding of Go—teaching is one of the best ways to learn.
  2. To create a straightforward, step-by-step guide for beginners, making it easier for more people to discover and learn this amazing language.

The process of creation

  1. Built a solid understanding of the Go programming language.
  2. Explored popular Go resources—books, articles, websites, and videos—to identify what works best for beginners and find a balance between covering fundamentals, providing enough detail, and keeping it concise.
  3. Organized related concepts into separate, focused classes.
  4. Started writing the learning materials step by step.
  5. Shared the website online.

How it was working?

I structured the content as a series of classes. Each class focused on minimal theory and emphasized hands-on coding examples to keep things practical and engaging. ninjago1
+-+-+-+-+-+-+-+-

ninjago2

How it ended?

Over time, I realized there were already plenty of great learning resources for Go online. Additionally, the time I was investing in maintaining NinjaGo wasn’t yielding the impact I had hoped for. So, I decided to close the website and shift my focus to other projects.

What I learned from this experience?

  1. Teaching a language is a great way to solidify your knowledge, but diving into hands-on projects is often a faster and more effective way to become an expert.
  2. The impact of NinjaGo was limited due to low readership—there were already many other resources available, and my time could have been better spent elsewhere.
  3. Whether contributing to open-source or starting a personal project, it’s important to ask: Am I creating meaningful value for others and myself?

+-+-+-+-+-+-+-+-

Pay.page (Founder, Ideator)

What is it?

Pay.page was designed to be an all-in-one platform for managing payment methods like CashApp, PayPal, bank transfers, crypto, and more. Users could connect their accounts or manually add payment methods, then share a single link with others to receive payments.

How it started?

I noticed a gap for small businesses and freelancers who needed a simple way to list all their payment methods in one place. The goal was to create something like Linktree but focused specifically on payments, making it easy to share a professional and customizable payment link with clients or customers.

The process of creation

  1. I noticed that freelancers, small businesses, and individuals were often sharing their payment methods manually, which was inconvenient for both clients and sellers. This inspired me to create a solution.
  2. I researched similar platforms and found that a modular structure, like Linktree, was familiar and user-friendly.
  3. Designed prototypes using Figma to visualize the concept.
  4. Attended startup events in person, introducing the idea to many people and showcasing the designs.
  5. Collected feedback and realized that while people liked the concept, they weren’t interested in paying for the service.
  6. Decided to conclude the project based on these insights

How it was working?

Users would claim a username and add their payment methods, either by connecting accounts or entering the details manually. paypage

How it ended?

  1. I realized that having multiple payment methods in one place wasn’t a problem for most individuals or businesses. While the idea had potential for a niche audience, it didn’t have the broad appeal needed to attract a large user base.
  2. Moreover, potential users find it easier and more secure to handle the payment method themselves.

What I learned from this experience?

  1. Not spending too much on a premium domain name at the beginning!
  2. People aren’t willing to pay just to list their payment methods in one place. XD

+-+-+-+-+-+-+-+-

NFT Marketplace (Product Manager)

What is it?

An NFT (Digital Art) Marketplace built on the BNB Chain, where users could create and trade NFTs.

How it started?

During the early days of the BNB Chain, its low transaction fees attracted a growing number of users, creating significant hype in the crypto space. There was a high demand for an NFT marketplace on BNB Chain to compete with Ethereum’s leading NFT platform, OpenSea. Recognizing this opportunity—and seeing even well-funded teams like PancakeSwap (the top decentralized exchange on BNB Chain) working on similar ideas—I decided to build an NFT marketplace to fill this gap.

The process of creation

  1. Recognized the demand and started building to meet the expectations of the emerging BNB Chain community.
  2. Assembled a team by speaking with over 50 professionals across various domains, including front-end and back-end development, business advising, smart contract auditing, blockchain specialists, and crypto contributors. I shared my vision, evaluated their expertise, ensured they could allocate time to the project, and gave them small tasks to test their skills. Those who met expectations joined as contractors.
  3. Created an outline for the project, developed a comprehensive plan, and managed all aspects—from user interface and experience to front-end, back-end, and smart contracts. I oversaw meetings, payroll, and team coordination while actively contributing to each department as both a manager and a team member.
  4. After three months of intense work, with a team of around five developers, we successfully launched a fully functional NFT marketplace on the BNB Chain.
  5. Fun fact: I woke up at 6 a.m. every day during the project to stay on top of everything!

How it was working?

nft

How it ended?

  1. We focused entirely on building a high-quality NFT marketplace—and we achieved that! However, I overlooked the importance of a sustainable business plan for growth beyond the initial launch. Our plan was solid up to the creation stage, but it lacked a clear path for scaling and maintaining momentum.
  2. The team’s incentives were tied to completing the project rather than driving its growth, which made continuing less motivating—especially after the intense effort left us feeling burned out. Meanwhile, new competitors entered the market, and the hype around the BNB Chain faded. The NFT space largely remained centered around Ethereum, making it difficult to compete.

What I learned from this experience?

  1. Create a sustainable business plan that ensures growth and revenue beyond the initial launch.
  2. Building a long-term business is far more valuable than chasing a one-time success.
  3. Prioritize maintaining strong connections with great people—these relationships are worth more than short-term financial gains. Investing in people and networks pays off in the long run.

+-+-+-+-+-+-+-+-

Morph (Ideator, designer)

What is it?

Morph was an algorithmic rebase stablecoin protocol inspired by the Ampleforth protocol, with some modifications. It aimed to stabilize its price at $1 automatically by adjusting the total supply (minting and burning tokens as needed).

How it started?

My friend and I noticed the success of the Ampleforth protocol on Ethereum. At the same time, we saw the lack of such a protocol on other blockchains with lower transaction costs and growing ecosystems, which could attract new users and capital. We saw Morph as a potential solution for these chains, with opportunities to generate revenue through earning a percentage of transaction fees or allocating team tokens.

The process of creation

  1. Identified the gap for reliable algorithmic rebase stablecoins on non-Ethereum chains and drew inspiration from Ampleforth’s success.
  2. Designed the dashboard interface using Figma.
  3. Worked on forking and modifying Ampleforth’s smart contracts to suit our protocol.
  4. Deployed the smart contracts on testnets and tested their functionality in various market fluctuation scenarios.
  5. My friend developed the backend for the website, adding features like real-time graphs, Web3 wallet integration, and connecting the smart contracts to the website.

How it was working?

morph1

How it ended?

Despite completing the technical side, we faced a major challenge: the lack of a community and sufficient capital. For an algorithmic stablecoin to function effectively, we needed significant liquidity in decentralized exchanges (like Uniswap) or venture capital investment—neither of which we could secure.

What I learned from this experience?

  1. Some projects require more than just time and skills—they need substantial capital and a strong community to succeed.
  2. Before starting a project, it’s crucial to assess its feasibility in terms of money (we didn’t have millions!), time (we had plenty), and skills (we were equipped).

+-+-+-+-+-+-+-+-

Clouds (Maker)

What is it?

A simple, free, and temporary file upload service with no registration required.

How it started?

I initially built this app for personal use because I often needed a quick and easy way to upload files and share links on the go.

The process of creation

  1. Found a suitable open-source backend on GitHub and forked it.
  2. Designed the dashboard interface using Figma.
  3. Deployed the code on my VPS.
  4. The app was up and running, ready for anyone to use.

How it was working?

clouds

How it ended?

The lack of registration and open access made it vulnerable to potential abuse, like uploading illegal files or malware. Concerned about misuse, I decided to shut it down.

What I learned from this experience?

  1. Before launching a free app, it’s essential to research existing alternatives. If similar solutions already exist, I should focus on creating something unique.
  2. Free apps need a long-term plan for maintenance, even without revenue. If it’s not sustainable or worth the investment of time and resources, it might not be the best idea to pursue.

+-+-+-+-+-+-+-+-

Foodish.tv (Maker)

What is it?

Refresh the foodish.tv website and see a new healthy meal with its ingredients’ prices.

How it started?

I created this app for my friend, who was eating unhealthy foods either by preparing large amounts of food in advance or eating fast food—neither of which are great for health. I wanted to show my friend and others that preparing healthy dishes can be simple and quick. Additionally, I considered monetizing the website through Google Ads or my own geo-based Ads if it gained significant traffic.

The process of creation

  1. Identified the problem through my friend’s eating habits.
  2. Designed the dashboard interface using Figma.
  3. Implemented a basic backend using Supabase.
  4. Sourced healthy dish photos from Tumblr.
  5. Manually inputted ingredient prices, with plans to use web scrapers for localized pricing in the future.
  6. Integrated a price converter API.
  7. Used Canvas.js to display the dish images along with ingredient prices.
  8. Launched the website with everything ready to use.

How it was working?

foodishtv

How it ended?

I uploaded around 15 dishes but then stopped adding more. The project didn’t resonate with me on a deeper level—it felt too simple. I realized I wanted to focus on more impactful projects, like an open-source AI email client. Since the idea didn’t excite me enough, I chose not to promote the website or continue developing it.

What I learned from this experience?

  1. Some ideas are fun as short-term hobbies, but they might not align with what I find meaningful and worth pursuing long-term.

+-+-+-+-+-+-+-+-

CakeFriend (Founder, Product Manager, frontend dev)

What is it?

Design your dream cake, we bake and deliver to you!! Ubereats but specialized for cakeshops, or a game that you can order the designed cakes!

How it started?

It was my sister’s birthday, and I thought why we cannot design a cake online, like a game, and then order it! Instead of visiting the shop, browsing pre-made designs, or manually uploading pictures we can do it online with fun and creativity! This became one of my biggest projects, where I spend a lot of time.

The process of creation

  1. Got the idea of a cake design and ordering platform inspired by my sister’s birthday.
  2. Hired a talented graphic designer as a contractor for one year to create over 500 cake items. yes thats a lot.
  3. Wrote all the front-end code (with some help from my AI assistant). The platform was fully functional, including:
    • Customer and cake shop dashboards.
    • Registration, login/signup, and cake design (using Canvas.js).
    • Online payment integration with Stripe.
    • Automated order processing, shop notifications, and order management.
  4. Hired a backend developer for one month to handle the database and backend systems.
  5. Documented detailed workflows for the backend, collaborated closely with the contractor, and held meetings every three days to ensure progress. cakefriend4
  6. Created promotional materials, including brochures and a video introduction featuring a spokesperson to explain CakeFriend.
  7. Personally visited cake shops across Toronto, Canada, and reached out via email and postal mail to shops across Canada and the USA.

How it was working?


cakefriend1
cakefriend2
cakefriend3
cakefriend4
cakefriend5

How it ended?

Despite the effort, the project failed dramatically. The core issue was the lack of interest from custom cake shops. These shops often operated at full capacity with bookings for at least a month and were not eager to adopt a platform that increases workload or requires paying commissions. Most were satisfied with their existing websites and customer base.

What I learned from this experience?

  1. Understand your audience: In B2B (or B2B2C) models, always engage with businesses before investing heavily in a solution. Their expectations and needs may differ from what you think.
  2. Start small: Don’t aim for perfection. Build an MVP first, and even before that, validate the idea with stakeholders.
  3. Cool isn’t always practical: Just because an idea excites you, and your surroundings doesn’t mean it solves a critical problem. Some ideas are “nice-to-haves,” not “must-haves.”
  4. Effort isn’t wasted: Despite the failure, I gained invaluable skills in web development, graphic design, and understanding business models. This project was a big learning opportunity to get closer to B2B business model!

+-+-+-+-+-+-+-+-

GGUUMMYY (Ideator)

What is it?

A special chat app focused on better privacy and an enhanced user experience.

How it started?

I believed I could create a highly secure and private chat app with innovative features and a visually appealing, minimalistic user interface.

The process of creation

  1. Conducted extensive research on popular chat apps by analyzing news, user complaints, reviews, and concerns related to privacy, design, and codebases.
  2. Studied various cryptographic algorithms used in existing secure P2P chat apps.
  3. Identified the Signal Protocol as one of the most advanced and widely used systems, featuring technologies like ratchets, x3DH key exchanges, and dynamic key updates for end-to-end message security.
  4. Decided to adopt a more modular and maintainable approach, exploring the Noise Protocol Framework, which offers standardized cryptographic libraries.
  5. Designed multiple user interface prototypes using Figma to visualize the app’s layout and user flow.

How it was working?

gguummyy1

How it ended?

I realized that developing a truly competitive chat app requires a team of professionals, including expert cryptographers, PhDs in mathematics, and senior software engineers, along with significant capital. The market for chat apps is saturated with free, high-quality options backed by major firms, making it highly competitive. As a solo developer, it wasn’t feasible to compete effectively.

What I learned from this experience?

  1. Avoid redundancy: Avoid building “another app for X” if the market already offers mature solutions with similar functionality. Focus on unique features or unmet needs instead.
  2. Be realistic about scope: While I can create products, some projects—like a chat app on par with WhatsApp—require large teams and significant resources.
  3. Solve new problems: Work on ideas that address unresolved issues rather than tackling the same problems already handled by established teams.
  4. Market research is key: Always evaluate the competitiveness and feasibility of entering a crowded market.

+-+-+-+-+-+-+-+-

hehe.so (co-founder, product manager, design, tech)

What is it?

An all-in-one community builder platform with modular “lego-like” features, including direct chat, group chat, knowledge base, curriculum, email client, calendar, tickets, events, social feeds, blog, file host, online support chat, analytics, search, voice and video calls, live stream, AI enabled chat box to retrieve data, voting, extended moderation tools, public and private communities, roles, permissions, customization, monetization, export content and messages, note taking, bots, form builder, simple website builder and …

The platform was designed to address the limitations of existing tools like Circle.so and Bettermode, which focus on paying users and lack generous free plans. This forced many free communities to rely on multiple disconnected platforms. The goal was to create a modern, minimal, feature-rich, and free-friendly solution.

How it started?

The idea came from the observation that many communities rely on multiple platforms to meet their diverse needs. Existing all-in-one platforms like Circle.so and Bettermode are more suitable for businesses and paid users, with limitations on free plans that make them inaccessible for communities operating on zero budgets. I aimed to create An all-in-one community builder with a generous free plan (similar business plan to Discord) and then monetize the large communities. In other words I was looking for expansion with consumers rather than businesses.

The process of creation

  1. Building the Team: I pitched the idea to a a number of of talented young individuals and persuaded two exceptional people to join:
    • Steven Wang: A Waterloo design alum.
    • Paul Mackles: A CS student from the UK, founder of Revolt Chat (a Discord alternative with a large user base). They committed to dedicating part of their time to the project.
  2. Market Research: Conducted thorough research to understand the market landscape, existing solutions, and gaps. This included analyzing competitors, evaluating their strengths and weaknesses, and gathering user feedback to identify pain points.
  3. Startup-Oriented Management: Adopted a startup approach with quick iterations, weekly sprints, and a results-driven workflow. This ensured we could make progress rapidly despite time constraints.
  4. UI Design: Created prototype designs for the user interface, emphasizing modernity, usability, and minimalism.
  5. Backend Discussions: Collaborated on defining the backend architecture, ensuring scalability and alignment with project goals.
  6. Business Model Development: Explored sustainable business models and competitive pricing strategies that could rival existing solutions.
  7. worked on it for 3 weeks

How it was working?

hehe6
hehe5
hehe4
hehe3
hehe2
hehe1

How it ended?

Team Challenges:

  • Paul Makles became preoccupied with scaling Revolt Chat after a surge in users due to government bans on Discord in Russia and Turkey.
  • Steven Wang relocated after graduation and shifted focus to finding a full-time/freelance paid employment.

Motivation and Funding:

  • The equity-sharing model (1-year cliff, 4-year vest) failed to motivate co-founders who preferred immediate paid positions.
  • Lack of VC funding made it impossible to sustain the project.

What I learned from this experience?

Efficient Project Management: Embraced a Y Combinator-style approach with rapid iterations, focused sprints, and clear weekly objectives.

Agility in Execution: Prioritized fast prototyping, learning from outcomes, and iterating to improve.

Importance of Funding: Even a great idea and a strong team cannot succeed without sufficient financial resources.

Incentives Matter: Equity-sharing may not be enough to sustain motivation, especially when co-founders need immediate income.

Market Fit vs. Resources: Building a competitive product requires both a compelling idea and the resources to see it through.