Skip to content
OverviewSolutions
9
Comments
5
Muhammad Gad
@GADMuhammad

All comments

  • abdalla shaker•140
    @abdalla-shaker
    What are you most proud of, and what would you do differently next time?

    making a custom hook and implementing some new things in my code such as modal component and forwardRef and many other things I don't remember TBH.

    What challenges did you encounter, and how did you overcome them?

    Opening the modal using context api was a pain but i cancelled that idea as the code didn't work asynchronously so i went back to prop drilling (well it's not prob drilling because i passed the functions to one component only) and i was gonna use useReducer instead of useState but the state updating functions was not complicated so I canceled that idea.

    What specific areas of your project would you like help with?

    Any feedback is appreciated

    REST Countries API

    #react
    2
    Muhammad Gad•260
    @GADMuhammad

    1- When a country is open, make the background blur. to not make the user get confused.

    2- It should close when pressing outside the country modal (pop-up).

    3- On every country page, border countries should be buttons to open this border-country page. Not <li>s inside <ul>

    4- The country page modal should be gone with animation like it appears with animation. Not immediately.

    4- On the list of continents in the light mode, when I hover an option, its background should be more obvious, not that light.

    5- The option of "reset" should be called "All countries".

    6- The placeholder of the input should be lighter.

    7- When I click outside the list of continents, it should close. The same as the modal.

    Marked as helpful
  • Muhammad Gad•260
    @GADMuhammad

    Give the colour change when (hover) a transition to make it smooth. It will be more fancy.

  • Muhammad Gad•260
    @GADMuhammad

    1- Make the header sticky >> to facilitate navigation on the page

    2- In the footer, do not let the href of <a> tag empty. put your own to facilitate communication with you

    3- Reduce some padding in the testimonial section. It is huge.

    Marked as helpful
  • Muhammad Gad•260
    @GADMuhammad

    Great work!

    but what about giving due care to accessibility? Using the keyboard to calculate.

  • SatishB15•160
    @SatishB15
    What are you most proud of, and what would you do differently next time?

    Proud of:

    1. User Interface Design: I'm particularly proud of the clean and intuitive user interface that makes the Age Calculator easy to use for people of all ages.

    2. Accuracy and Performance: Ensuring that the calculations are precise and the application performs efficiently was a key achievement. The app handles various date formats and edge cases accurately.

    3. Code Quality: Maintaining high code quality with clear documentation and well-structured code has been a significant accomplishment.

    Do Differently Next Time:

    1. Enhanced Features: Next time, I would implement additional features such as calculating age in different time units (e.g., weeks, days, hours) and adding a feature to save and compare multiple dates.

    2. User Feedback Integration: I would set up a more structured process for gathering and integrating user feedback earlier in the development cycle to better align the project with user needs.

    3. Automated Testing: Incorporating automated testing from the beginning would help in catching bugs early and ensuring the reliability of the application.

    What challenges did you encounter, and how did you overcome them?

    Challenges:

    1. Date Handling: One of the main challenges was handling various date formats and ensuring the application could accurately compute ages regardless of the input format.

    2. Cross-Browser Compatibility: Ensuring the application worked seamlessly across different web browsers required significant testing and adjustments.

    Overcoming Challenges:

    1. Date Handling: To overcome this, I researched and implemented robust date-parsing libraries that could handle multiple formats and edge cases effectively.

    2. Cross-Browser Compatibility: I utilized extensive testing on multiple browsers and used polyfills to ensure compatibility with older browser versions, ensuring a consistent user experience.

    What specific areas of your project would you like help with?

    Areas for Help:

    1. User Experience (UX) Design: I would appreciate feedback and suggestions from UX designers to improve the overall user experience, making the interface even more user-friendly and accessible.

    2. Localization: Assistance with localizing the application for different languages and regions would be valuable to make the Age Calculator accessible to a global audience.

    3. Advanced Features: Help with implementing advanced features like saving date comparisons, integrating with calendar APIs, or adding more complex calculations (e.g., accounting for leap years more elegantly) would be beneficial.

    Age Calculator App

    1
    Muhammad Gad•260
    @GADMuhammad

    1. The age does not appear when clicking the button or pressing Enter.

    2. There is no need to change the cursor to a pointer when hovering over the input field; keep the default cursor.

    3. Limit the input values based on their type. For example, in the input for days, do not allow the user to enter a number larger than 31, as no month has more than 31 days, and so on.

    4. Prioritize accessibility. It is crucial, and most of the time, users find it more comfortable to use the keyboard instead of the mouse.

    I have already completed this project. You can review it if needed. I believe it will be very useful for providing you with some programming logic.