You don’t have to cancel your subscription. If they discontinue the subscription model, your subscription will automatically go away. If they institute a new cost, you will have to authorize that specifically, they can’t just change the subscription so that you pay the new cost. So you really don’t have to do anything until you get some kind of notification from Apple or FlickType it’s self, and even in that case the worst that will happen is that the keyboard will just stop working and you will have to use the regular keyboard or dictation or whatever else you use when you’re not using FlickType.

Merry Christmas!

Luke

On Dec 22, 2019, at 12:32, Alexis Cooks via Groups.Io <alexiscooks_75=icloud.com@groups.io> wrote:

Hello everyone, I have a question. Does that mean I should cancel my subscription? When should I do so? that way I won’t have any unwanted charges. What I mean is I don’t want to pay if I don’t have to. I hope you know what I mean.

Thank you,
Lexi

On Dec 21, 2019, at 9:49 PM, Jessica Dail via Groups.Io <jldail13=icloud.com@groups.io> wrote:

Hi,
Can you please tell me what's going on with Flicktype?
Is it still being actively developed?

I see that the app store version hasn'tbeen updated in over a year, and this concerns me greatly.
I love the app, and would hate to see it go.

Thanks,
Jessica

On Nov 20, 2018, at 6:20 PM, FlickType <hello@flicktype.com> wrote:

Dear FlickType friends,

We have had numerous rejections of FlickType by Apple over the last few months, most often due to the uncommon nature of our app being a keyboard for VoiceOver users. Usually the reviewer is confused by the way they need to operate the keyboard with VoiceOver, and it takes some back-and-forth before they eventually reverse their devision and let us release our updates to the App Store.

This past weekend, our update got rejected because, quote, "the app uses auto-renewing subscriptions, but it is not an appropriate use of the service". This has happened before, and after our detailed explanation and position they agreed to reverse their decision at the time. It would seem that they have now either changed their policy, or this is a different person reviewing the app and for some reason they don't have the context of our earlier conversations. This is likely to happen again in the future, even if we succeed in getting the current update through.

Either way, App Store rejections and appeals to the App Review Board take a long time to resolve, time that we can better spend developing the app itself. We have therefore decided to drop the subscription model moving forward, and instead introduce a one-off purchasing fee for the system-wide keyboard, so that we at least eliminate one of the potential causes of App Store rejections and delays in the future.

We have not yet decided on the pricing, and in fact we'd love to hear some of your ideas on that. We are still hoping that we can find a price that is both reasonable for users, and also sustainable for us as a business. We also wanted to share this background information with you, and for you to be aware of the upcoming pricing changes.

Again, we welcome your thoughts in the matter, and we are thankful for all your support so far.

Warmly,
Kosta

On Dec 22, 2019, at 12:32, Alexis Cooks via Groups.Io <alexiscooks_75=icloud.com@groups.io> wrote:

Hello everyone, I have a question. Does that mean I should cancel my subscription? When should I do so? that way I won’t have any unwanted charges. What I mean is I don’t want to pay if I don’t have to. I hope you know what I mean.

Thank you,
Lexi

On Dec 21, 2019, at 9:49 PM, Jessica Dail via Groups.Io <jldail13=icloud.com@groups.io> wrote:

Hi,
Can you please tell me what's going on with Flicktype?
Is it still being actively developed?

I see that the app store version hasn'tbeen updated in over a year, and this concerns me greatly.
I love the app, and would hate to see it go.

Thanks,
Jessica

On Nov 20, 2018, at 6:20 PM, FlickType <hello@flicktype.com> wrote:

Dear FlickType friends,

We have had numerous rejections of FlickType by Apple over the last few months, most often due to the uncommon nature of our app being a keyboard for VoiceOver users. Usually the reviewer is confused by the way they need to operate the keyboard with VoiceOver, and it takes some back-and-forth before they eventually reverse their devision and let us release our updates to the App Store.

This past weekend, our update got rejected because, quote, "the app uses auto-renewing subscriptions, but it is not an appropriate use of the service". This has happened before, and after our detailed explanation and position they agreed to reverse their decision at the time. It would seem that they have now either changed their policy, or this is a different person reviewing the app and for some reason they don't have the context of our earlier conversations. This is likely to happen again in the future, even if we succeed in getting the current update through.

Either way, App Store rejections and appeals to the App Review Board take a long time to resolve, time that we can better spend developing the app itself. We have therefore decided to drop the subscription model moving forward, and instead introduce a one-off purchasing fee for the system-wide keyboard, so that we at least eliminate one of the potential causes of App Store rejections and delays in the future.

We have not yet decided on the pricing, and in fact we'd love to hear some of your ideas on that. We are still hoping that we can find a price that is both reasonable for users, and also sustainable for us as a business. We also wanted to share this background information with you, and for you to be aware of the upcoming pricing changes.

Again, we welcome your thoughts in the matter, and we are thankful for all your support so far.

Warmly,
Kosta

On Dec 21, 2019, at 9:49 PM, Jessica Dail via Groups.Io <jldail13=icloud.com@groups.io> wrote:

Hi,
Can you please tell me what's going on with Flicktype?
Is it still being actively developed?

I see that the app store version hasn'tbeen updated in over a year, and this concerns me greatly.
I love the app, and would hate to see it go.

Thanks,
Jessica

On Nov 20, 2018, at 6:20 PM, FlickType <hello@flicktype.com> wrote:

Dear FlickType friends,

We have had numerous rejections of FlickType by Apple over the last few months, most often due to the uncommon nature of our app being a keyboard for VoiceOver users. Usually the reviewer is confused by the way they need to operate the keyboard with VoiceOver, and it takes some back-and-forth before they eventually reverse their devision and let us release our updates to the App Store.

This past weekend, our update got rejected because, quote, "the app uses auto-renewing subscriptions, but it is not an appropriate use of the service". This has happened before, and after our detailed explanation and position they agreed to reverse their decision at the time. It would seem that they have now either changed their policy, or this is a different person reviewing the app and for some reason they don't have the context of our earlier conversations. This is likely to happen again in the future, even if we succeed in getting the current update through.

Either way, App Store rejections and appeals to the App Review Board take a long time to resolve, time that we can better spend developing the app itself. We have therefore decided to drop the subscription model moving forward, and instead introduce a one-off purchasing fee for the system-wide keyboard, so that we at least eliminate one of the potential causes of App Store rejections and delays in the future.

We have not yet decided on the pricing, and in fact we'd love to hear some of your ideas on that. We are still hoping that we can find a price that is both reasonable for users, and also sustainable for us as a business. We also wanted to share this background information with you, and for you to be aware of the upcoming pricing changes.

Again, we welcome your thoughts in the matter, and we are thankful for all your support so far.

Warmly,
Kosta

On Nov 20, 2018, at 6:20 PM, FlickType <hello@flicktype.com> wrote:

Dear FlickType friends,

We have had numerous rejections of FlickType by Apple over the last few months, most often due to the uncommon nature of our app being a keyboard for VoiceOver users. Usually the reviewer is confused by the way they need to operate the keyboard with VoiceOver, and it takes some back-and-forth before they eventually reverse their devision and let us release our updates to the App Store.

This past weekend, our update got rejected because, quote, "the app uses auto-renewing subscriptions, but it is not an appropriate use of the service". This has happened before, and after our detailed explanation and position they agreed to reverse their decision at the time. It would seem that they have now either changed their policy, or this is a different person reviewing the app and for some reason they don't have the context of our earlier conversations. This is likely to happen again in the future, even if we succeed in getting the current update through.

Either way, App Store rejections and appeals to the App Review Board take a long time to resolve, time that we can better spend developing the app itself. We have therefore decided to drop the subscription model moving forward, and instead introduce a one-off purchasing fee for the system-wide keyboard, so that we at least eliminate one of the potential causes of App Store rejections and delays in the future.

We have not yet decided on the pricing, and in fact we'd love to hear some of your ideas on that. We are still hoping that we can find a price that is both reasonable for users, and also sustainable for us as a business. We also wanted to share this background information with you, and for you to be aware of the upcoming pricing changes.

Again, we welcome your thoughts in the matter, and we are thankful for all your support so far.

Warmly,
Kosta

Paula and Luke,

I apologize if you've already stated this but have you gone to Settings,

Alan Lemly

Yeah I just deleted my dictionary. I wish we could select all and do in one sweep. But if you put some good music on you enjoy and get started, you can get
it done pretty fast.

Paula and Luke,

I apologize if you've already stated this but have you gone to Settings, General, Keyboard, Keyboards, FlickType and confirmed that allow full access is turned on? If yes, why not turn off full access, play around with keyboard input, and then turn FlickType's full access back on?

Alan Lemly

Hi, yes I have done all that, but my FlickType container app doesn’t open either. I think I am going to just delete it, I don’t wish to subscribe to something that isn’t going to work, and doesn’t seem to be being developed now. Thank you for your help though.

Paula

I just did some testing and the appearance is different on my iPhone 7 than it is on my 10R. On my 10R the dictate button is there on the bottom right side of the screen. However there is no dictate button on the 7 while flick type is the active keyboard. On the 10R, a double tap of the next keyboard button will cycle through all of my keyboards. However on the 7, I have to double tap and hold the next keyboard button and slide my finger up the side of the screen. As I make my way to the top it will announce different keyboards. So you just release your finger when you're on the one you want. So you want to try double tapping and holding the next keyboard button and sliding up to get the one you want to be active. But the next keyboard button is not there on the 7 when flick type is active. So I do a slide up to have flick type advance to the next keyboard.

On 12/19/2019 2:08 AM, Paula Page wrote:

I have had exactly the same problem, tried everything to sort it out, but I can’t seem to, so have given up with FlickType, sadly.
Paula

On 18 Dec 2019, at 21:30, Luke Davis <newanswertech@gmail.com> wrote:
After update to iOS 13.3, Flicktype still doesn't work system wide.
I removed and re-installed the app, and still it does not work.
I can change keyboard to imoji. After that, the next keyboard button says "Flicktype", but when I tap it, it just goes back to the English keyboard.
In fact, it still announces "next keyboard: flicktype", but if I actually read the button, it isn't Flicktype, but either Imoji or English.
And yet some of you are having success on iOS 13.3? What are your settings?
Luke

Chuck,

 

Thanks so much for telling me to give the container app time when opening it. I counted 30 Mississippi's before Voiceover began speaking. I guess I must have an extensive custom dictionary as well. Not surprising since FlickType is supposed to save any new words typed into it and I use it quite extensively.

 

Alan Lemly

 

From: hello@flicktype.groups.io [mailto:hello@flicktype.groups.io] On Behalf Of Chuck Dean
Sent: Thursday, December 19, 2019 11:25 AM
To: hello@flicktype.groups.io
Subject: Re: [FlickType] FlickType Container app not working on my iPhone 8

 

Hello again,

I just timed how long it took to open the FlickType container app. Once I double tapped on the icon, I got no response for 26 seconds.

 

This is because I have an extremely large dictionary. About every six months I clear out my dictionary and the loading time is much reduced.

 

Chuck  (mobile)

Pleez x cuze enny tie ping or spelin air ores.

 

Our 1972 Honda 600 Coupe

 

Our 1961 Vespa 400

On Dec 19, 2019, at 9:40 AM, Chuck Dean via Groups.Io <cadean329@...> wrote:

Hello Alan,

Hi Ellen,

How long did you play with the container app? When I open the container app it takeHi Ellen,

How long did you play with the container app? When I open the container app it takes almost 15 to 20 seconds before anything will happen. This is because I have an extremely large dictionary and it takes a long time to load. I remember Kosta found this almost unacceptable, but could not figure out how to shorten the time        

 

Chuck  (mobile)

Pleez x cuze enny tie ping or spelin air ores.

 

Our 1972 Honda 600 Coupe

 

Our 1961 Vespa 400

On Dec 19, 2019, at 8:24 AM, Alan Lemly <walemly@...> wrote:



Hi List,

 

I'm running iOS 13.3 on my iPhone 8 and in the process of looking into Luke's and Paula's issue, I attempted to open my FlickType Container app. When I did, my screen was totally frozen with Voiceover speaking nothing on the FlickType screen. Voiceover did speak the topline status bar but that was it. I removed FlickType from the Apps switcher and then opened the FlickType Classic app and got the same result. I then uninstalled the FlickType Classic app thinking it might be the problem since it predates the Container app but this caused no change. I also did a hard reset of my iPhone with no change in the Container app freeze. I'm hesitant to uninstall and reinstall the Container app since my FlickType Keyboard is working perfectly. Does anyone have any suggestions?

 

Alan Lemly

On Dec 19, 2019, at 9:40 AM, Chuck Dean via Groups.Io <cadean329@...> wrote:

Hello Alan,

Hi Ellen,

How long did you play with the container app? When I open the container app it takeHi Ellen,

How long did you play with the container app? When I open the container app it takes almost 15 to 20 seconds before anything will happen. This is because I have an extremely large dictionary and it takes a long time to load. I remember Kosta found this almost unacceptable, but could not figure out how to shorten the time        

Chuck  (mobile)

Pleez x cuze enny tie ping or spelin air ores.

Our 1972 Honda 600 Coupe

Our 1961 Vespa 400

On Dec 19, 2019, at 8:24 AM, Alan Lemly <walemly@...> wrote:



Hi List,

 

I'm running iOS 13.3 on my iPhone 8 and in the process of looking into Luke's and Paula's issue, I attempted to open my FlickType Container app. When I did, my screen was totally frozen with Voiceover speaking nothing on the FlickType screen. Voiceover did speak the topline status bar but that was it. I removed FlickType from the Apps switcher and then opened the FlickType Classic app and got the same result. I then uninstalled the FlickType Classic app thinking it might be the problem since it predates the Container app but this caused no change. I also did a hard reset of my iPhone with no change in the Container app freeze. I'm hesitant to uninstall and reinstall the Container app since my FlickType Keyboard is working perfectly. Does anyone have any suggestions?

 

Alan Lemly

On Dec 19, 2019, at 8:41 AM, Paula Page <fairyhugs@...> wrote:

Hi, yes I have done all that, but my FlickType container app doesn’t open either. I think I am going to just delete it, I don’t wish to subscribe to something that isn’t going to work, and doesn’t seem to be being developed now. Thank you for your help though.

Paula

On 19 Dec 2019, at 15:19, Alan Lemly <walemly@...> wrote:

Paula and Luke,

I apologize if you've already stated this but have you gone to Settings, General, Keyboard, Keyboards, FlickType and confirmed that allow full access is turned on? If yes, why not turn off full access, play around with keyboard input, and then turn FlickType's full access back on?   

Alan Lemly

-----Original Message-----

From: hello@flicktype.groups.io [mailto:hello@flicktype.groups.io] On Behalf Of Paula Page

Sent: Thursday, December 19, 2019 2:09 AM

To: hello@flicktype.groups.io

Subject: Re: [FlickType] iOS 13.3 and flicktype across the system

I have had exactly the same problem, tried everything to sort it out, but I can�t seem to, so have given up with FlickType, sadly.

Paula

On 18 Dec 2019, at 21:30, Luke Davis <newanswertech@...> wrote:

?After update to iOS 13.3, Flicktype still doesn't work system wide.

I removed and re-installed the app, and still it does not work.

I can change keyboard to imoji. After that, the next keyboard button says "Flicktype", but when I tap it, it just goes back to the English keyboard.

In fact, it still announces "next keyboard: flicktype", but if I actually read the button, it isn't Flicktype, but either Imoji or English.

And yet some of you are having success on iOS 13.3? What are your settings?

Luke

On Dec 19, 2019, at 8:24 AM, Alan Lemly <walemly@...> wrote:



Hi List,

 

I'm running iOS 13.3 on my iPhone 8 and in the process of looking into Luke's and Paula's issue, I attempted to open my FlickType Container app. When I did, my screen was totally frozen with Voiceover speaking nothing on the FlickType screen. Voiceover did speak the topline status bar but that was it. I removed FlickType from the Apps switcher and then opened the FlickType Classic app and got the same result. I then uninstalled the FlickType Classic app thinking it might be the problem since it predates the Container app but this caused no change. I also did a hard reset of my iPhone with no change in the Container app freeze. I'm hesitant to uninstall and reinstall the Container app since my FlickType Keyboard is working perfectly. Does anyone have any suggestions?

 

Alan Lemly

On 19 Dec 2019, at 15:19, Alan Lemly <walemly@gmail.com> wrote:

Paula and Luke,

I apologize if you've already stated this but have you gone to Settings, General, Keyboard, Keyboards, FlickType and confirmed that allow full access is turned on? If yes, why not turn off full access, play around with keyboard input, and then turn FlickType's full access back on?

Alan Lemly

-----Original Message-----
From: hello@flicktype.groups.io [mailto:hello@flicktype.groups.io] On Behalf Of Paula Page
Sent: Thursday, December 19, 2019 2:09 AM
To: hello@flicktype.groups.io
Subject: Re: [FlickType] iOS 13.3 and flicktype across the system

I have had exactly the same problem, tried everything to sort it out, but I can�t seem to, so have given up with FlickType, sadly.

Paula

On 18 Dec 2019, at 21:30, Luke Davis <newanswertech@gmail.com> wrote:

?After update to iOS 13.3, Flicktype still doesn't work system wide.

I removed and re-installed the app, and still it does not work.

I can change keyboard to imoji. After that, the next keyboard button says "Flicktype", but when I tap it, it just goes back to the English keyboard.
In fact, it still announces "next keyboard: flicktype", but if I actually read the button, it isn't Flicktype, but either Imoji or English.

And yet some of you are having success on iOS 13.3? What are your settings?

Luke