Date   

[FlickType] Paying for custom keyboard?

Chuck Dean
 


Hi Kosta, 
 Here is the email I eventually wrote with FTC. 
 Chuck 


Begin forwarded message:

From: "Chuck Dean" <cadean329@...>
Date: June 28, 2018 at 2:39:31 PM MST
To: hello@flicktype.groups.io
Subject: Re: [FlickType] Paying for custom keyboard?
Reply-To: hello@flicktype.groups.io

Hello,
When Fleksy first came out I paid nineteen dollars and ninety nine cents as a one time purchase price. Unfortunately, even this high purchase price did not generate enough revenue to sustain the app, so they released it to the general public.
In order to please the masses the developers had to make Fleksy appear more like a qwerty keyboard, which made Fleksy almost impossible for the visually impaired to operate.

As you can see, a one time purchase price will have to be very expensive to fund ongoing improvements, maintenance and other languages.

Ninety nine cents a month is surely affordable for anyone who owns an iPhone and will generate a steady revenue flow, so FlickType will not end up in the scrap heap like Fleksy.

Chuck

PS. Three and a half cents a day seems like a steal for a handful of magic.  😎

On Jun 28, 2018, at 12:19 PM, Chuck Dean <cadean329@...> wrote:

From the developer:

As we have a developing product that we will be making considerable updates
and improvements to, coupled with a small market, an ongoing subscription
model is the best way to ensure that the project is sustainable and will be
around for a long time. This, as well as the fact that we want to ensure
everyone is paying for what they’re using and not paying a one time
purchase for a product that they don't use a year or two down the road, we
feel that a subscription is best for everyone. That being said, things are
not set in stone as we are going to be fluid and adaptable to the
circumstances.

Please let us know if you have any other questions,
Ashley


Chuck
Pleez x cuze enny tie ping or spelin air ores.

Our 1972 Honda 600 Coupe <http://www.cadean.com/>       Our 1961 Vespa 400
<http://cadean.com/Vespa.html>




On Fri, Jun 22, 2018 at 6:41 AM, Jessica D <jldail13@...> wrote:

Hi,
I just opened FlickType and went to the upgrade tab.

I see that when it’s released, FlickType will require a monthly $0.99
subscription.

I don’t understand why this is.
Can you please explain why you feel this is necessary, & consider making
it a 1-time purchase?

A lot of us, myself included, have limited funding available, and can only
use iTunes cards to purchase items from the App Store and iTunes.
When paying for a subscription, that funding disappears very quickly.

Thanks for your understanding,
Jessica











Re: Build 114.

 

🙁

Since it happened twice while trying to type the same, or almost the same text, the text itself might be the best way to reproduce the problem. Would you be able to share with us the exact text you attempted to type? You could also send it to us privately if you wanted, instead of the list. Again, only if you're comfortable sharing it.

Thanks,
Kosta

- To join our beta, please send an email here
- Browse all our forum topics
Post to our forum
Join our forum
Help & support
- Follow us on Twitter





On Thu, Jun 28, 2018 at 3:31 PM Chuck Dean <cadean329@...> wrote:
Such is the burden we alpha testers must bear.

> On Jun 28, 2018, at 3:28 PM, FlickType <hello@...> wrote:
>
> Thank you Chuck, and really sorry for the huge inconvenience. This
> must be extremely frustrating. I am investigating and will keep you
> updated.
>
> Thanks for defending us, even in the face of such issues, smile.
>
> Kosta
>
>
>> On Thu, Jun 28, 2018 at 2:22 PM Chuck Dean <cadean329@...> wrote:
>>
>> Build 114. Losing text again!
>> Hi Kosta,
>> While typing a long email defending the ninety nine cent subscription for FlickType, the screen flashed three times, went red, and I lost half my text. This happened about two fourteen PDT
>>
>> I went back and started typing again, once I finished I changed to the iOS keyboard to see that what I just typed, wasn't there.
>>
>> I am using Classic to type this. Chuck
>>
>>
>>
>
>
>




Re: Build 114.

Chuck Dean
 

Such is the burden we alpha testers must bear.

On Jun 28, 2018, at 3:28 PM, FlickType <@FlickType> wrote:

Thank you Chuck, and really sorry for the huge inconvenience. This
must be extremely frustrating. I am investigating and will keep you
updated.

Thanks for defending us, even in the face of such issues, smile.

Kosta


On Thu, Jun 28, 2018 at 2:22 PM Chuck Dean <cadean329@...> wrote:

Build 114. Losing text again!
Hi Kosta,
While typing a long email defending the ninety nine cent subscription for FlickType, the screen flashed three times, went red, and I lost half my text. This happened about two fourteen PDT

I went back and started typing again, once I finished I changed to the iOS keyboard to see that what I just typed, wasn't there.

I am using Classic to type this. Chuck




Re: Build 114.

 

Thank you Chuck, and really sorry for the huge inconvenience. This
must be extremely frustrating. I am investigating and will keep you
updated.

Thanks for defending us, even in the face of such issues, smile.

Kosta

On Thu, Jun 28, 2018 at 2:22 PM Chuck Dean <cadean329@...> wrote:

Build 114. Losing text again!
Hi Kosta,
While typing a long email defending the ninety nine cent subscription for FlickType, the screen flashed three times, went red, and I lost half my text. This happened about two fourteen PDT

I went back and started typing again, once I finished I changed to the iOS keyboard to see that what I just typed, wasn't there.

I am using Classic to type this. Chuck



Build 114.

Chuck Dean
 

Build 114. Losing text again!
Hi Kosta,
While typing a long email defending the ninety nine cent subscription for FlickType, the screen flashed three times, went red, and I lost half my text. This happened about two fourteen PDT

I went back and started typing again, once I finished I changed to the iOS keyboard to see that what I just typed, wasn't there.

I am using Classic to type this. Chuck


Re: Contact email address?

Chuck Dean
 

Ok👌
That's what I thought.

On Jun 28, 2018, at 11:58 AM, FlickType <@FlickType> wrote:

Hi Chuck,

It's @FlickType

- Kosta

On Thu, Jun 28, 2018 at 11:54 AM Chuck Dean <cadean329@...> wrote:


Hello Ashley,
What is your contact email for the general public?

Thanks,
Chuck




Re: Contact email address?

 

Hi Chuck,

It's @FlickType

- Kosta

On Thu, Jun 28, 2018 at 11:54 AM Chuck Dean <cadean329@...> wrote:


Hello Ashley,
What is your contact email for the general public?

Thanks,
Chuck



Contact email address?

Chuck Dean
 

Hello Ashley,
What is your contact email for the general public?

Thanks,
Chuck


Re: Build 112

Dan Lococo
 

I like build 112 very much. The only issue I found is when I go to share
text, focus does not default to the first item on the share sheet.

Thanks for all you do.

Dan

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf
Of Salman Haider
Sent: Thursday, June 28, 2018 8:56 AM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 112

Everything is working well. No new issues.
Good job guys.
Salman

On Jun 28, 2018, at 12:19 AM, FlickType <@FlickType> wrote:

Just wanted to check in and see if anyone had any new issues with build 112.
It has a fix for a rare text loss issue but we want to make sure we didn't
break anything else in the process.

If you feel like you've used it long enough without issues please let us
know and we will push it to beta.

Thank you,
Kosta


Re: Build 112

Salman Haider
 

Everything is working well. No new issues.
Good job guys.
Salman

On Jun 28, 2018, at 12:19 AM, FlickType <@FlickType> wrote:

Just wanted to check in and see if anyone had any new issues with build 112. It has a fix for a rare text loss issue but we want to make sure we didn't break anything else in the process.

If you feel like you've used it long enough without issues please let us know and we will push it to beta.

Thank you,
Kosta


Re: Build 112

Chanelle Allen
 

There are no issues for me as well.
Thank you.
Chanelle

On Jun 28, 2018, at 04:20, Benny Barber <rebelben@...> wrote:

Thanks Chuck. Everything is working well right now.

Benny

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf
Of Chuck Dean
Sent: Wednesday, June 27, 2018 10:01 PM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 112

Hi Benny,
Open the Test flight App and install build 112.
Chuck

On Jun 27, 2018, at 7:34 PM, Benny Barber <rebelben@...> wrote:


Kosta,
I downloaded the FlickType app from the app store and it says my build is
110. somehow I have reverted to the earlier build. I camp fine a way to get
built 112 any suggestions? Thanks.
Benny

On Jun 27, 2018, at 4:09 PM, FlickType <@FlickType> wrote:

- Fixed rare lost text issue when adding text at the beginning of a
non-empty textfield. Thanks David!









Re: Build 112

Benny Barber
 

Thanks Chuck. Everything is working well right now.

Benny

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf
Of Chuck Dean
Sent: Wednesday, June 27, 2018 10:01 PM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 112

Hi Benny,
Open the Test flight App and install build 112.
Chuck

On Jun 27, 2018, at 7:34 PM, Benny Barber <rebelben@...> wrote:


Kosta,
I downloaded the FlickType app from the app store and it says my build is
110. somehow I have reverted to the earlier build. I camp fine a way to get
built 112 any suggestions? Thanks.
Benny

On Jun 27, 2018, at 4:09 PM, FlickType <@FlickType> wrote:

- Fixed rare lost text issue when adding text at the beginning of a
non-empty textfield. Thanks David!





Re: Build 112

Paul Sutton
 

All seems to be working from this end.😎

On 28 Jun 2018, at 05:20, FlickType <@FlickType> wrote:

Just wanted to check in and see if anyone had any new issues with build 112. It has a fix for a rare text loss issue but we want to make sure we didn't break anything else in the process.

If you feel like you've used it long enough without issues please let us know and we will push it to beta.

Thank you,
Kosta



Re: Build 112

Chuck Dean
 


All is good here.👍 
 Chuck 

On Jun 27, 2018, at 11:00 PM, David Nason <dnason@...> wrote:


Hi Kosta, 
 
 I haven't spotted any new issues. 
 
 Dave 
 


On 28 Jun 2018, at 05:22, George Cham <George.cham@...> wrote:

Hi costa,
No issues from my end👍

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: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of FlickType <hello@...>
Sent: Thursday, June 28, 2018 2:19:59 PM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 112
 
Just wanted to check in and see if anyone had any new issues with build 112. It has a fix for a rare text loss issue but we want to make sure we didn't break anything else in the process.

If you feel like you've used it long enough without issues please let us know and we will push it to beta.

Thank you,
Kosta




Re: Build 112

David Nason
 


Hi Kosta, 
 
 I haven't spotted any new issues. 
 
 Dave 
 


On 28 Jun 2018, at 05:22, George Cham <George.cham@...> wrote:

Hi costa,
No issues from my end👍

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: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of FlickType <hello@...>
Sent: Thursday, June 28, 2018 2:19:59 PM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 112
 
Just wanted to check in and see if anyone had any new issues with build 112. It has a fix for a rare text loss issue but we want to make sure we didn't break anything else in the process.

If you feel like you've used it long enough without issues please let us know and we will push it to beta.

Thank you,
Kosta




Re: Build 112

George Cham
 

Hi costa,
No issues from my end👍

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: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of FlickType <hello@...>
Sent: Thursday, June 28, 2018 2:19:59 PM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 112
 
Just wanted to check in and see if anyone had any new issues with build 112. It has a fix for a rare text loss issue but we want to make sure we didn't break anything else in the process.

If you feel like you've used it long enough without issues please let us know and we will push it to beta.

Thank you,
Kosta




Re: Build 112

 

Just wanted to check in and see if anyone had any new issues with build 112. It has a fix for a rare text loss issue but we want to make sure we didn't break anything else in the process.

If you feel like you've used it long enough without issues please let us know and we will push it to beta.

Thank you,
Kosta


Re: Build 112

Chuck Dean
 

Hi Benny,
Open the Test flight App and install build 112.
Chuck

On Jun 27, 2018, at 7:34 PM, Benny Barber <rebelben@...> wrote:


Kosta,
I downloaded the FlickType app from the app store and it says my build is 110. somehow I have reverted to the earlier build. I camp fine a way to get built 112 any suggestions? Thanks.
Benny

On Jun 27, 2018, at 4:09 PM, FlickType <@FlickType> wrote:

- Fixed rare lost text issue when adding text at the beginning of a non-empty textfield. Thanks David!





Re: Build 112

Benny Barber
 

Kosta,
I downloaded the FlickType app from the app store and it says my build is 110. somehow I have reverted to the earlier build. I camp fine a way to get built 112 any suggestions? Thanks.
Benny

On Jun 27, 2018, at 4:09 PM, FlickType <@FlickType> wrote:

- Fixed rare lost text issue when adding text at the beginning of a non-empty textfield. Thanks David!



Build 112

 

- Fixed rare lost text issue when adding text at the beginning of a non-empty textfield. Thanks David!