Skip to content
This repository has been archived by the owner on Mar 6, 2024. It is now read-only.

platform specific instructions added #182

Closed
wants to merge 2 commits into from
Closed

platform specific instructions added #182

wants to merge 2 commits into from

Conversation

Peddinti-Sriram-Bharadwaj

Description

Added new strings in E:\super_dash\lib\l10n\arb\app_en.arb and modified existing strings.

Earlier, the instructions were 'Tap/press space to start' irrespective of the platform. I modified the existing string 'tapToStart' that says 'Tap/press space to start' into 'Tap to start for the sake of iOs and Android platforms.' I added a new string 'pressSpaceToStart' that says 'Press space to start.' for the sake of desktop platforms.

These changes were made to improve the user experience on different platforms by providing clearer instructions.

Upon making changes, I thoroughly checked how the modified application works in the web browser, on Android, and on iOS.

I also ran 'flutter test --coverage --test-randomize-ordering-seed random', and the modified application passed all tests.

Type of Change

  • [x] ✨ New feature (non-breaking change which adds functionality)
  • 🛠️ Bug fix (non-breaking change which fixes an issue)
  • ❌ Breaking change (fix or feature that would cause existing functionality to change)
  • 🧹 Code refactor
  • ✅ Build configuration change
  • 📝 Documentation
  • 🗑️ Chore

Copy link

google-cla bot commented Dec 3, 2023

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.


bool get isAndroid => !kIsWeb && Platform.isAndroid;
bool get isIOS => !kIsWeb && Platform.isIOS;
bool get isWindows => !kIsWeb && Platform.isWindows;

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why add !kIsWeb in this condition?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

because it is possible that people open the app in browser but on a android or iOs or windows, opening the tab as in 'desktop view'. So, I believed that adding this condition would help.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I understood the fallacy in my logic. It must show 'tap to start' even if the app were to be opened in a smartphone weather it is browser or mobile app. I shall revise the logic again sir. Thank you for your review.

Shall I make the following changes and pull again?

  1. remove !kIsWeb in the boolean conditions
  2. remove options for windows and web, as they are not used in the logic.
  3. modify the text statement for other platforms to say 'tap/press Space to start' so that users can either tap or press space from a desktop platform.

@Peddinti-Sriram-Bharadwaj Peddinti-Sriram-Bharadwaj closed this by deleting the head repository Aug 10, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants