Thanks for confirming for me that they don't use the nub/tip any more. I genuinely count your positive experience. What I will do (once bitten, twice shy) is wait until at least another person says their ProPoint is awesome too.
I know I sound quite angry in the forums (when it comes to SwiftPoint). I assure you I did not use that tone with them. Here is the email I sent them, and their reply below.
I barely mentioned tilt gestures because when they did not work for me, I assumed it was "because I was a dummy" and not because of inherent hardware flaws. Now finding that others have issues with tilt as well, I regret spending all that time troubleshooting. If you have to ship a feature where the first thing the user has to do is disable it or reconfigure it, so that they don't have a terrible experience - maybe that wasn't a smart default. Vintage Apple developer guidelines tell programmers to make sensible defaults, so this isn't a new idea.
(sent June 27, 2017)
I own a SwiftPoint GT mouse, and mostly use it with my iPad (mini 3). In a few weeks I'll get an iPad Pro 12.9, and use it with that instead. I mainly use it with Jump Desktop to remote into my PC and get coding done.
I noticed that the Microsoft mice with BlueTrack have no need for a mouse pad at all - they are able to track on the shiny white tables that our workplace happens to have. Actually they track just about anywhere. Would you consider using similar technology in a future model of the SwiftPoint GT mouse? Then we simply wouldn't need any mouse pads, which would lead to a much nicer user experience.
Also, I have no need for touch gestures on an iPad, so it would be nice if I could configure the SwiftPoint GT to send, say, the 360° scroll events as found on the Apple TrackPads, Magic Mice, etc. I know that 360° doesn't really work on Windows (I know scrolling on Windows is a bag of hurt). But it would be nice because I could use that with a Mac, and maybe even over Jump Desktop.
Third, I was wondering if it would be possible to support multiple pairings. I know that might complicate things, but it could be like, power on = pairing 1, hold down left-click while powering on = pairing 2 (maybe blink the LED a certain way to confirm that), hold down right-click while powering on = pairing 3, hold down both while powering on = pairing 4, scroll forward while powering on = pairing 5, scroll backward while powering on = pairing 6.
Why 6 pairings? Coincidentally that is the number of pairings on my WayTools TextBlade. If it turns out after general release there is a market for that (I sure hope there is - my test unit is AWESOME), then there is likely a desire by the same crowd for an ultra-portable mouse. Bonus points if you can talk with the TextBlade and jump to the same device that it is switched to.
Just a few thoughts.
Thanks for making the SwiftPoint GT! It is because I use it, and want to use it in more places, that I thought of these suggestions. It is a great product as-is.
Their reply, July 22, 2017:
Thank for reaching out to us. My sincere apologies for the extremely delayed response. We're currently working through a huge amount of feedback regarding the recently released Swiftpoint Z and your query got a bit lost amongst it all.
Something similar to Microsofts Bluetrack could indeed be useful for the GT and will certainly be looked into should be revise or upgrade the GTs hardware.
How the GT's stylus is used on iOS is determined by the app it is used in. So if you have any suggestions for how you would like it to be implemented I can only suggest you reach out to Jump Desktop.
Currently the GT can only maintain two separate pairings, one over Bluetooth and the other with the USB receiver. Unfortunately I do not believe increasing this number would be possible with the GTs currently hardware, but again thank you for the suggestion.
Please let us know if you have any for feedback or queries regarding your GT.
Swiftpoint Support Team