Topics

Build 95

Benny Barber
 

Kosta,
Sometimes having an issue when flicking through word options. Sometimes when flicking down through the word options, I will hear a click sound on the first flick down along with a single letter. I have to delete the letter, the incorrect word and start over. This has happened several times in this email. This is in the custom keyboard, build 95. Thanks..
Benny

On Jun 19, 2018, at 3:32 AM, FlickType <@FlickType> wrote:

- Set the actual launch price for the paid feature. We got you all worried there for a second, smile. Thank you for all your feedback on the pricing.
- TestFlight users are now automatically upgraded to always have the full custom keyboard functionality.
- Speculative fix for the crash that causes lost text. If the issue persists, please let us know what you were attempting to do at the precise moment the crash occurred, as well as the time that it occurred. Also a set of steps which reliably reproduce the issue would be incredibly helpful, as we have been unable to reproduce the issue so far.

Thank you for testing!

Warmly,
Kosta & Ashley


 

Thanks Benny.

Some gesture timing thresholds might have inadvertently changed a few builds back, ever so slightly.

Does it work better for you if you perform the flick gesture a bit faster? In other words, try to initiate the flick gesture before you even touch the screen. I think Chuck explained it better sometime ago.

If you are still having difficulties, or if other folks are having the same issue, we will try to restore the exact previous behavior.

Kosta

On Jun 19, 2018, at 11:58, Benny Barber <rebelben@...> wrote:

Kosta,
Sometimes having an issue when flicking through word options. Sometimes when flicking down through the word options, I will hear a click sound on the first flick down along with a single letter. I have to delete the letter, the incorrect word and start over. This has happened several times in this email. This is in the custom keyboard, build 95. Thanks..
Benny

On Jun 19, 2018, at 3:32 AM, FlickType <@FlickType> wrote:

- Set the actual launch price for the paid feature. We got you all worried there for a second, smile. Thank you for all your feedback on the pricing.
- TestFlight users are now automatically upgraded to always have the full custom keyboard functionality.
- Speculative fix for the crash that causes lost text. If the issue persists, please let us know what you were attempting to do at the precise moment the crash occurred, as well as the time that it occurred. Also a set of steps which reliably reproduce the issue would be incredibly helpful, as we have been unable to reproduce the issue so far.

Thank you for testing!

Warmly,
Kosta & Ashley




Benny Barber
 

Kosta,
I am trying to flick down faster, but it is still happening. Thanks.
Benny

On Jun 19, 2018, at 2:06 PM, FlickType <@FlickType> wrote:

Thanks Benny.

Some gesture timing thresholds might have inadvertently changed a few builds back, ever so slightly.

Does it work better for you if you perform the flick gesture a bit faster? In other words, try to initiate the flick gesture before you even touch the screen. I think Chuck explained it better sometime ago.

If you are still having difficulties, or if other folks are having the same issue, we will try to restore the exact previous behavior.

Kosta

On Jun 19, 2018, at 11:58, Benny Barber <rebelben@...> wrote:

Kosta,
Sometimes having an issue when flicking through word options. Sometimes when flicking down through the word options, I will hear a click sound on the first flick down along with a single letter. I have to delete the letter, the incorrect word and start over. This has happened several times in this email. This is in the custom keyboard, build 95. Thanks..
Benny

On Jun 19, 2018, at 3:32 AM, FlickType <@FlickType> wrote:

- Set the actual launch price for the paid feature. We got you all worried there for a second, smile. Thank you for all your feedback on the pricing.
- TestFlight users are now automatically upgraded to always have the full custom keyboard functionality.
- Speculative fix for the crash that causes lost text. If the issue persists, please let us know what you were attempting to do at the precise moment the crash occurred, as well as the time that it occurred. Also a set of steps which reliably reproduce the issue would be incredibly helpful, as we have been unable to reproduce the issue so far.

Thank you for testing!

Warmly,
Kosta & Ashley





Benny Barber
 

Kosta,
This is the first build that I have had this flicking problem. Thanks.

On Jun 19, 2018, at 3:32 AM, FlickType <@FlickType> wrote:

- Set the actual launch price for the paid feature. We got you all worried there for a second, smile. Thank you for all your feedback on the pricing.
- TestFlight users are now automatically upgraded to always have the full custom keyboard functionality.
- Speculative fix for the crash that causes lost text. If the issue persists, please let us know what you were attempting to do at the precise moment the crash occurred, as well as the time that it occurred. Also a set of steps which reliably reproduce the issue would be incredibly helpful, as we have been unable to reproduce the issue so far.

Thank you for testing!

Warmly,
Kosta & Ashley


David Nason
 

I think I have seen Benny's issue a couple of times, but had put it down to an error on my part.
Its very rare though.
Like Chuck, I don't honestly even notice if the sound is on the tap down or up.

Dave

On 19 Jun 2018, at 20:14, Benny Barber <rebelben@...> wrote:


Kosta,
I am trying to flick down faster, but it is still happening. Thanks.
Benny

On Jun 19, 2018, at 2:06 PM, FlickType <@FlickType> wrote:

Thanks Benny.

Some gesture timing thresholds might have inadvertently changed a few builds back, ever so slightly.

Does it work better for you if you perform the flick gesture a bit faster? In other words, try to initiate the flick gesture before you even touch the screen. I think Chuck explained it better sometime ago.

If you are still having difficulties, or if other folks are having the same issue, we will try to restore the exact previous behavior.

Kosta

On Jun 19, 2018, at 11:58, Benny Barber <rebelben@...> wrote:

Kosta,
Sometimes having an issue when flicking through word options. Sometimes when flicking down through the word options, I will hear a click sound on the first flick down along with a single letter. I have to delete the letter, the incorrect word and start over. This has happened several times in this email. This is in the custom keyboard, build 95. Thanks..
Benny

On Jun 19, 2018, at 3:32 AM, FlickType <@FlickType> wrote:

- Set the actual launch price for the paid feature. We got you all worried there for a second, smile. Thank you for all your feedback on the pricing.
- TestFlight users are now automatically upgraded to always have the full custom keyboard functionality.
- Speculative fix for the crash that causes lost text. If the issue persists, please let us know what you were attempting to do at the precise moment the crash occurred, as well as the time that it occurred. Also a set of steps which reliably reproduce the issue would be incredibly helpful, as we have been unable to reproduce the issue so far.

Thank you for testing!

Warmly,
Kosta & Ashley







 

Thanks.

Benny, could you please confirm if build 88 had the same issue? I know it’s a broken build that keeps popping us alerts, but if your issue happens very often, it should be easy to check and that would help a lot.

Kosta

On Jun 19, 2018, at 12:23, Benny Barber <rebelben@...> wrote:

Kosta,
This is the first build that I have had this flicking problem. Thanks.

On Jun 19, 2018, at 3:32 AM, FlickType <@FlickType> wrote:

- Set the actual launch price for the paid feature. We got you all worried there for a second, smile. Thank you for all your feedback on the pricing.
- TestFlight users are now automatically upgraded to always have the full custom keyboard functionality.
- Speculative fix for the crash that causes lost text. If the issue persists, please let us know what you were attempting to do at the precise moment the crash occurred, as well as the time that it occurred. Also a set of steps which reliably reproduce the issue would be incredibly helpful, as we have been unable to reproduce the issue so far.

Thank you for testing!

Warmly,
Kosta & Ashley




Benny Barber
 

David,
It happened about ten times on my last email. Thanks.
Benny

On Jun 19, 2018, at 2:24 PM, David Nason <dnason@...> wrote:


I think I have seen Benny's issue a couple of times, but had put it down to an error on my part.
Its very rare though.
Like Chuck, I don't honestly even notice if the sound is on the tap down or up.

Dave
On 19 Jun 2018, at 20:14, Benny Barber <rebelben@...> wrote:


Kosta,
I am trying to flick down faster, but it is still happening. Thanks.
Benny

On Jun 19, 2018, at 2:06 PM, FlickType <@FlickType> wrote:

Thanks Benny.

Some gesture timing thresholds might have inadvertently changed a few builds back, ever so slightly.

Does it work better for you if you perform the flick gesture a bit faster? In other words, try to initiate the flick gesture before you even touch the screen. I think Chuck explained it better sometime ago.

If you are still having difficulties, or if other folks are having the same issue, we will try to restore the exact previous behavior.

Kosta

On Jun 19, 2018, at 11:58, Benny Barber <rebelben@...> wrote:

Kosta,
Sometimes having an issue when flicking through word options. Sometimes when flicking down through the word options, I will hear a click sound on the first flick down along with a single letter. I have to delete the letter, the incorrect word and start over. This has happened several times in this email. This is in the custom keyboard, build 95. Thanks..
Benny

On Jun 19, 2018, at 3:32 AM, FlickType <@FlickType> wrote:

- Set the actual launch price for the paid feature. We got you all worried there for a second, smile. Thank you for all your feedback on the pricing.
- TestFlight users are now automatically upgraded to always have the full custom keyboard functionality.
- Speculative fix for the crash that causes lost text. If the issue persists, please let us know what you were attempting to do at the precise moment the crash occurred, as well as the time that it occurred. Also a set of steps which reliably reproduce the issue would be incredibly helpful, as we have been unable to reproduce the issue so far.

Thank you for testing!

Warmly,
Kosta & Ashley








Benny Barber
 

Kosta,
I did not get a chance to download 88. Should I try to do that and will that be a problem since I have downloaded 95? Thanks.
Benny

On Jun 19, 2018, at 2:31 PM, FlickType <@FlickType> wrote:

Thanks.

Benny, could you please confirm if build 88 had the same issue? I know it’s a broken build that keeps popping us alerts, but if your issue happens very often, it should be easy to check and that would help a lot.

Kosta

On Jun 19, 2018, at 12:23, Benny Barber <rebelben@...> wrote:

Kosta,
This is the first build that I have had this flicking problem. Thanks.

On Jun 19, 2018, at 3:32 AM, FlickType <@FlickType> wrote:

- Set the actual launch price for the paid feature. We got you all worried there for a second, smile. Thank you for all your feedback on the pricing.
- TestFlight users are now automatically upgraded to always have the full custom keyboard functionality.
- Speculative fix for the crash that causes lost text. If the issue persists, please let us know what you were attempting to do at the precise moment the crash occurred, as well as the time that it occurred. Also a set of steps which reliably reproduce the issue would be incredibly helpful, as we have been unable to reproduce the issue so far.

Thank you for testing!

Warmly,
Kosta & Ashley





Paul Sutton
 

Hi chuck,
I am also now able to type faster then I have ever typed in my life on my iPhone. Its just that I like to have things in sink when I touch the screen. Therefore I really do notice the slight delay.
In the grand scheme of things, a slight delay of the clicks isn't going to prevent me from using the app its just a preference that I would prefer..
Regards, paul.

On 19 Jun 2018, at 19:20, Chuck Dean <cadean329@...> wrote:


Hi Paul,
I am surprised this is still an issue. FlickType has me typing so fast I no longer notice it.
Chuck

On Jun 19, 2018, at 11:00 AM, Paul Sutton <sutty_p@...> wrote:

Hi, , all working well here. I just wondered if there may be an update on when the sounds will play on touch down rather than touch up?
Kind regards, paul
On 19 Jun 2018, at 09:32, FlickType <@FlickType> wrote:

- Set the actual launch price for the paid feature. We got you all worried there for a second, smile. Thank you for all your feedback on the pricing.
- TestFlight users are now automatically upgraded to always have the full custom keyboard functionality.
- Speculative fix for the crash that causes lost text. If the issue persists, please let us know what you were attempting to do at the precise moment the crash occurred, as well as the time that it occurred. Also a set of steps which reliably reproduce the issue would be incredibly helpful, as we have been unable to reproduce the issue so far.

Thank you for testing!

Warmly,
Kosta & Ashley




Benny Barber
 

Kosta,
I went back to build 88 and the flick problem was their as well. It was definitely not their in 85. It persists in 96. Thanks.
Benny

On Jun 19, 2018, at 2:31 PM, FlickType <@FlickType> wrote:

Thanks.

Benny, could you please confirm if build 88 had the same issue? I know it’s a broken build that keeps popping us alerts, but if your issue happens very often, it should be easy to check and that would help a lot.

Kosta

On Jun 19, 2018, at 12:23, Benny Barber <rebelben@...> wrote:

Kosta,
This is the first build that I have had this flicking problem. Thanks.

On Jun 19, 2018, at 3:32 AM, FlickType <@FlickType> wrote:

- Set the actual launch price for the paid feature. We got you all worried there for a second, smile. Thank you for all your feedback on the pricing.
- TestFlight users are now automatically upgraded to always have the full custom keyboard functionality.
- Speculative fix for the crash that causes lost text. If the issue persists, please let us know what you were attempting to do at the precise moment the crash occurred, as well as the time that it occurred. Also a set of steps which reliably reproduce the issue would be incredibly helpful, as we have been unable to reproduce the issue so far.

Thank you for testing!

Warmly,
Kosta & Ashley





Benny Barber
 

Kosta,
I meant to say that the flick problem was not in build 86. The problem started in build 95 and persists in 96. Thanks.
Benny

On Jun 19, 2018, at 2:31 PM, FlickType <@FlickType> wrote:

Thanks.

Benny, could you please confirm if build 88 had the same issue? I know it’s a broken build that keeps popping us alerts, but if your issue happens very often, it should be easy to check and that would help a lot.

Kosta

On Jun 19, 2018, at 12:23, Benny Barber <rebelben@...> wrote:

Kosta,
This is the first build that I have had this flicking problem. Thanks.

On Jun 19, 2018, at 3:32 AM, FlickType <@FlickType> wrote:

- Set the actual launch price for the paid feature. We got you all worried there for a second, smile. Thank you for all your feedback on the pricing.
- TestFlight users are now automatically upgraded to always have the full custom keyboard functionality.
- Speculative fix for the crash that causes lost text. If the issue persists, please let us know what you were attempting to do at the precise moment the crash occurred, as well as the time that it occurred. Also a set of steps which reliably reproduce the issue would be incredibly helpful, as we have been unable to reproduce the issue so far.

Thank you for testing!

Warmly,
Kosta & Ashley





 

Hi Benny, thanks for confirming. Could you please let us know if build 86 has the issue for you? We're trying to narrow it down between two successive builds that were released to alpha, so at from what you've reported it was either introduced with build 86, or build 88 if 86 does not have the issue. Also, what device and iOS version are you on? We might send a test build to you only as we are trying to figure this out.

- Kosta

 

Thanks Benny, although I'm a little confused. You also mentioned that build 88 had the problem as well, so that would be the earliest build that had the issue?

- Kosta

Salman Haider
 

My preference personally would be to have a one time purchase option, along with the tip jar option to allow for contribution from those who wish to support it on a consistent level, as well as those who wish to do it but without having to commit to a monthly contribution. I think that would be a good solution as it would give everyone the opportunity to contribute however much and however regularly they want. Plus, the developers would continue to get the support that they need/deserve. Again, just my opinion.

On Jun 19, 2018, at 2:27 PM, FlickType <@FlickType> wrote:

We will consider a one-off purchase option after we launch. On the sounds, there will definitely be an update that will at least offer the option to have sounds play on touch down, like in the classic app.

It should be evident that our normal feature development activity has slowed down significantly due to the purchasing structure that needs to be put in place. This has taken much longer than anticipated, but is a necessary step for the project to be successful and long-term. Also paid app reviews can be a long and tedious process, that is often slowed down by many things you wouldn't expect. Hopefully once the main structure is in place and the app has been approved by Apple, we can resume our regular rapid-fire schedule of feature updates for you all, smile.

Funny story: the last build we attempted to submit to the App Store got rejected for having a blank icon, with Apple telling us we need to have a more eye-catching graphic.

- Kosta

Benny Barber
 

Kosta,
Sorry for the confusion. I'm getting myself confused as well. The problem definitely started in 88. Thanks.
Benny

On Jun 19, 2018, at 5:56 PM, FlickType <@FlickType> wrote:

Thanks Benny, although I'm a little confused. You also mentioned that build 88 had the problem as well, so that would be the earliest build that had the issue?

- Kosta


Benny Barber
 

Using a5S with iOS 11.3. Thanks.

On Jun 19, 2018, at 5:56 PM, FlickType <@FlickType> wrote:

Thanks Benny, although I'm a little confused. You also mentioned that build 88 had the problem as well, so that would be the earliest build that had the issue?

- Kosta


 

Thank you Benny, build 88 is the suspect one on our end as well. While we're investigating, a couple things you could also try are updating to iOS 11.4, and trying the latest build on a different device if you happen to have one.

Thank you Salman for the pricing feedback. We will need to look into tip jar options and if those are allowed by Apple.

Kosta

Salman Haider
 

Thank you Kosta. I can confirm that the tip jar option is definitely allowed as I do use at least one app that has that feature. It gives great flexibility in terms of contribution. Whether it's a monthly, annual or a one time contribution. So definitely something that you guys can consider.
Thanks.

On Jun 19, 2018, at 7:33 PM, FlickType <@FlickType> wrote:

Thank you Benny, build 88 is the suspect one on our end as well. While we're investigating, a couple things you could also try are updating to iOS 11.4, and trying the latest build on a different device if you happen to have one.

Thank you Salman for the pricing feedback. We will need to look into tip jar options and if those are allowed by Apple.

Kosta

 

What is the app that has the tip jar feature, or what it the feature
itself called?

Kosta
On Tue, Jun 19, 2018 at 5:25 PM Salman Haider
<salmanhaider.purdue@...> wrote:

Thank you Kosta. I can confirm that the tip jar option is definitely allowed as I do use at least one app that has that feature. It gives great flexibility in terms of contribution. Whether it's a monthly, annual or a one time contribution. So definitely something that you guys can consider.
Thanks.

On Jun 19, 2018, at 7:33 PM, FlickType <@FlickType> wrote:

Thank you Benny, build 88 is the suspect one on our end as well. While we're investigating, a couple things you could also try are updating to iOS 11.4, and trying the latest build on a different device if you happen to have one.

Thank you Salman for the pricing feedback. We will need to look into tip jar options and if those are allowed by Apple.

Kosta





Ed Worrell
 

Hey kosta,

There are two apps that I use that include a "tip jar" feature.

Twitterific and Padometer++.

Ed

On Jun 19, 2018, at 10:33 PM, FlickType <@FlickType> wrote:

What is the app that has the tip jar feature, or what it the feature
itself called?

Kosta
On Tue, Jun 19, 2018 at 5:25 PM Salman Haider
<salmanhaider.purdue@...> wrote:

Thank you Kosta. I can confirm that the tip jar option is definitely allowed as I do use at least one app that has that feature. It gives great flexibility in terms of contribution. Whether it's a monthly, annual or a one time contribution. So definitely something that you guys can consider.
Thanks.

On Jun 19, 2018, at 7:33 PM, FlickType <@FlickType> wrote:

Thank you Benny, build 88 is the suspect one on our end as well. While we're investigating, a couple things you could also try are updating to iOS 11.4, and trying the latest build on a different device if you happen to have one.

Thank you Salman for the pricing feedback. We will need to look into tip jar options and if those are allowed by Apple.

Kosta