<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Nilam Kumari Mahato</title>
    <description>The latest articles on DEV Community by Nilam Kumari Mahato (@nilammahato10).</description>
    <link>https://dev.to/nilammahato10</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4159679%2F81c36736-4646-40ee-a7c2-0ecda190bc70.jpg</url>
      <title>DEV Community: Nilam Kumari Mahato</title>
      <link>https://dev.to/nilammahato10</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/nilammahato10"/>
    <language>en</language>
    <item>
      <title>DesignSpark — Never Stare at a Blank Figma Canvas Again ✨</title>
      <dc:creator>Nilam Kumari Mahato</dc:creator>
      <pubDate>Mon, 05 Oct 2026 02:25:46 +0000</pubDate>
      <link>https://dev.to/nilammahato10/designspark-never-stare-at-a-blank-figma-canvas-again-1p6i</link>
      <guid>https://dev.to/nilammahato10/designspark-never-stare-at-a-blank-figma-canvas-again-1p6i</guid>
      <description>&lt;p&gt;&lt;em&gt;This is a submission for the &lt;a href="https://dev.to/challenges/hacktoberfest-weekend-2026-10-01"&gt;Hacktoberfest Weekend Challenge: Build for a Friend&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What I Built
&lt;/h2&gt;

&lt;p&gt;DesignSpark is an AI-powered UI/UX design challenge generator that I built for a friend who is learning UI/UX design.&lt;br&gt;
One of the biggest problems she faces isn't knowing how to design.&lt;br&gt;
It's knowing what to design.&lt;br&gt;
Sometimes you open Figma, create a new blank frame, and then spend more time thinking:&lt;br&gt;
"Okay... but what should I actually make?"&lt;/p&gt;

&lt;p&gt;That's where DesignSpark comes in.&lt;br&gt;
Instead of generating a complete UI, DesignSpark gives you a realistic design problem to solve yourself.&lt;br&gt;
You choose:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;🎯 A design category&lt;/li&gt;
&lt;li&gt;📊 A difficulty level
And DesignSpark generates a structured design challenge containing things like:&lt;/li&gt;
&lt;li&gt;A realistic problem&lt;/li&gt;
&lt;li&gt;Target users&lt;/li&gt;
&lt;li&gt;User scenario&lt;/li&gt;
&lt;li&gt;Design objective&lt;/li&gt;
&lt;li&gt;Design task&lt;/li&gt;
&lt;li&gt;Constraints&lt;/li&gt;
&lt;li&gt;Edge cases&lt;/li&gt;
&lt;li&gt;Things to think about&lt;/li&gt;
&lt;li&gt;Suggested number of screens
For example:
Category: Healthcare
Difficulty: Intermediate&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Challenge:&lt;br&gt;
Design a medication management experience&lt;br&gt;
for elderly users who take multiple medications&lt;br&gt;
throughout the day.&lt;/p&gt;

&lt;p&gt;Target User:&lt;br&gt;
Adults aged 60+ managing daily medication.&lt;/p&gt;

&lt;p&gt;Constraints:&lt;br&gt;
• The experience should be easy to understand.&lt;br&gt;
• Consider accessibility and readability.&lt;br&gt;
• Handle missed medication scenarios.&lt;/p&gt;

&lt;p&gt;Edge Cases:&lt;br&gt;
• A user forgets a dose.&lt;br&gt;
• Medication schedule changes.&lt;br&gt;
• Multiple medications have overlapping times.&lt;/p&gt;

&lt;p&gt;The important part is that DesignSpark doesn't design the solution for you.&lt;br&gt;
It gives you the problem.&lt;br&gt;
You bring the creativity. We bring the challenge. ✨&lt;/p&gt;

&lt;h2&gt;
  
  
  Demo
&lt;/h2&gt;

&lt;p&gt;Live Demo:&lt;a href="https://designspark-1.onrender.com/" rel="noopener noreferrer"&gt;DesignSpark&lt;/a&gt;&lt;br&gt;
Demo Video:&lt;a href="https://youtu.be/LwGrssUzlGw" rel="noopener noreferrer"&gt;VideoDemo&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Code
&lt;/h2&gt;

&lt;p&gt;GitHub:&lt;a href="https://github.com/Nilam-Kumari-Mahato/DesignSpark" rel="noopener noreferrer"&gt;Github Repo&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  How I Built It
&lt;/h2&gt;

&lt;p&gt;The core stack is:&lt;br&gt;
Frontend&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;React&lt;/li&gt;
&lt;li&gt;TypeScript&lt;/li&gt;
&lt;li&gt;Vite&lt;/li&gt;
&lt;li&gt;Tailwind CSS&lt;/li&gt;
&lt;li&gt;React Router&lt;/li&gt;
&lt;li&gt;Lucide React&lt;/li&gt;
&lt;li&gt;Framer Motion
Backend&lt;/li&gt;
&lt;li&gt;Node.js&lt;/li&gt;
&lt;li&gt;Express.js&lt;/li&gt;
&lt;li&gt;Zod&lt;/li&gt;
&lt;li&gt;CORS&lt;/li&gt;
&lt;li&gt;dotenv
AI
The most important part of DesignSpark is Gemma 4.
I use the open-weight Gemma 4 model through Google's API to generate the design challenges.
The architecture looks like this:
            DesignSpark
                 │
                 ▼
         React + TypeScript
                 │
                 │ category
                 │ difficulty
                 ▼
         Express.js Backend
                 │
                 ▼
          Challenge Prompt
                 │
                 ▼
              Gemma 4
                 │
                 ▼
        Structured Challenge
                 │
                 ▼
         React Challenge UI&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I deliberately kept the AI on the backend rather than calling it directly from the frontend so that the API key isn't exposed to the client.&lt;br&gt;
The backend also validates the user's category and difficulty before sending the request to the model.&lt;br&gt;
The AI's role&lt;br&gt;
I wanted to avoid building another tool where AI simply creates a UI and the human watches.&lt;br&gt;
Instead, Gemma acts more like a design challenge mentor.&lt;br&gt;
The prompt tells the model:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Don't generate HTML/CSS.&lt;/li&gt;
&lt;li&gt;Don't generate code.&lt;/li&gt;
&lt;li&gt;Don't create a wireframe.&lt;/li&gt;
&lt;li&gt;Don't specify the exact UI layout.&lt;/li&gt;
&lt;li&gt;Don't solve the design problem.&lt;/li&gt;
&lt;li&gt;Give the designer enough context to solve it creatively.
This means the AI provides the starting point, while the human still does the actual design work.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Why Does Open Innovation Matter?
&lt;/h2&gt;

&lt;p&gt;For DesignSpark, open innovation is important because the goal isn't just to use AI — it's to use AI in a way that keeps the human creative process at the center.&lt;br&gt;
A closed AI system could generate a complete interface for the user.&lt;br&gt;
But that's not what I wanted.&lt;br&gt;
I'm building DesignSpark for someone who is trying to learn design.&lt;br&gt;
If the AI creates the entire solution, she doesn't get to practice the skills she's trying to develop.&lt;br&gt;
Using an open-weight model like Gemma lets me build an AI-assisted workflow where the model provides structured challenges while the designer remains responsible for the creative decisions.&lt;br&gt;
It also gives developers more freedom to experiment with how AI is integrated into applications rather than treating AI as a black-box feature.&lt;br&gt;
For DesignSpark, open innovation makes it possible to explore a different question:&lt;br&gt;
What if AI didn't replace the creative process, but helped people start it?&lt;/p&gt;

&lt;p&gt;That's the idea behind DesignSpark.&lt;/p&gt;

&lt;h2&gt;
  
  
  My Agent Session
&lt;/h2&gt;

&lt;p&gt;I used an AI coding agent during development to help structure the Express backend, integrate the Gemma 4 API, and improve the project architecture.&lt;/p&gt;

&lt;h2&gt;
  
  
  Prize Categories
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Gemma&lt;/strong&gt; — Gemma 4 is the core AI model powering DesignSpark's design challenge generation.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Render&lt;/strong&gt; — The DesignSpark is deployed on Render .&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>devchallenge</category>
      <category>weekendchallenge</category>
      <category>hf26challenge</category>
    </item>
  </channel>
</rss>
