Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added Haptic Feedback : Enhance User Experience #24

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

gokulnair2001
Copy link

So while using your pod I felt it was quiet amazing but the feature it was lacking behind was in terms of UX(User experience), To solve this I thought why not add an UX enhancing feature called "Haptic Feedback".

Added a Haptic Feedback generator code in the SHCircleBar.swift file and a method to call it in SHCircleBarController.swift.

This merge will not create any merge conflict as well as issue in your Pod, it will only enhance the user experience. Personally being a Developer I felt this feature was quite required in your app.

New Changes:
From now if the user clicks on any tab bar item they will get a feedback from the phone.

If any changes required, please inform me.

@perteraul perteraul requested a review from perteadrian February 2, 2021 11:37
Copy link
Collaborator

@perteadrian perteadrian left a comment

Choose a reason for hiding this comment

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

Thanks for your interest on helping this repository.
Adding haptic feedback is a great idea!
Since this is an open project, everyone who uses CircleBar, might not want to use haptic feedback in their apps, thus forcing it and not letting a decision on their side is not the best solution. Please add a boolean that is @IBInspactable to SHCircleBar, so that it would be easy for others to choose their preference.
Also, I saw that you added a new singleton (not really a singleton, since it has it's init() public) for the haptic feedback which is not used and also does not belong in any Xcode project (pod or example), it is just added to the root of the folder. Please delete that file if it is not used.
Thank you again for your contribution 😄

@gokulnair2001
Copy link
Author

Also, I saw that you added a new singleton (not really a singleton, since it has it's init() public) for the haptic feedback which is not used and also does not belong in any Xcode project (pod or example), it is just added to the root of the folder. Please delete that file if it is not used.

Hey Adrian,
Actually I didn't understood what you have mentioned above, I didn't added any file, if possible will you elaborate or add a screen shot of it.

And about the Haptic Feedback change I will surely change it and add an option for the user :)

@gokulnair2001
Copy link
Author

gokulnair2001 commented Feb 5, 2021

Required Changes done

  • So as you told I have added @IBInspactable to the code, so that now the user have the option to add haptic feed back, please check my implementation and let me know is there any correction required.
  • Still if any changes required, do tell me :).
  • And about my second commit regarding the UI changes, you didn't mentioned anything about it.

@gokulnair2001
Copy link
Author

Thanks for your interest on helping this repository.
Adding haptic feedback is a great idea!
Since this is an open project, everyone who uses CircleBar, might not want to use haptic feedback in their apps, thus forcing it and not letting a decision on their side is not the best solution. Please add a boolean that is @IBInspactable to SHCircleBar, so that it would be easy for others to choose their preference.
Also, I saw that you added a new singleton (not really a singleton, since it has it's init() public) for the haptic feedback which is not used and also does not belong in any Xcode project (pod or example), it is just added to the root of the folder. Please delete that file if it is not used.
Thank you again for your contribution 😄

I understood what you have mentioned regarding the file at root, actually at first I thought to create a new file, then realised why to create a new one, so after my second commit I have removed it, once you can clone my forked project to get an exact idea :).

The new file as shown in changes are not present now, you can see in my future commit changes.

@perteraul perteraul requested a review from perteadrian February 6, 2021 09:56
@perteadrian
Copy link
Collaborator

Hey, here's the screenshot showing that the folder has a new added file:
Screenshot 2021-02-08 at 16 31 51

@gokulnair2001
Copy link
Author

gokulnair2001 commented Feb 8, 2021 via email

@gokulnair2001
Copy link
Author

gokulnair2001 commented Feb 8, 2021 via email

@gokulnair2001
Copy link
Author

Final Changes

  • All the changes are done according to your standards , please do check and tell me if any further changes required.
  • The feature is working all fine.
  • Thank you for the immense help.

@gokulnair2001
Copy link
Author

@perteadrian I had made all changes as required, do have a look on it!

@perteadrian
Copy link
Collaborator

@gokulnair2001, thanks again for your interest in this library. Everything looks good so far. We will merge this when we release a new version on cocoapods also (~next week) :)

@gokulnair2001
Copy link
Author

Thank you so much for your constant support, though my contribution was small but I learned a lot in this journey.

Thank you @perteadrian @perteraul 😊

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants