Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 3 years ago

Mobile-first w/ Vue 3 + Composition API, Tailwind, TypeScript, Vite

tailwind-css, vue, typescript
Ilan•675
@iknowmagic
A solution to the Pomodoro app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Feedback is appreciated :)

A Mobile-First project featuring Vue 3 + Composition API, Tailwind, Vite, TypeScript.

The "start" text was changed to "resume" but it can be easily changed back to "start" if needed. Typically this would be something to discuss with the stockholder/project manager.

A few "advanced features" have been added (they can be easily hidden from the final implementation if not wanted). This is something to discuss with the stockholder/project manager.

Advanced features: Auto transition from pomodoro to short/long breaks. Option to show/hide the seconds (the seconds' constant flickering is somewhat distracting). Option to show the current amount of pomodoros completed. Reset option.

Comments for the stockholder/project manager.

The "restart" text/functionality needs to be revisited.

The intention seems to be that as soon as the pomodoro time is over, the "restart" option is presented.

Is the "restart" option needed for short/long breaks? If the restart option is not included in the short/long breaks, is the user experience inconsistent between pomodors and breaks?

The advanced features section allows automatic transition from pomodoro to short/long breaks. This seems to be a better UX and it does not require the above-mentioned "restart" treatment.

Other - To be discussed with stockholder/project manager.

The pomodoro progress bar is shown as a favicon. This allows the user to pin the page or move to other tabs and still see the pomodoro's activity.

The state of the application is saved so the user can reopen the application at any time and continue where they left off.

Missing / Todo: Unit Testing, Accessibility Check

Thanks!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Ilan's solution.

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord
Frontend Mentor logo

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit all CSS, SCSS and Less files in your repository.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

How does the JavaScript validation report work?

When a solution is submitted, we use eslint to run an automated check on the JavaScript code.

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.