English for developers · Daily standup

Daily standup phrases in English

Quick answer

Here are 280 daily standup phrases from the Devlingo app, each with when to use it and the audio of the pronunciation. They go from “No blockers on my end” to an incident update, sorted by level.

Updated

A standup almost always follows the same order: what you did yesterday, what you will do today and what is blocking you. Learn one phrase for each part and swap only the subject (the screen, the endpoint, the ticket).

Easy phrases (155)

  1. I'm working on the login feature today.

    When to use it: Sharing your current task during daily standup

  2. Yesterday I finished the API integration.

    When to use it: Reporting what you completed the previous day

  3. No blockers on my end.

    When to use it: Confirming you have no impediments

  4. I'll continue with the same task.

    When to use it: Indicating you're still working on the same item

  5. I'm almost done with my ticket.

    When to use it: Letting the team know you're close to finishing

  6. I'll pick that up after lunch.

    When to use it: Committing to start a task later

  7. I pushed my changes yesterday.

    When to use it: Telling the team you committed code

  8. The tests are passing now.

    When to use it: Confirming your tests are green

  9. I need to update the documentation.

    When to use it: Mentioning a documentation task

  10. I'm reviewing the pull request.

    When to use it: Telling the team you're doing code review

  11. I'll start the new sprint item today.

    When to use it: Planning to begin a new task

  12. Everything is on track.

    When to use it: Confirming progress is going well

  13. I fixed the bug in the checkout flow.

    When to use it: Reporting a bug fix

  14. I'll be working on the database migration.

    When to use it: Announcing your planned task

  15. I created a new branch for the feature.

    When to use it: Telling the team about your branch

  16. I'm waiting for the design to be finalized.

    When to use it: Explaining a dependency on design team

  17. I'll move this ticket to done.

    When to use it: Closing a completed task

  18. I need to write more tests.

    When to use it: Mentioning testing work needed

  19. The deployment went smoothly.

    When to use it: Reporting a successful deployment

  20. I'm pairing with Alex on this.

    When to use it: Telling the team about collaboration

  21. I updated the Jira board.

    When to use it: Confirming project board is current

  22. Good morning, everyone.

    When to use it: Greeting the team at standup

  23. That's all from me.

    When to use it: Signaling you're done with your update

  24. I'm on track to finish by Friday.

    When to use it: Giving a timeline estimate

  25. I refactored the service layer.

    When to use it: Reporting code improvement work

  26. I need access to the staging server.

    When to use it: Requesting permissions

  27. I'll add error handling to that endpoint.

    When to use it: Planning to improve code robustness

  28. Can someone review my PR?

    When to use it: Asking for a code review

  29. I'll sync up with the backend team.

    When to use it: Planning cross-team coordination

  30. I merged my branch into develop.

    When to use it: Reporting a merge

  31. I resolved the merge conflict.

    When to use it: Reporting conflict resolution

  32. I'm setting up the dev environment.

    When to use it: Working on environment configuration

  33. I updated the dependencies.

    When to use it: Reporting package updates

  34. I optimized the database query.

    When to use it: Reporting performance improvement

  35. I'm looking into the performance issue.

    When to use it: Investigating a problem

  36. I added unit tests for the new feature.

    When to use it: Reporting test additions

  37. I estimate about two more days of work on this ticket.

    When to use it: Giving a time estimate for remaining work

  38. I'm debugging an edge case.

    When to use it: Working on a tricky bug

  39. I'll work on the responsive layout.

    When to use it: Planning UI work

  40. I'm implementing the search functionality.

    When to use it: Working on search feature

  41. I'm stuck on this issue — can someone take a look with me after standup?

    When to use it: Asking for help with a blocker during standup

  42. I paired with Sarah yesterday to work through the database design.

    When to use it: Mentioning you paired with someone yesterday

  43. I'm actually ahead of schedule on this one.

    When to use it: Reporting you are ahead of schedule

  44. We'll need to update the timeline — this task is more complex than expected.

    When to use it: Saying you need to update the project timeline

  45. I'm waiting on the platform team to deploy their service before I can continue.

    When to use it: Noting a dependency on another team's work

  46. I attended the knowledge-sharing session on Kubernetes yesterday.

    When to use it: Mentioning you attended a knowledge-sharing session

  47. I spent part of yesterday onboarding the new developer on our codebase.

    When to use it: Reporting you onboarded a new team member

  48. I refactored the legacy code in the billing module to make it testable.

    When to use it: Saying you refactored legacy code

  49. I set up monitoring alerts for the new endpoints.

    When to use it: Mentioning you set up monitoring alerts

  50. I wrote integration tests for the checkout workflow.

    When to use it: Reporting you wrote integration tests

  51. I updated the CI pipeline to run linting before the tests.

    When to use it: Saying you updated the CI pipeline configuration

  52. I participated in the architecture review for the new microservice.

    When to use it: Mentioning you participated in an architecture review

  53. I migrated the user data from the old schema to the new one.

    When to use it: Reporting you migrated data from old schema

  54. I profiled the app and found a few performance bottlenecks in the rendering layer.

    When to use it: Saying you profiled the app for performance bottlenecks

  55. I fixed several accessibility issues flagged by the audit tool.

    When to use it: Mentioning you fixed accessibility issues

  56. I updated our third-party dependencies to their latest stable versions.

    When to use it: Reporting you updated third-party dependencies

  57. I documented all the API endpoints in the wiki.

    When to use it: Saying you documented the API endpoints

  58. I created runbooks for the ops team to handle common incidents.

    When to use it: Mentioning you created runbooks for ops team

  59. I implemented error tracking so we can catch crashes in production.

    When to use it: Reporting you implemented error tracking

  60. I reviewed the security audit findings and created tickets for each vulnerability.

    When to use it: Saying you reviewed the security audit findings

  61. I'll handle that.

    When to use it: Volunteering for a task

  62. Let me check on that.

    When to use it: Offering to investigate something

  63. I'll have it ready by tomorrow.

    When to use it: Committing to a timeline

  64. Nothing new to report.

    When to use it: When you have no significant updates

  65. I ran the full test suite.

    When to use it: Confirming comprehensive testing

  66. I'll sync with QA to make sure they have test cases ready for this feature.

    When to use it: Coordinating with the QA team on testing

  67. The feature is code complete.

    When to use it: Reporting feature completion

  68. I'm updating the API documentation.

    When to use it: Working on API docs

  69. I need to refactor this component.

    When to use it: Planning code improvement

  70. I'll clean up the code before merging.

    When to use it: Planning pre-merge cleanup

  71. I'm working on the frontend refactor.

    When to use it: Sharing your current task

  72. I closed three tickets yesterday.

    When to use it: Reporting completed work

  73. I'm pair programming with the new hire today.

    When to use it: Describing collaborative work

  74. My PR is waiting for approval.

    When to use it: Sharing blocker status

  75. I'll tackle the performance issue next.

    When to use it: Planning upcoming work

  76. I'll wrap up the testing by end of day.

    When to use it: Setting expectations

  77. I updated the environment variables for staging.

    When to use it: Sharing infrastructure work

  78. The build is green after my latest changes.

    When to use it: Reporting test status

  79. I'll demo the feature in sprint review.

    When to use it: Planning a presentation

  80. I'll update the Swagger docs after the API changes.

    When to use it: Planning documentation

  81. I completed the code review for the authentication PR.

    When to use it: Reporting review work

  82. I submitted the PR late yesterday and it still needs review.

    When to use it: Sharing PR status

  83. The QA team approved the feature for release.

    When to use it: Sharing good news

  84. I'll ping the team in Slack if I need help.

    When to use it: Communicating availability

  85. I had to increase the timeout on the API calls.

    When to use it: Explaining a fix

  86. I'm working through the backlog of bug reports.

    When to use it: Describing bug fix work

  87. I'll move the ticket to 'in review' now.

    When to use it: Updating board status

  88. I had to rebase my branch against main.

    When to use it: Describing git operations

  89. I'll take ownership of that ticket.

    When to use it: Volunteering for work

  90. I'm adding input validation to the form fields.

    When to use it: Describing validation work

  91. The hotfix was deployed to production last night.

    When to use it: Reporting deployment

  92. I'll handle the data migration over the weekend.

    When to use it: Planning weekend work

  93. The linter is flagging some style issues I need to fix.

    When to use it: Reporting linter issues

  94. I'll reach out to the stakeholders for feedback.

    When to use it: Planning communication

  95. I'm adding logging to help trace the issue.

    When to use it: Describing debugging approach

  96. I'm adding dark mode support to the settings page.

    When to use it: Describing UI feature

  97. I'll finish writing the unit tests this morning.

    When to use it: Setting a timeline

  98. I'll create a separate PR for the refactoring.

    When to use it: Organizing work

  99. I had a productive pairing session with the tech lead.

    When to use it: Sharing collaboration

  100. I'm updating the error messages to be more user-friendly.

    When to use it: Describing UX improvement

  101. I'll schedule a meeting with the architect to discuss the design.

    When to use it: Planning a meeting

  102. The automated tests caught a bug before it reached production.

    When to use it: Sharing positive outcome

  103. I'll tag the release after the final round of QA.

    When to use it: Planning release

  104. I fixed the broken import statement that was causing the build to fail.

    When to use it: Reporting a fix

  105. I'll add the loading spinner for better UX.

    When to use it: Describing UX work

  106. I finished setting up the staging environment.

    When to use it: Reporting setup completion

  107. I'll fix the failing snapshot tests today.

    When to use it: Planning test fixes

  108. I onboarded the new team member on our git workflow.

    When to use it: Describing mentoring

  109. I'll be focusing on tech debt reduction today.

    When to use it: Sharing today's focus

  110. I wrote a helper function to reduce code duplication.

    When to use it: Describing refactoring

  111. I'll coordinate with the mobile team on the API contract.

    When to use it: Planning collaboration

  112. I cleaned up the unused feature flags.

    When to use it: Reporting cleanup

  113. I'll share the technical design document for feedback.

    When to use it: Planning collaboration

  114. I'll follow up on the open questions from yesterday's design review.

    When to use it: Planning follow-up

  115. The database migration ran successfully in staging.

    When to use it: Reporting migration result

  116. I need someone to help me reproduce the issue on Windows.

    When to use it: Asking for help

  117. I'll create a runbook for the deployment process.

    When to use it: Planning documentation

  118. The code freeze starts tomorrow, so I'm wrapping up my changes.

    When to use it: Sharing timeline awareness

  119. I'll update the changelog before the release.

    When to use it: Planning release documentation

  120. I attended the incident retro yesterday afternoon.

    When to use it: Sharing what you did

  121. I'm reviewing the pull requests from the open source contributors.

    When to use it: Describing community work

  122. I triaged the incoming bug reports and prioritized them.

    When to use it: Reporting triage work

  123. I'll run the performance benchmarks after my changes.

    When to use it: Planning performance testing

  124. I need to bump the version number for the next release.

    When to use it: Describing release prep

  125. I debugged the issue and it turned out to be a null pointer exception.

    When to use it: Explaining root cause

  126. I'll clean up the temporary workarounds after the proper fix lands.

    When to use it: Planning cleanup

  127. I need to update the API documentation with the new endpoints.

    When to use it: Planning documentation

  128. I'll pair with the frontend team on the component library.

    When to use it: Planning collaboration

  129. I updated the README with the troubleshooting guide.

    When to use it: Reporting documentation work

  130. I reproduced the bug and I'm working on a fix.

    When to use it: Sharing debugging progress

  131. I'll update the CI config to include the new test suite.

    When to use it: Planning CI changes

  132. I'll be working from home today, but I'm fully available.

    When to use it: Sharing availability

  133. I enabled compression on the API responses.

    When to use it: Describing optimization

  134. I just picked up the highest priority bug from the backlog.

    When to use it: Sharing what you picked up

  135. I'll add smoke tests for the critical user flows.

    When to use it: Planning testing

  136. I'll verify the fix on staging before promoting to production.

    When to use it: Planning verification

  137. I'll share the retrospective action items with the team.

    When to use it: Planning communication

  138. I need help reviewing the database schema changes.

    When to use it: Asking for help

  139. I just deployed the new version of the mobile app to TestFlight.

    When to use it: Reporting deployment

  140. I replaced the hard-coded values with environment variables.

    When to use it: Describing config improvement

  141. I'll add the feature to the beta channel first.

    When to use it: Planning gradual rollout

  142. I updated the TypeScript types to match the new API response.

    When to use it: Describing type safety work

  143. I resolved the dependency vulnerability by bumping the package version.

    When to use it: Reporting security fix

  144. I cleaned up the dead code after the feature was deprecated.

    When to use it: Reporting cleanup

  145. I pinpointed the root cause — it was a missing null check.

    When to use it: Explaining root cause

  146. I need to look into why the nightly build keeps failing.

    When to use it: Identifying investigation

  147. I'll send a summary of my findings in Slack after standup.

    When to use it: Planning communication

  148. I'm done with my updates. Does anyone need help with anything?

    When to use it: Offering help at end of standup

  149. I'll refactor the tests to use the new test utilities.

    When to use it: Planning test improvement

  150. I need to discuss the rate limiting thresholds with the product owner.

    When to use it: Planning discussion

  151. I'll be offline for a couple of hours this afternoon for a dentist appointment.

    When to use it: Sharing availability

  152. I wrote a database seed script for the development environment.

    When to use it: Describing tooling

  153. I removed the console.log statements I left during debugging.

    When to use it: Reporting cleanup

  154. I need to add the CORS headers to allow cross-origin requests.

    When to use it: Identifying task

  155. I'm wrapping up the documentation for the new API version.

    When to use it: Describing documentation work

Intermediate phrases (90)

  1. I'm blocked on the payment integration because the third-party API is returning 500 errors.

    When to use it: Explaining a blocker with specific technical details

  2. I had to revert my last commit because it broke the build.

    When to use it: Explaining a rollback situation

  3. I've been investigating a memory leak in the service worker.

    When to use it: Reporting deep debugging work

  4. Could someone from the backend team help me with the GraphQL schema?

    When to use it: Requesting cross-team help

  5. I'm going to split this into smaller PRs to make it easier to review.

    When to use it: Explaining PR strategy

  6. I've been working on improving the test coverage for the authentication module.

    When to use it: Reporting testing efforts on a specific area

  7. I've been working on improving the test coverage for the payment module.

    When to use it: Reporting testing efforts on a specific area

  8. I've been working on improving the test coverage for the notification module.

    When to use it: Reporting testing efforts on a specific area

  9. I've been working on improving the test coverage for the search module.

    When to use it: Reporting testing efforts on a specific area

  10. I've been working on improving the test coverage for the analytics module.

    When to use it: Reporting testing efforts on a specific area

  11. I need to coordinate with the QA team before we can release this feature.

    When to use it: Explaining a dependency on QA

  12. I discovered that the issue is related to a race condition in the async handler.

    When to use it: Sharing a debugging discovery

  13. I noticed the staging environment is behaving differently from production.

    When to use it: Flagging an environment discrepancy

  14. I'll need to pair with someone on the infrastructure changes.

    When to use it: Requesting collaboration

  15. The feature flag is ready, so we can do a gradual rollout.

    When to use it: Explaining release strategy

  16. I'm going to add some logging to help us debug this issue in production.

    When to use it: Adding observability

  17. I realized we need to handle the edge case where the user has no internet connection.

    When to use it: Identifying a missing scenario

  18. I ran into a dependency conflict.

    When to use it: Reporting a blocker

  19. The code review took longer than expected.

    When to use it: Explaining time spent

  20. I found a regression in the latest build.

    When to use it: Reporting an issue

  21. I'm going to spike on the new payment provider.

    When to use it: Describing research work

  22. I need the product team to clarify the acceptance criteria.

    When to use it: Expressing a dependency

  23. I'm writing the migration script for the new table.

    When to use it: Describing database work

  24. I'm waiting on the DevOps team to provision the new server.

    When to use it: Reporting external dependency

  25. I need to add caching to improve the response time.

    When to use it: Identifying improvement

  26. I'm investigating why the webhook isn't firing.

    When to use it: Describing debugging work

  27. I'm setting up end-to-end tests for the checkout flow.

    When to use it: Describing testing work

  28. I'm implementing the search filters as per the latest designs.

    When to use it: Describing UI work

  29. I noticed some flaky tests in the CI pipeline.

    When to use it: Reporting CI issues

  30. I need to set up a feature flag for the new experiment.

    When to use it: Describing feature flag work

  31. I'll cherry-pick the fix to the release branch.

    When to use it: Describing git workflow

  32. I optimized the image loading to reduce bundle size.

    When to use it: Reporting optimization

  33. I completed the spike on the real-time notification system.

    When to use it: Reporting research results

  34. I'm going to shadow the on-call engineer today to learn the process.

    When to use it: Describing learning activity

  35. I fixed the CORS issue on the staging server.

    When to use it: Reporting a fix

  36. The API response time improved after the indexing changes.

    When to use it: Sharing performance results

  37. I need to update the SSL certificate before it expires.

    When to use it: Reporting urgent task

  38. I'll add retry logic to the failed API calls.

    When to use it: Describing resilience work

  39. I'm writing a script to automate the database seeding.

    When to use it: Describing automation

  40. I'm upgrading the Node version across all services.

    When to use it: Describing infrastructure work

  41. I'm configuring the new monitoring dashboard.

    When to use it: Describing observability work

  42. I had to roll back the feature toggle because of a bug.

    When to use it: Explaining a revert

  43. I set up the pre-commit hooks for the team.

    When to use it: Describing tooling work

  44. I'm extracting the shared logic into a reusable module.

    When to use it: Describing code reuse

  45. I'm looking into upgrading our authentication library.

    When to use it: Describing research

  46. I'm adding pagination to the list endpoint.

    When to use it: Describing API feature

  47. I added structured logging to the payment service.

    When to use it: Describing observability

  48. I'm containerizing the service with Docker.

    When to use it: Describing DevOps work

  49. I'm converting the callback-based code to async/await.

    When to use it: Describing modernization

  50. I'm working on the accessibility improvements for screen readers.

    When to use it: Describing accessibility work

  51. I submitted the security patch to the upstream repository.

    When to use it: Reporting open source work

  52. I verified that the rollback plan works correctly.

    When to use it: Reporting validation

  53. I'll write the postmortem document for the outage.

    When to use it: Planning documentation

  54. I'm adding health check endpoints to all our services.

    When to use it: Describing infrastructure work

  55. I configured alerts for when CPU usage exceeds eighty percent.

    When to use it: Describing monitoring

  56. I'm migrating the cron jobs to a task scheduler.

    When to use it: Describing infrastructure change

  57. I removed the deprecated API endpoints as planned.

    When to use it: Reporting cleanup

  58. I optimized the SQL queries to reduce the page load time.

    When to use it: Reporting optimization

  59. I'll set up the continuous deployment pipeline today.

    When to use it: Planning DevOps work

  60. I'm adding support for internationalization to the frontend.

    When to use it: Describing i18n work

  61. I'm refactoring the API to follow RESTful conventions.

    When to use it: Describing API improvement

  62. I'll create a shared library for the common utilities.

    When to use it: Planning code sharing

  63. I added database indexes to speed up the search queries.

    When to use it: Reporting optimization

  64. The security scan flagged a vulnerable dependency.

    When to use it: Reporting security issue

  65. I migrated the tests from Jest to Vitest.

    When to use it: Describing tooling migration

  66. I'm adding request validation middleware to the API.

    When to use it: Describing security work

  67. I cached the API responses to reduce latency.

    When to use it: Reporting optimization

  68. I added the error boundary to prevent the whole app from crashing.

    When to use it: Describing resilience

  69. I refactored the middleware chain for better readability.

    When to use it: Describing refactoring

  70. I set up the new Grafana dashboard for the backend metrics.

    When to use it: Describing observability

  71. I'm working on lazy loading the images to improve initial page load.

    When to use it: Describing performance work

  72. The load balancer configuration needs to be updated for the new instances.

    When to use it: Identifying a task

  73. I created a shared context for the authenticated user state.

    When to use it: Describing architecture work

  74. I'm working on the file upload feature with drag and drop.

    When to use it: Describing UI feature

  75. I'll add the cron job to clean up expired sessions.

    When to use it: Planning maintenance task

  76. I automated the release notes generation from commit messages.

    When to use it: Describing automation

  77. I need to add a retry queue for failed email deliveries.

    When to use it: Identifying a task

  78. I reduced the Docker image size by switching to Alpine.

    When to use it: Reporting optimization

  79. I adjusted the retry policy to be more aggressive during peak hours.

    When to use it: Describing configuration change

  80. The API gateway is now routing traffic correctly to the new service.

    When to use it: Reporting progress

  81. I'm building the admin dashboard for managing user accounts.

    When to use it: Describing feature work

  82. I'll set up the mock server for the frontend team to start working.

    When to use it: Enabling other team

  83. I'm adding the soft delete feature so we can recover deleted records.

    When to use it: Describing data safety

  84. I'm working on the GraphQL resolvers for the new entity.

    When to use it: Describing API work

  85. I configured the CDN to cache the static assets.

    When to use it: Describing infrastructure

  86. I rolled out the feature to ten percent of users for A/B testing.

    When to use it: Describing gradual rollout

  87. I standardized the error response format across all endpoints.

    When to use it: Describing API improvement

  88. I set up the integration tests with the real database.

    When to use it: Describing test infrastructure

  89. I'm setting up GitHub Actions for the automated deployments.

    When to use it: Describing CI/CD work

  90. I noticed the memory usage has been increasing steadily and I'll investigate.

    When to use it: Identifying investigation

Advanced phrases (35)

  1. I've been going down a rabbit hole trying to figure out why the WebSocket connection drops intermittently.

    When to use it: Describing a complex debugging situation

  2. I think we should consider breaking this monolith into microservices, but that's a bigger conversation.

    When to use it: Suggesting architectural change carefully

  3. The tech debt is starting to snowball — we might want to allocate a sprint for cleanup.

    When to use it: Advocating for tech debt time

  4. I'm leaning towards using a pub/sub pattern for this, but I'd like to get a second opinion before committing to the architecture.

    When to use it: Seeking consensus on a technical decision

  5. We might want to add a circuit breaker around this external service call to prevent cascading failures.

    When to use it: Suggesting a resilience pattern

  6. I'm refactoring the state management to use Redux.

    When to use it: Describing architecture change

  7. I'm implementing rate limiting on the public API.

    When to use it: Describing security work

  8. I resolved the timeout issue by implementing connection pooling.

    When to use it: Explaining a technical fix

  9. I'm investigating a spike in error rates since yesterday's deploy.

    When to use it: Describing incident investigation

  10. I fixed the race condition in the order processing pipeline.

    When to use it: Reporting a complex fix

  11. I'm splitting the monolithic service into smaller microservices.

    When to use it: Describing architecture work

  12. I need to update the API versioning strategy.

    When to use it: Describing API work

  13. I'm working on reducing the cold start time for our serverless functions.

    When to use it: Describing performance work

  14. I'll add the API key rotation mechanism today.

    When to use it: Describing security work

  15. I'm setting up the blue-green deployment strategy.

    When to use it: Describing deployment work

  16. I'm implementing the webhook retry mechanism with exponential backoff.

    When to use it: Describing resilience work

  17. I'll set up the canary deployment for the new version.

    When to use it: Planning deployment

  18. I updated the Terraform configuration for the new resources.

    When to use it: Describing IaC work

  19. I'm implementing the new OAuth flow for third-party integrations.

    When to use it: Describing auth work

  20. I'm adding two-factor authentication to the admin panel.

    When to use it: Describing security feature

  21. I fixed a memory leak in the image processing pipeline.

    When to use it: Reporting a fix

  22. I'm working on the data export feature for GDPR compliance.

    When to use it: Describing compliance work

  23. I'm implementing the event-driven architecture for the notification system.

    When to use it: Describing architecture work

  24. I'm handling the edge case where the session token expires mid-request.

    When to use it: Describing edge case handling

  25. I wrote a custom linter rule for our coding standards.

    When to use it: Describing tooling work

  26. I'm implementing server-side rendering for better SEO.

    When to use it: Describing SSR work

  27. I'm adding WebSocket support for real-time updates.

    When to use it: Describing feature work

  28. I'm implementing the GraphQL subscriptions for the chat feature.

    When to use it: Describing feature work

  29. I'm implementing the queue system for background jobs.

    When to use it: Describing backend work

  30. I'm setting up distributed tracing across our microservices.

    When to use it: Describing observability

  31. I'm adding the database connection pool to handle more concurrent requests.

    When to use it: Describing scalability work

  32. I added the OpenTelemetry instrumentation for better observability.

    When to use it: Describing observability work

  33. I'm looking into the failing health checks on the production pods.

    When to use it: Describing investigation

  34. I'm handling the graceful shutdown of the service.

    When to use it: Describing reliability work

  35. I'm implementing the circuit breaker pattern for the external API calls.

    When to use it: Describing resilience pattern

Other everyday developer situations

← English for developers

Guides with more context

Take it to your phone

In the Devlingo app you get 10 new phrases a day, each with real-world context, pronunciation and examples, and the widget shows the phrase of the day on your iPhone Home Screen.

Frequently asked questions

What people ask most about this, answered with the source.

What do you say in a daily standup?
Three short parts: Yesterday I finished…, Today I'm working on… and No blockers or I'm blocked on…. Keep it under a minute; details go to a thread after the call. More examples in what to say in a standup meeting.
How do you say you have no blockers?
No blockers on my end or Nothing blocking me right now. If there is one, I'm blocked on… followed by what you need and from whom.
DevlingoLearn tech phrases & speaking
Use without installingGet