mirror of
https://github.com/foss42/apidash.git
synced 2025-05-20 07:46:32 +08:00
Janavi Mahadik Application
This commit is contained in:
Janavi Mahadik
91
doc/proposals/2025/gsoc/Janavi Mahadik
Normal file
91
doc/proposals/2025/gsoc/Janavi Mahadik
Normal file
@ -0,0 +1,91 @@
|
||||
### About
|
||||
|
||||
1. *Full Name:* Janavi Mahadik
|
||||
2. *Contact info:* janavimahadik06@gmail.com 9136344543
|
||||
3. *Discord handle:* janavimahadik_15736
|
||||
4. *GitHub profile link:* https://github.com/JanaviMahadik
|
||||
5. *LinkedIn:* https://www.linkedin.com/in/janavi-mahadik-b8054b24b/
|
||||
6. *Hackerrank:* https://www.hackerrank.com/profile/janavimahadik06
|
||||
7. *Leetcode:* https://leetcode.com/u/janavimahadik/
|
||||
8. *Time zone:* IST (UTC +5:30)
|
||||
9. *Link to a resume:* https://drive.google.com/file/d/1UvCNjcUxiyXia7crq_Hm0esl1UPQ5IoV/view?usp=drive_link
|
||||
|
||||
|
||||
|
||||
### University Info
|
||||
|
||||
1. *University name:* University of Mumbai, SVKM’s Mithibai College
|
||||
2. *Program:* Bachelor of Computer Science
|
||||
3. *Year:* Final Year
|
||||
4. *Expected graduation date:* May 2025
|
||||
|
||||
|
||||
|
||||
### Motivation & Past Experience
|
||||
|
||||
1. *Have you worked on or contributed to a FOSS project before?*
|
||||
While I haven’t contributed to any major public FOSS project yet, I have built full-stack projects like Khanawal (my own project) and
|
||||
participated in hackathons and collaborative academic projects which follow open-source development practices.
|
||||
I am eager to contribute meaningfully to real-world open-source projects like API Dash.
|
||||
|
||||
2. *What is your one project/achievement that you are most proud of? Why?*
|
||||
I’m most proud of Khanawal, a full-stack food ordering and management system that I built independently using Flutter, React.js, Node.js, Express, MongoDB, and Firebase.
|
||||
It gave me real-world experience in integrating frontends, backends, and databases using REST APIs, and taught me how to manage user roles, build UIs, and implement analytics.
|
||||
|
||||
3. *What kind of problems or challenges motivate you the most to solve them?*
|
||||
I enjoy solving challenges that bridge the gap between complex backend data and meaningful user interfaces—especially when it improves user experience and productivity.
|
||||
Problems involving automation, visualization, or data interaction excite me the most.
|
||||
|
||||
4. *Will you be working on GSoC full-time? In case not, what will you be studying or working on while working on the project?*
|
||||
Yes, I will be available full-time during the GSoC period. While I will have regular college hours, I will ensure uninterrupted availability for project work and mentor sync-ups,
|
||||
dedicating the required hours per week.
|
||||
|
||||
5. *Do you mind regularly syncing up with the project mentors?*
|
||||
Not at all! Regular communication helps align goals and expectations, and I am happy to schedule sync-ups, demos, or progress reports.
|
||||
|
||||
6. *What interests you the most about API Dash?*
|
||||
The idea of turning raw API responses into interactive, customizable UI elements excites me. It aligns well with my experience in full-stack development and my interest in combining backend logic
|
||||
with intuitive frontends. I’m also excited to work with Flutter and real-time rendering tools.
|
||||
|
||||
7. *Can you mention some areas where the project can be improved?*
|
||||
- Introducing support for both JSON and XML parsing can increase compatibility.
|
||||
- Providing a visual drag-and-drop UI builder could enhance the user experience.
|
||||
- Integrating export templates for popular frameworks (e.g., React, Flutter widgets) can help with faster integration into apps.
|
||||
- Adding version control for UI snapshots or generated components could make the system more developer-friendly.
|
||||
|
||||
|
||||
|
||||
|
||||
### Project Proposal Information
|
||||
|
||||
1. *Proposal Title:* AI UI Designer for APIs – Dynamic UI Generator from API Responses
|
||||
|
||||
2. *Abstract:*
|
||||
This project aims to develop an AI-powered agent that automatically generates dynamic, user-friendly UI components from structured API responses (JSON/XML).
|
||||
By analyzing the API structure, the agent will create UI elements such as tables, forms, charts, and cards, which users can customize and export into their Flutter/Web apps.
|
||||
This eliminates manual UI coding and enhances the developer workflow.
|
||||
|
||||
3. *Detailed Description:*
|
||||
The system will accept API endpoints and parse the response structure (JSON/XML). Based on the data types and patterns, the agent will use AI-based heuristics and predefined rules to
|
||||
create appropriate UI components:
|
||||
- Lists/tables for arrays of objects
|
||||
- Input forms for structured fields
|
||||
- Graphs for numerical trends
|
||||
- Cards for object summaries
|
||||
Users will have customization options to change styles, rearrange components, apply filters, pagination, and sorting. The generated UI will be exportable as code (Flutter widgets, HTML/CSS/JS for web apps)
|
||||
for seamless integration. A real-time previewer will also be included for live editing and visualization.
|
||||
|
||||
4. *Weekly Timeline:*
|
||||
| Week | Goals / Activities | Deliverables |
|
||||
|--------|--------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------|
|
||||
| Week 1 | Community bonding, understand the API Dash codebase and architecture, set up development environment | Local setup ready, active communication with mentors and community |
|
||||
| Week 2 | Develop core parser to analyze JSON/XML API responses and begin dynamic mapping to UI components | Basic JSON/XML structure parser with object-type identification |
|
||||
| Week 3 | Implement automatic UI component generation (cards, tables, forms) with real-time API integration | Initial auto-generated UI layout rendering from sample API response |
|
||||
| Week 4 | Add interactivity features: filters, sorting, pagination; begin frontend-export setup | Dynamic UI components with interactivity; partial export code for web/flutter |
|
||||
| Week 5 | Improve customization options: themes, layout, component styling | Customization interface; multiple layout templates with applied themes |
|
||||
| Week 6 | Refactor and modularize code; integrate generated components into existing API Dash system | Seamless integration with API Dash interface; improved code structure |
|
||||
| Week 7 | Extend support for complex/nested API response structures; maintain tests and benchmarks regularly | Robust UI generation for advanced responses; test coverage updates |
|
||||
| Week 8 | Improve export functionality with advanced options for Flutter/Web; validate with multiple frameworks | Finalized export feature with support for multiple frameworks |
|
||||
| Week 9 | Integrate with existing API Dash features; fix bugs and address feedback from mentors and users | Stable version integrated into API Dash; resolved issues based on iterative feedback |
|
||||
| Week 10| Final polish, optimization, and performance testing; prepare final reports, user guide, and GSoC submission | Optimized, production-ready version with documentation and submission deliverables complete |
|
||||
|
||||
Reference in New Issue
Block a user