UI/UX Designer + Flutter/React Native Developer Needed — Digital School Calendar App (Phase 1)

Please read the whole document. Project Overview We are developing a modern, beautifully designed digital school calendar app that transforms the traditional physical school calendar/diary into a clean, interactive digital experience for parents and students. The first version will focus specifically on the school academic calendar — holidays, examinations, events, important dates and other key academic information. The objective is NOT to build a complicated school ERP. We want something that feels: Modern Clean Extremely easy to use Lightweight Fast Visually attractive Parent-friendly Suitable for children/families Much more polished than traditional school ERP applications The product should feel closer to a premium consumer mobile app than a school management system. The physical school calendar will be the primary source of information and inspiration for Phase 1. PHASE 1 — DIGITAL SCHOOL CALENDAR 1. Academic Year Home / Year-at-a-Glance The user should immediately be able to see the entire academic year. Example: 2026–27 Academic Calendar June → July → August → September → October → November → December → January → February → March → April → May The user should be able to quickly understand: School holidays Examination periods Major school events Parent–teacher meetings Sports events Cultural events Academic events Important dates The design should allow the user to understand the school year visually within a few seconds. This should be a visual snapshot, not a dense spreadsheet. 2. MONTH VIEW The primary calendar experience. Users should be able to select any month and see a clean monthly calendar. Example: SEPTEMBER 2026 A conventional calendar grid should be displayed, but important dates should have subtle visual indicators/icons. For example: 🏖 Holiday 📝 Exam 🎉 Event 👨‍👩‍👧 Parent Meeting 🏆 Sports 📚 Academic The exact icon style will be determined during UI/UX design. Clicking a date should reveal the events occurring on that day. Example: 8 September 📝 Mathematics Examination 18 September 👨‍👩‍👧 Parent–Teacher Meeting 3. QUARTER VIEW Users should also be able to view the academic year quarter by quarter. For example: Q1 June · July · August Q2 September · October · November Q3 December · January · February Q4 March · April · May The quarter view should provide a visual overview of the major dates and activities occurring during that period. The goal is: "Show me what is coming up over the next three months." 4. HOLIDAYS VIEW A dedicated section showing all holidays in the academic year. Example: 2026–27 HOLIDAYS June 12 June — School Holiday July 15 July — School Holiday August 15 August — Independence Day September ... The user should not have to go through every month to find holidays. At the top we may display useful information such as: 18 Holidays This Year Next Holiday — 7 Days The exact presentation can be proposed by the designer. 5. EXAM VIEW A dedicated examination calendar. Example: EXAM CALENDAR TERM 1 08 September — Mathematics 10 September — English 12 September — Science 15 September — French TERM 2 ... FINAL EXAMINATION ... The user should be able to see examinations chronologically and/or grouped by examination period. If the school provides grades/classes, the system should be designed so that exams can eventually be filtered by grade/class. 6. EVENTS VIEW A dedicated list/grid/timeline of important school events. Possible categories: Academic Sports Cultural Trips Parent–Teacher Meetings Competitions School functions Workshops Other important events Users should be able to filter events by category. 7. EVENT DETAIL SCREEN When a user taps an event: Mathematics Examination 8 September 2026 Grade 3 Mathematics Examination Time: 9:00 AM – 10:00 AM Additional information can be displayed if provided by the school. Potential future functionality: Add to phone calendar Set reminder View syllabus Attach documents View instructions These features do not necessarily need to be implemented in the first MVP unless they are straightforward to include. 8. ICONS / VISUAL ASSETS This is an important part of the project. We do NOT expect the freelancer to create every illustration/icon from scratch. The app should make intelligent use of existing high-quality clipart/icon libraries and commercially usable assets, where appropriate. For example: Holiday icon Exam icon Sports icon School event icon Parent meeting icon Academic icon Travel/trip icon Important date icon The designer/developer should be comfortable sourcing suitable icons/clipart from existing libraries such as: Flaticon Freepik Icons8 Noun Project Material Symbols Font Awesome Other appropriately licensed libraries IMPORTANT: All visual assets used in the final product must have licensing that permits commercial use. The freelancer must clearly document the source/license of any third-party assets used. We are NOT looking for a completely custom illustration-heavy app. We want a smart combination of clean UI, typography, colour, layout and existing visual assets. The icons should feel cohesive even if sourced from existing libraries. 9. DESIGN DIRECTION The application should NOT look like a traditional school ERP. Avoid: Dense dashboards Tiny text Too many buttons Complicated navigation Old-fashioned tables Excessive borders Visually cluttered screens Generic ERP templates We want: Clean Modern Friendly Premium Lightweight Intuitive Think of the UX quality of modern consumer applications rather than traditional school software. The app should be understandable by a parent without any training. 10. RESPONSIVE / MOBILE-FIRST The initial product is primarily intended for: iPhone Android phones The design should accommodate different screen sizes. Tablet support should also be considered. A responsive web/admin interface will eventually be required for school administrators. 11. ADMIN / SCHOOL DATA ENTRY The school will eventually need a simple admin interface to manage the calendar. The admin should be able to create: Holiday Name Date Description Applicable grades/classes Optional attachment Exam Exam name Subject Date Time Grade/class Description Event Event name Date Time Category Applicable grades/classes Description Optional image/attachment The admin interface should be extremely simple. The school should not need technical knowledge. 12. DATA STRUCTURE The application should be built with the future product in mind. Although Phase 1 is only a calendar, the underlying architecture should allow future modules such as: Announcements Homework Attendance Parent communication School notices Student information Documents Notifications Teacher communication School ERP integrations Do not build these features in Phase 1. However, the code/database architecture should not make future expansion unnecessarily difficult. 13. TECHNOLOGY We are open to recommendations, but would prefer a modern cross-platform approach such as: Flutter or React Native Backend can be proposed by the developer depending on the architecture. We want: Clean code Scalable architecture Proper database structure API-based architecture Secure authentication Easy future maintenance Proper documentation Please recommend your preferred technology stack and explain why. 14. DELIVERABLES — PHASE 1 UI/UX Complete Figma design for: Splash/onboarding if required Login Home / Year-at-a-Glance Month view Quarter view Holiday view Exam view Events view Event detail Navigation Empty states Loading states Error states Basic notification states Development A working mobile application for Android and iOS. Admin Basic school calendar administration interface. Backend Database + APIs required for Phase 1. Documentation Source code Figma files Database structure API documentation Setup instructions Third-party asset/license list 15. IMPORTANT — PHASE 1 IS A PAID MVP We want to develop this in clearly separated phases. PHASE 1 Digital School Calendar The focus is: Take the physical school calendar and make it an exceptionally good digital experience. We do NOT want the freelancer expanding the scope unnecessarily. Do not add: Fees Attendance Homework Transport Payroll Library Full ERP Complex student management Those may become future phases. 16. FUTURE PHASES If Phase 1 is successful, the product can eventually expand into a broader parent-school platform. Potential future modules: Phase 2 Announcements + Notifications Phase 3 Homework / Assignments Phase 4 Attendance Phase 5 Parent–Teacher Communication Phase 6 Documents / Permissions Phase 7 ERP integrations The freelancer selected for Phase 1 may be considered for subsequent phases. 17. WHO WE ARE LOOKING FOR We are looking for an individual freelancer or very small team who can handle: UI/UX + Mobile Development + Backend or a strong UI/UX designer working together with an experienced developer. The ideal candidate has experience creating: Consumer mobile applications Education applications Calendar applications Parent-facing applications SaaS products Modern mobile interfaces Please do NOT apply if your main experience is building generic ERP dashboards. 18. WHAT WE VALUE MOST More important than having hundreds of previous projects: 1. Taste You understand what makes an app look genuinely modern. 2. UX thinking You understand how a parent will actually use the application. 3. Simplicity You know what NOT to put on the screen. 4. Attention to detail Spacing, typography, icons, animations and transitions should feel polished. 5. Technical quality The application should be fast, stable and maintainable. 19. APPLICATION REQUIREMENTS Please include the following in your proposal: A. Portfolio Show us 3 mobile applications you have designed/developed that demonstrate strong UI/UX. Please provide links/screenshots. B. Your proposed technology stack For example: Flutter + Firebase or React Native + Node + PostgreSQL Explain briefly. C. Your approach In 5–10 sentences, explain how you would turn a physical school calendar into a digital product. D. UI/UX concept Please explain how you would approach: Year view Month view Quarter view Holidays Exams Events E. Third-party assets Tell us which icon/clipart libraries you normally use and how you handle commercial licensing. F. Timeline Give us your realistic estimate for completing Phase 1. G. Cost Provide: UI/UX cost Development cost Total Phase 1 cost Please separate these clearly. 20. VERY IMPORTANT — DO NOT BUILD FROM A TEMPLATE We are not looking for a generic calendar template downloaded from ThemeForest or another marketplace. We want a custom-designed product using established UI principles and existing licensed visual assets where appropriate. Using existing icon/clipart libraries is completely acceptable and encouraged. However, the overall product experience, layout and interaction design should be original and thoughtfully designed. 21. SUCCESS CRITERIA At the end of Phase 1, a parent should be able to open the app and answer these questions almost immediately: What is happening this month? When are the holidays? When are the exams? What important school events are coming up? What is happening in the next three months? What is happening during the entire academic year? If a parent has to search through multiple menus to answer these questions, the UX has failed. PROJECT PHILOSOPHY The physical school calendar is already useful. We are not trying to digitise it by simply putting the same information into a generic calendar. We want to rethink the experience for digital. The result should feel like: "This is what the school calendar should have been all along." This is the first product in what could eventually become a much larger school-parent platform, so we are looking for someone who can think beyond just writing code while still respecting the strict Phase 1 scope. Phase 1 : $200 Further, every milestone will be at $300