1. hello@flicktype.groups.io
   Date   
Re: Upcoming pricing changes

Katie Epperson
 

What are your thoughts? I’ve never sold an app, but I can try to help

On Nov 20, 2018, at 3:20 PM, FlickType <@FlickType> 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
Re: Upcoming pricing changes

Liz and Hope
 

I know that a price needs to be economical for blind and visually impaired people to be able to afford this product. I think that $4.99 would be a reasonable fee for this keyboard. Whatever price you decide I will pay because our use FlickType 99% of the time at this point.
Liz Ulrich and leader Dog hope
HTTP://WWW.FACEBOOK.COM/ELIZABETH.ULRICH.1

On Nov 20, 2018, at 6:20 PM, FlickType <@FlickType> 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
Re: Upcoming pricing changes

leonard morris
 

You stated, "We have therefore decided to drop the subscription model moving forward, and instead introduce a one-off purchasing fee for the system-wide keyboard." Well, while the annual renewal subscription is relatively inexpensive how will I and others who elected for the annual pricing subscription option be impacted by the new pricing scheme whatever it happens to be determined by the developers?

On 11/20/2018 6:20 PM, FlickType 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

--
"Every country has an idenity, history, customs, and culture. It's a unique landscape in determining how its people live, work and play."
Re: Upcoming pricing changes

Christy S
 

Wow, that makes me wonder just what they consider an appropriate use of subscriptions? If there's one thing I don't like about apple, it's how controlling they are. Apparently, their communication with one another is a bit lacking, too.


Anyway, complaints aside, I'm curious what will happen for those of us who are already on subscription? Will we still have to pay whatever price? My personal thought for a price is perhaps $20. I don't know how sustainable that would be for you guys, though. I just know that many blind folks are sadly unemployed, so making a large one time purchase can be challenging.

On 11/20/2018 5:20 PM, FlickType 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
Upcoming pricing changes

FlickType
 
Edited

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 decision 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
Re: FlickType question or suggestion

Harry Bell
 

Ah, got it!
Thanks
Harry

On 20 Nov 2018, at 18:22, FlickType <@FlickType> wrote:

Hi Harry,

Thanks for the message. We recently made a change where you need to press and hold to show any of the action keys. Does this help?

Thanks!
Ashley

On Mon, Nov 19, 2018 at 10:57 PM, Harry Bell wrote:


I am using the latest app store version of FlickType on my iPad running the
latest beta of iOS 12.1.1 and the dismiss keyboard key does not show up
visually even though that setting is turned on in settings. I have restarted
the iPad but no change. VoiceOver does read out the next keyboard key but it
is invisible.
Re: FlickType question or suggestion

FlickType
 

Hi Harry,

Thanks for the message. We recently made a change where you need to press and hold to show any of the action keys. Does this help?

Thanks!
Ashley

On Mon, Nov 19, 2018 at 10:57 PM, Harry Bell wrote:


I am using the latest app store version of FlickType on my iPad running the
latest beta of iOS 12.1.1 and the dismiss keyboard key does not show up
visually even though that setting is turned on in settings. I have restarted
the iPad but no change. VoiceOver does read out the next keyboard key but it
is invisible.
FlickType question or suggestion

Harry Bell
 

I am using the latest app store version of FlickType on my iPad running the latest beta of iOS 12.1.1 and the dismiss keyboard key does not show up visually even though that setting is turned on in settings. I have restarted the iPad but no change. VoiceOver does read out the next keyboard key but it is invisible.
Thanks
Re: To upgrade from version 3.4 #206 to version 4.1 or not?

Alan Lemly
 

Kosta,

Thanks so much for the quick reply. I'm sure Theodore very much enjoys your dulcet tones and I know you enjoy singing to him.

I'll go ahead and update since the list below is quite extensive and I'm not using anything in my current version that's gone away from what you've described.

Enjoy your new son and thanks again for FlickType and how it makes typing fast and fun.

Alan

-----Original Message-----
From: hello@flicktype.groups.io [mailto:hello@flicktype.groups.io] On Behalf Of FlickType
Sent: Friday, November 16, 2018 11:38 AM
To: hello@flicktype.groups.io
Subject: Re: [FlickType] To upgrade from version 3.4 #206 to version 4.1 or not?

Hi Alan,

I have also been practicing my singing, and surprisingly it seems that Theodore likes it, smile.

With regards to upgrading, it's a fair question. You can always check the changelogs from the App Store, and we generally keep older versions on TestFlight that you can access using the "Previous Builds" option in case you need to revert for any reason. In any case, below are the changes from the two versions that have followed since 3.4, so you can decide if you want to upgrade.

- Kosta

4.1 Nov 14, 2018
� Improved behavior in numerical fields, such as currency fields in financial apps. Please let us know what you think!
� Added "Theodore" to the dictionary. My wife and I just had a new baby, and guess what we named him, smile :)

4.0 Nov 7, 2018
� Brand new Apple Watch companion app. You can now send messages straight from your watch!
� Performance improvements to make FlickType even more snappy.
� Updated instructions.
� Reduced memory usage.
� Dictionary improvements.
� Fixed some typing issues when using the half-screen mode.
� Removed "Minimal" size setting, and renamed "Half screen" to "Standard".
� Workaround for iOS bug where switching keyboards is impossible on text fields that expect numbers. FlickType will now dismiss the keyboard instead of attempting to switch to the next keyboard, since the latter would cause a freeze.
� Added announcement when changing keyboard layouts (numbers, uppercase, lowercase etc).
� Removed "Dismiss" key setting - the dismiss key will now automatically appear when in "Full screen" mode only.
� Replaced "Done" button in "Settings" tab with a "Dismiss" button that only appears when editing the emoji shortcuts.
� Renamed "Demo" tab to "Type".
� Other bug fixes.
Re: To upgrade from version 3.4 #206 to version 4.1 or not?

FlickType
 

Hi Alan,

I have also been practicing my singing, and surprisingly it seems that Theodore likes it, smile.

With regards to upgrading, it's a fair question. You can always check the changelogs from the App Store, and we generally keep older versions on TestFlight that you can access using the "Previous Builds" option in case you need to revert for any reason. In any case, below are the changes from the two versions that have followed since 3.4, so you can decide if you want to upgrade.

- Kosta

4.1 Nov 14, 2018
• Improved behavior in numerical fields, such as currency fields in financial apps. Please let us know what you think!
• Added "Theodore" to the dictionary. My wife and I just had a new baby, and guess what we named him, smile :)

4.0 Nov 7, 2018
• Brand new Apple Watch companion app. You can now send messages straight from your watch!
• Performance improvements to make FlickType even more snappy.
• Updated instructions.
• Reduced memory usage.
• Dictionary improvements.
• Fixed some typing issues when using the half-screen mode.
• Removed "Minimal" size setting, and renamed "Half screen" to "Standard".
• Workaround for iOS bug where switching keyboards is impossible on text fields that expect numbers. FlickType will now dismiss the keyboard instead of attempting to switch to the next keyboard, since the latter would cause a freeze.
• Added announcement when changing keyboard layouts (numbers, uppercase, lowercase etc).
• Removed "Dismiss" key setting - the dismiss key will now automatically appear when in "Full screen" mode only.
• Replaced "Done" button in "Settings" tab with a "Dismiss" button that only appears when editing the emoji shortcuts.
• Renamed "Demo" tab to "Type".
• Other bug fixes.
To upgrade from version 3.4 #206 to version 4.1 or not?

Alan Lemly
 

Hi Ashley and Kosta,

 

I hope Baby Theodore is settling in and letting you get some sleep. My first son was very colicky and I made it my task to walk him around and sing to him to calm him down. If I sang the theme to Gilligan's Island once, I must have sung it a thousand times. We won't dwell on whether it was helpful or made things worse.

 

I'm currently running version 3.4 #206 of the Flicktype Keyboard on my iPhone 8 with iOS 12.1. I'm not a fan of upgrading apps when they are doing what I need and I have to confess that I'm no longer downloading any Flicktype versions other than what's available from the Apps Store. I don't have an Apple Watch and I use the full screen version of the Flicktype Keyboard.

 

With the above in mind, can you comment whether the version 4.1 will offer me anything new without my giving up anything? I realize that one can't stay on old versions of apps forever but I've come to learn that timing one's upgrades can be beneficial.

 

Thanks for anything you can share.

 

Alan Lemly

Re: Dictionary question

Jean-Philippe Rykiel
 

hello Ashley,

thank you for your reply. The thing is, I don't see how this words Could have popped into the list As they are French words, and I am sure I did not write them inflict type at all. Nor did I add them manually in the text I was typing with flick type. The only thing that could have happened, is that I may have Started to write in French, and found that flick type was on, but then I immediately switched to the French keyboard. With that affect the dictionary?

That's intriguing isn't it.

Best regards,

JPR



http://jeanphilipperykiel.com
http://soundcloud.com/ryksounet
http://twitter.com/ryksounet
http://facebook.com/jeanphilipperykiel

Le 16/11/2018 à 03:27, FlickType a écrit :
Hi JP,

Thanks for the message. Yes, we look at all the words at the end of the typing session, and sometimes this may include pre-existing words (eg when you edit something). Is this an issue for you?

Thanks,
Ashley
Re: Dictionary question

FlickType
 

Hi JP,

Thanks for the message. Yes, we look at all the words at the end of the typing session, and sometimes this may include pre-existing words (eg when you edit something). Is this an issue for you?

Thanks,
Ashley
Re: Dictionary question

Jean-Philippe Rykiel
 

Hi all.
I am re-asking my question hoping someone can sort out this weird problem I’m having.
See message below please.
Thank you for your help if you can.
Cheers,
Jp

http://www.jprykiel.com

http://soundcloud.com/ryksounet
http://twitter.com/ryksounet
Http://www.facebook.com/jprykiel

Le 10 nov. 2018 à 11:53, Jean-Philippe Rykiel <jprykiel@...> a écrit :

Hi all.
A lot of words have been added to my FlickType dictionary, including French words I am sure I never typed within FlickType. Does anyone know how this can happen?
Cheers,
JPR

http://www.jprykiel.com

http://soundcloud.com/ryksounet
http://twitter.com/ryksounet
Http://www.facebook.com/jprykiel
FlickType on Product Hunt

FlickType
 

Dear friends,

We've just launched FlickType for Apple Watch on ProductHunt!
Join the discussion here: https://www.producthunt.com/posts/flicktype

Warmly,
Kosta and Ashley
Dictionary question

Jean-Philippe Rykiel
 

Hi all.
A lot of words have been added to my FlickType dictionary, including French words I am sure I never typed within FlickType. Does anyone know how this can happen?
Cheers,
JPR

http://www.jprykiel.com

http://soundcloud.com/ryksounet
http://twitter.com/ryksounet
Http://www.facebook.com/jprykiel
Re: Strange behaviour on web sites and Facebook

Jean-Philippe Rykiel
 

Well, its one of these bugs that cannot be reproduced I'm afraid. Everything works normally this morning. Go figure it out.
Cheers,
Jpr

http://www.jprykiel.com

http://soundcloud.com/ryksounet
http://twitter.com/ryksounet
Http://www.facebook.com/jprykiel

Le 10 nov. 2018 à 00:15, Jean-Philippe Rykiel <jprykiel@...> a écrit :

Hi Ashley. Thanks for your quick reply.
It happens when doing tap typing in Full screen mode. I haven’t tried half screen in this situation. Should I?
Best,
Jp

http://www.jprykiel.com

http://soundcloud.com/ryksounet
http://twitter.com/ryksounet
Http://www.facebook.com/jprykiel

Le 9 nov. 2018 à 22:29, FlickType <@FlickType> a écrit :

Hi JP,

Thanks for reporting and sorry to hear about this issue. Does it happen when you do manual typing or tap typing? What size keyboard are you using, full screen or half screen?

We'll try to get to the bottom of it.

Thanks!
Ashley
Re: Strange behaviour on web sites and Facebook

Jean-Philippe Rykiel
 

Hi Ashley. Thanks for your quick reply.
It happens when doing tap typing in Full screen mode. I haven’t tried half screen in this situation. Should I?
Best,
Jp

http://www.jprykiel.com

http://soundcloud.com/ryksounet
http://twitter.com/ryksounet
Http://www.facebook.com/jprykiel

Le 9 nov. 2018 à 22:29, FlickType <@FlickType> a écrit :

Hi JP,

Thanks for reporting and sorry to hear about this issue. Does it happen when you do manual typing or tap typing? What size keyboard are you using, full screen or half screen?

We'll try to get to the bottom of it.

Thanks!
Ashley
Re: 👶

George Cham
 

So you named him after one of the chipmunks☺️  

Kind Regards,

George Cham

‘May the Lord bless you and protect you. May the Lord smile on you and be gracious to you. May the Lord show you his favor and give you his peace.’
Numbers 6:24-26


Get Outlook for iOS
 

From: hello@flicktype.groups.io on behalf of FlickType <hello@...>
Sent: Saturday, November 10, 2018 8:24 am
To: hello@flicktype.groups.io
Subject: Re: [FlickType] 👶
 
Wow, thank you all, so much!! We had a boy, his name is Theodore ☺️

We're back online today, so if you're waiting to hear back from us, we'll get back to you soon. Kosta is working on a couple fixes that he will be sending out soon.

Thanks again for all the kind words!

Warmly,
Ashley and Kosta



Re: Strange behaviour on web sites and Facebook

FlickType
 

Hi JP,

Thanks for reporting and sorry to hear about this issue. Does it happen when you do manual typing or tap typing? What size keyboard are you using, full screen or half screen?

We'll try to get to the bottom of it.

Thanks!
Ashley