Date   

Re: Fliktype user list?

 

Thanks Chuck. Here's all the relevant addresses. Non-subscribers can
post, and their first post will be moderated:

Post: hello@flicktype.groups.io
Subscribe: hello+subscribe@flicktype.groups.io
Unsubscribe: hello+unsubscribe@flicktype.groups.io
Group Owner: hello+owner@flicktype.groups.io
Help: hello+help@flicktype.groups.io

- Kosta

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




Begin forwarded message:

From: Kimberly <kimbersinbox1963@...>
Date: June 28, 2018 at 6:39:43 PM MST
To: viphone@...
Subject: Re: Fliktype user list?
Reply-To: viphone@...


How do you subscribe?

Sent from Kimber's iPhone

The happy ending still beckons, and it is in the hope of grasping it that we go on.—Annie Proulx


On Jun 28, 2018, at 9:15 PM, Chuck Dean <chuckdean@...> wrote:

The list is
hello@flicktype.groups.io

and we'd love any suggestions
to make this the best place to discuss all things FlickType.

- Kosta

On Thursday, June 28, 2018 at 1:38:10 PM UTC-7, Kimber wrote:

Hi all,

Is there a fliktype users list? I'm finding I have a lot of questions
and don't want to clutter up this list.

Thankjs in advance.

--
Kimberly
--
The following information is important for all members of the V iPhone list.

If you have any questions or concerns about the running of this list, or if you feel that a member's post is inappropriate, please contact the owners or moderators directly rather than posting on the list itself.

Your V iPhone list moderator is Mark Taylor. Mark can be reached at: @markmarcus. Your list owner is Cara Quinn - you can reach Cara at caraquinn@...

The archives for this list can be searched at:
http://www.mail-archive.com/viphone@.../
---
You received this message because you are subscribed to the Google Groups "VIPhone" group.
To unsubscribe from this group and stop receiving emails from it, send an email to viphone+unsubscribe@....
To post to this group, send email to viphone@....
Visit this group at https://groups.google.com/group/viphone.
For more options, visit https://groups.google.com/d/optout.

--
The following information is important for all members of the V iPhone list.

If you have any questions or concerns about the running of this list, or if you feel that a member's post is inappropriate, please contact the owners or moderators directly rather than posting on the list itself.

Your V iPhone list moderator is Mark Taylor. Mark can be reached at: @markmarcus. Your list owner is Cara Quinn - you can reach Cara at caraquinn@...

The archives for this list can be searched at:
http://www.mail-archive.com/viphone@.../
---
You received this message because you are subscribed to a topic in the Google Groups "VIPhone" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/viphone/r0CV7YNv-fE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to viphone+unsubscribe@....
To post to this group, send email to viphone@....
Visit this group at https://groups.google.com/group/viphone.
For more options, visit https://groups.google.com/d/optout.


A fund for those who can not afford FlickType?

Chuck Dean
 

Hello everyone,
Although I find it hard to believe that someone who owns an iPhone couldn't afford to subscribe to FlickType, I was thinking of funding a project to aid those less fortunate.. Does anyone have any ideas how to verify someone is actually in need and not just trying to get a free ride?
Also, is it possible for me to pay for someone subscription?
Just spitballing.
Chuck


Re: Build 114.

Ed Worrell
 

Hey Kosta and Ashley, I agree. I love what you guys have done with the keyboard and will continue to support the project by both subscribing and beta testing as long as the testing period continues. I will always support developers that work with the visually impaired community as you guys pour your heart and sole into your apps. You guys need to eat too. So here's to a great job!👍🏻

Ed Worrell

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

Thank you so much Michael, that really means a lot.

We do not think the classic keyboard will cannibalize sales in any
meaningful way, since we believe the convenience to use the custom
keyboard in any app is hard to ignore, particularly for people who
would otherwise use the classic app repeatedly. Smile.

Kosta



On Thu, Jun 28, 2018 at 5:28 PM Michael Maslo <michaelmaslo04@...> wrote:

It is very disappointing the things which are said about the subscription model. I purchased the subscription and feel it is a well worth product. I could say more but I will stop here before I offend most people. If a one time charge is considered, I do hope it costs the same as a five year subscription. The issue is that there are no other keyboard out there which is so awesome for the blind. I know kosta you said the classic keyboard would always be out there but I wonder as for a business model if that may take business away from the custom keyboard. Anyway I want to sincerely thank you for making such a awesome keyboard. Keep up the great job.
On Jun 28, 2018, at 17:28, 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






Fliktype user list?

Chuck Dean
 




Begin forwarded message:

From: Kimberly <kimbersinbox1963@...>
Date: June 28, 2018 at 6:39:43 PM MST
To: viphone@...
Subject: Re: Fliktype user list?
Reply-To: viphone@...


How do you subscribe? 

Sent from Kimber's iPhone

The happy ending still beckons, and it is in the hope of grasping it that we go on.—Annie Proulx


On Jun 28, 2018, at 9:15 PM, Chuck Dean <chuckdean@...> wrote:

The list is

 and we'd love any suggestions
to make this the best place to discuss all things FlickType.

- Kosta

On Thursday, June 28, 2018 at 1:38:10 PM UTC-7, Kimber wrote:
Hi all,

Is there a fliktype users list? I'm finding I have a lot of questions
and don't want to clutter up this list.

Thankjs in advance.

--
Kimberly

--
The following information is important for all members of the V iPhone list.
 
If you have any questions or concerns about the running of this list, or if you feel that a member's post is inappropriate, please contact the owners or moderators directly rather than posting on the list itself.
 
Your V iPhone list moderator is Mark Taylor. Mark can be reached at: mktay@.... Your list owner is Cara Quinn - you can reach Cara at caraquinn@...
 
The archives for this list can be searched at:
http://www.mail-archive.com/viphone@.../
---
You received this message because you are subscribed to the Google Groups "VIPhone" group.
To unsubscribe from this group and stop receiving emails from it, send an email to viphone+unsubscribe@....
To post to this group, send email to viphone@....
Visit this group at https://groups.google.com/group/viphone.
For more options, visit https://groups.google.com/d/optout.

--
The following information is important for all members of the V iPhone list.
 
If you have any questions or concerns about the running of this list, or if you feel that a member's post is inappropriate, please contact the owners or moderators directly rather than posting on the list itself.
 
Your V iPhone list moderator is Mark Taylor. Mark can be reached at: mktay@.... Your list owner is Cara Quinn - you can reach Cara at caraquinn@...
 
The archives for this list can be searched at:
http://www.mail-archive.com/viphone@.../
---
You received this message because you are subscribed to a topic in the Google Groups "VIPhone" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/viphone/r0CV7YNv-fE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to viphone+unsubscribe@....
To post to this group, send email to viphone@....
Visit this group at https://groups.google.com/group/viphone.
For more options, visit https://groups.google.com/d/optout.


Re: Build 114 prediction not as good?

Chuck Dean
 


 Here is the sentence where I typed... On... And the first prediction was... Of.
The dwarf car museum was on my classic car so I sent the you tube on to the cars list.

I am not sure if both... On... Had the problem but I know the one after you tube was. 
 Chuck 
 

On Jun 28, 2018, at 6:23 PM, FlickType <hello@...> wrote:

Michael, Chuck and George, do you have any specific accuracy examples
you can reproduce and share? Chuck, you mentioned you tried to type
"on" and instead got the word "off", do you remember what the last two
words were in that context?

Also, have others noticed any similar change in accuracy?

Thanks,
Kosta

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

Hello,
I reverted back to the app store version. The difference is night and day.
I was getting frustrated with the constant wrong words so I went back to classic and all was well, so I figured it was the app and not my typing, so I went back.
Chuck

On Jun 28, 2018, at 6:01 PM, FlickType <hello@...> wrote:

Thank you both for the report. I don't see any changes on our end that could affect the accuracy between builds 110 and 114, but one can never be 100% certain. A good way to test this, now that you can get corrections after typing something manually, is to pick a word and then type it out manually but wrong in a deliberate and repeatable way. For example, to type Apple you might type something like S O O K R, and then see how far down in the suggestion you can find the original word. Also please note that the last two words or punctuation before the word you are correcting need to be identical if you are comparing between builds. Of course sometimes you can type the same letter but on a slightly different location of that letter's key, but on average over 4-5 different examples you should be able to know if there are any big differences.

Again, I don't see anything on our end that would result in lower accuracy, but it's obviously extremely important to avoid any such regressions so if you have any reproducible examples of how this differs between versions we'd love to know. And for me to reproduce anything I will need to also know the previous two words or punctuation, as well as the word in question.

Thank you,
Kosta



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


Hello everyone,
I reverted back to the app store version. The predictions are almost perfect. While typing this I haven't had to swipe down at all.
Chuck

On Jun 28, 2018, at 5:34 PM, George Cham <George.cham@...> wrote:

I'm having the same problem.
I typed in apple, but found that I had to swipe down several times

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

________________________________
From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Chuck Dean <cadean329@...>
Sent: Friday, June 29, 2018 10:28:14 AM
To: Alpha
Subject: [FlickType-alpha] Build 114 prediction not as good?

Build 114 prediction not as good?
Hello everyone,
Is it my imagination or is the predictions in build 114 a little off? It seems like I am having to swipe down a lot more than usual.
For example I went to type the word "on" end the first prediction was "of".

Anyone else having this problem?

Chuck








Re: Build 114 prediction not as good?

George Cham
 

Hi costa,,
I was typing apple, as I type, apple came up as the second suggestion after swiping gown.
It may be the way I'm typing and where I'm placing my finger. .
Because as I type, some of the words coming out the first time.

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: Friday, June 29, 2018 11:23:45 AM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 114 prediction not as good?
 
Michael, Chuck and George, do you have any specific accuracy examples
you can reproduce and share? Chuck, you mentioned you tried to type
"on" and instead got the word "off", do you remember what the last two
words were in that context?

Also, have others noticed any similar change in accuracy?

Thanks,
Kosta

On Thu, Jun 28, 2018 at 6:11 PM Chuck Dean <cadean329@...> wrote:
>
> Hello,
>  I reverted back to the app store version. The difference is night and day.
>  I was getting frustrated with the constant wrong words so I went back to classic and all was well, so I figured it was the app and not my typing, so I went back.
>  Chuck
>
> On Jun 28, 2018, at 6:01 PM, FlickType <hello@...> wrote:
>
> Thank you both for the report. I don't see any changes on our end that could affect the accuracy between builds 110 and 114, but one can never be 100% certain. A good way to test this, now that you can get corrections after typing something manually, is to pick a word and then type it out manually but wrong in a deliberate and repeatable way. For example, to type Apple you might type something like S O O K R, and then see how far down in the suggestion you can find the original word. Also please note that the last two words or punctuation before the word you are correcting need to be identical if you are comparing between builds. Of course sometimes you can type the same letter but on a slightly different location of that letter's key, but on average over 4-5 different examples you should be able to know if there are any big differences.
>
> Again, I don't see anything on our end that would result in lower accuracy, but it's obviously extremely important to avoid any such regressions so if you have any reproducible examples of how this differs between versions we'd love to know. And for me to reproduce anything I will need to also know the previous two words or punctuation, as well as the word in question.
>
> Thank you,
> Kosta
>
>
>
> On Thu, Jun 28, 2018 at 5:40 PM Chuck Dean <cadean329@...> wrote:
>>
>>
>>  Hello everyone,
>>  I reverted back to the app store version. The predictions are almost perfect. While typing this I haven't had to swipe down at all.
>>  Chuck
>>
>> On Jun 28, 2018, at 5:34 PM, George Cham <George.cham@...> wrote:
>>
>> I'm having the same problem.
>> I typed in apple, but found that I had to swipe down several times
>>
>> 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 Chuck Dean <cadean329@...>
>> Sent: Friday, June 29, 2018 10:28:14 AM
>> To: Alpha
>> Subject: [FlickType-alpha] Build 114 prediction not as good?
>>
>> Build 114 prediction not as good?
>> Hello everyone,
>> Is it my imagination or is the predictions in build 114 a little off? It seems like I am having to swipe down a lot more than usual.
>> For example I went to type the word "on" end the first prediction was "of".
>>
>> Anyone else having this problem?
>>
>> Chuck
>>
>>
>>
>




Re: Build 114.

 

Thank you so much Michael, that really means a lot.

We do not think the classic keyboard will cannibalize sales in any
meaningful way, since we believe the convenience to use the custom
keyboard in any app is hard to ignore, particularly for people who
would otherwise use the classic app repeatedly. Smile.

Kosta

On Thu, Jun 28, 2018 at 5:28 PM Michael Maslo <michaelmaslo04@...> wrote:

It is very disappointing the things which are said about the subscription model. I purchased the subscription and feel it is a well worth product. I could say more but I will stop here before I offend most people. If a one time charge is considered, I do hope it costs the same as a five year subscription. The issue is that there are no other keyboard out there which is so awesome for the blind. I know kosta you said the classic keyboard would always be out there but I wonder as for a business model if that may take business away from the custom keyboard. Anyway I want to sincerely thank you for making such a awesome keyboard. Keep up the great job.
On Jun 28, 2018, at 17:28, 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 prediction not as good?

 

Michael, Chuck and George, do you have any specific accuracy examples
you can reproduce and share? Chuck, you mentioned you tried to type
"on" and instead got the word "off", do you remember what the last two
words were in that context?

Also, have others noticed any similar change in accuracy?

Thanks,
Kosta

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

Hello,
I reverted back to the app store version. The difference is night and day.
I was getting frustrated with the constant wrong words so I went back to classic and all was well, so I figured it was the app and not my typing, so I went back.
Chuck

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

Thank you both for the report. I don't see any changes on our end that could affect the accuracy between builds 110 and 114, but one can never be 100% certain. A good way to test this, now that you can get corrections after typing something manually, is to pick a word and then type it out manually but wrong in a deliberate and repeatable way. For example, to type Apple you might type something like S O O K R, and then see how far down in the suggestion you can find the original word. Also please note that the last two words or punctuation before the word you are correcting need to be identical if you are comparing between builds. Of course sometimes you can type the same letter but on a slightly different location of that letter's key, but on average over 4-5 different examples you should be able to know if there are any big differences.

Again, I don't see anything on our end that would result in lower accuracy, but it's obviously extremely important to avoid any such regressions so if you have any reproducible examples of how this differs between versions we'd love to know. And for me to reproduce anything I will need to also know the previous two words or punctuation, as well as the word in question.

Thank you,
Kosta



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


Hello everyone,
I reverted back to the app store version. The predictions are almost perfect. While typing this I haven't had to swipe down at all.
Chuck

On Jun 28, 2018, at 5:34 PM, George Cham <George.cham@...> wrote:

I'm having the same problem.
I typed in apple, but found that I had to swipe down several times

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 Chuck Dean <cadean329@...>
Sent: Friday, June 29, 2018 10:28:14 AM
To: Alpha
Subject: [FlickType-alpha] Build 114 prediction not as good?

Build 114 prediction not as good?
Hello everyone,
Is it my imagination or is the predictions in build 114 a little off? It seems like I am having to swipe down a lot more than usual.
For example I went to type the word "on" end the first prediction was "of".

Anyone else having this problem?

Chuck



Re: Build 114 prediction not as good?

Chuck Dean
 

Hello, 
 I reverted back to the app store version. The difference is night and day. 
 I was getting frustrated with the constant wrong words so I went back to classic and all was well, so I figured it was the app and not my typing, so I went back. 
 Chuck 

On Jun 28, 2018, at 6:01 PM, FlickType <hello@...> wrote:

Thank you both for the report. I don't see any changes on our end that could affect the accuracy between builds 110 and 114, but one can never be 100% certain. A good way to test this, now that you can get corrections after typing something manually, is to pick a word and then type it out manually but wrong in a deliberate and repeatable way. For example, to type Apple you might type something like S O O K R, and then see how far down in the suggestion you can find the original word. Also please note that the last two words or punctuation before the word you are correcting need to be identical if you are comparing between builds. Of course sometimes you can type the same letter but on a slightly different location of that letter's key, but on average over 4-5 different examples you should be able to know if there are any big differences.

Again, I don't see anything on our end that would result in lower accuracy, but it's obviously extremely important to avoid any such regressions so if you have any reproducible examples of how this differs between versions we'd love to know. And for me to reproduce anything I will need to also know the previous two words or punctuation, as well as the word in question.

Thank you,
Kosta



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

 Hello everyone, 
 I reverted back to the app store version. The predictions are almost perfect. While typing this I haven't had to swipe down at all. 
 Chuck 

On Jun 28, 2018, at 5:34 PM, George Cham <George.cham@...> wrote:

I'm having the same problem.
I typed in apple, but found that I had to swipe down several times

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 Chuck Dean <cadean329@...>
Sent: Friday, June 29, 2018 10:28:14 AM
To: Alpha
Subject: [FlickType-alpha] Build 114 prediction not as good?
 
Build 114 prediction not as good?
Hello everyone,
Is it my imagination or is the predictions in build 114 a little off? It seems like I am having to swipe down a lot more than usual.
For example I went to type the word "on" end the first prediction was "of".

Anyone else having this problem?

Chuck




Re: They are asking for a group.

 

Thank you Chuck,

The list is hello@flicktype.groups.io, and we'd love any suggestions
to make this the best place to discuss all things FlickType.

- Kosta

PS: Ashley's mostly out today running some errands, and I'm covering
for her, smile.

- 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

http://flicktype.com

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


Hi Ashley,
On the ViPhone list people are asking for a discussion list for FlickType.
Is there one already, if so where can they join and post?
Chuck



Re: Build 114 prediction not as good?

 

Thank you both for the report. I don't see any changes on our end that could affect the accuracy between builds 110 and 114, but one can never be 100% certain. A good way to test this, now that you can get corrections after typing something manually, is to pick a word and then type it out manually but wrong in a deliberate and repeatable way. For example, to type Apple you might type something like S O O K R, and then see how far down in the suggestion you can find the original word. Also please note that the last two words or punctuation before the word you are correcting need to be identical if you are comparing between builds. Of course sometimes you can type the same letter but on a slightly different location of that letter's key, but on average over 4-5 different examples you should be able to know if there are any big differences.

Again, I don't see anything on our end that would result in lower accuracy, but it's obviously extremely important to avoid any such regressions so if you have any reproducible examples of how this differs between versions we'd love to know. And for me to reproduce anything I will need to also know the previous two words or punctuation, as well as the word in question.

Thank you,
Kosta



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

 Hello everyone, 
 I reverted back to the app store version. The predictions are almost perfect. While typing this I haven't had to swipe down at all. 
 Chuck 

On Jun 28, 2018, at 5:34 PM, George Cham <George.cham@...> wrote:

I'm having the same problem.
I typed in apple, but found that I had to swipe down several times

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 Chuck Dean <cadean329@...>
Sent: Friday, June 29, 2018 10:28:14 AM
To: Alpha
Subject: [FlickType-alpha] Build 114 prediction not as good?
 
Build 114 prediction not as good?
Hello everyone,
Is it my imagination or is the predictions in build 114 a little off? It seems like I am having to swipe down a lot more than usual.
For example I went to type the word "on" end the first prediction was "of".

Anyone else having this problem?

Chuck




They are asking for a group.

Chuck Dean
 

Hi Ashley,
On the ViPhone list people are asking for a discussion list for FlickType.
Is there one already, if so where can they join and post?
Chuck


Re: Build 114 prediction not as good?

Chuck Dean
 


 Hello everyone, 
 I reverted back to the app store version. The predictions are almost perfect. While typing this I haven't had to swipe down at all. 
 Chuck 

On Jun 28, 2018, at 5:34 PM, George Cham <George.cham@...> wrote:

I'm having the same problem.
I typed in apple, but found that I had to swipe down several times

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 Chuck Dean <cadean329@...>
Sent: Friday, June 29, 2018 10:28:14 AM
To: Alpha
Subject: [FlickType-alpha] Build 114 prediction not as good?
 
Build 114 prediction not as good?
Hello everyone,
Is it my imagination or is the predictions in build 114 a little off? It seems like I am having to swipe down a lot more than usual.
For example I went to type the word "on" end the first prediction was "of".

Anyone else having this problem?

Chuck




Re: Build 114 prediction not as good?

George Cham
 

I'm having the same problem.
I typed in apple, but found that I had to swipe down several times

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 Chuck Dean <cadean329@...>
Sent: Friday, June 29, 2018 10:28:14 AM
To: Alpha
Subject: [FlickType-alpha] Build 114 prediction not as good?
 
Build 114 prediction not as good?
Hello everyone,
Is it my imagination or is the predictions in build 114 a little off? It seems like I am having to swipe down a lot more than usual.
For example I went to type the word "on" end the first prediction was "of".

Anyone else having this problem?

Chuck




Re: Build 114 prediction not as good?

Chuck Dean
 

I am going to revert back to the app store version for comparison.
Chuck

On Jun 28, 2018, at 5:30 PM, Michael Maslo <michaelmaslo04@...> wrote:

Hey chuck, yes I have noticed the same. I thought it was me.
On Jun 28, 2018, at 19:28, Chuck Dean <cadean329@...> wrote:

Build 114 prediction not as good?
Hello everyone,
Is it my imagination or is the predictions in build 114 a little off? It seems like I am having to swipe down a lot more than usual.
For example I went to type the word "on" end the first prediction was "of".

Anyone else having this problem?

Chuck




Re: Build 114 prediction not as good?

Michael Maslo
 

Hey chuck, yes I have noticed the same. I thought it was me.

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

Build 114 prediction not as good?
Hello everyone,
Is it my imagination or is the predictions in build 114 a little off? It seems like I am having to swipe down a lot more than usual.
For example I went to type the word "on" end the first prediction was "of".

Anyone else having this problem?

Chuck



Build 114 prediction not as good?

Chuck Dean
 

Build 114 prediction not as good?
Hello everyone,
Is it my imagination or is the predictions in build 114 a little off? It seems like I am having to swipe down a lot more than usual.
For example I went to type the word "on" end the first prediction was "of".

Anyone else having this problem?

Chuck


Re: Build 114.

Michael Maslo
 

It is very disappointing the things which are said about the subscription model. I purchased the subscription and feel it is a well worth product. I could say more but I will stop here before I offend most people. If a one time charge is considered, I do hope it costs the same as a five year subscription. The issue is that there are no other keyboard out there which is so awesome for the blind. I know kosta you said the classic keyboard would always be out there but I wonder as for a business model if that may take business away from the custom keyboard. Anyway I want to sincerely thank you for making such a awesome keyboard. Keep up the great job.

On Jun 28, 2018, at 17:28, 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: [FlickType] Paying for custom keyboard?

Chuck Dean
 


Sorry, but my memory isn't that good. One thing that is different, I spelled out nineteen dollars and ninety nine cents in classic while in the custom keyboard I used $19.99 just because it is easier. 
 Chuck 

On Jun 28, 2018, at 4:32 PM, FlickType <hello@...> wrote:

Thank you Chuck, and your argument was nicely worded, smile.

I typed it out word for word twice and didn't lose any text, in the Mail app. A couple of things that come to mind:
- You mentioned that the first time, you lost half of your text but not all. Did you do anything special at that half text mark, such as switch or dismiss the keyboard?
- You said this is what you eventually wrote with Classic. Maybe there was a difference in the text that you typed with the custom keyboard? It's a long shot, and a long text, but if you can remember and arrive to steps to reproduce the problem, it will be as good as solved. And maybe it's something only in the later part of the text, the part that you lost, rather then the entire thing. In fact, if you only lost half because you toggled keyboards halfway through, it's almost certainly nothing to do with the text that you didn't lose.
- Some likely culprits could be the presence of new lines, manually capitalizing a common word, manual touch typing and emojis. I wonder if the actual lost text had any of those.
- Finally it could have been unrelated to the exact text. But twice in a row seems suspicious enough to me that I am almost certain there was something specific you repeated both times that caused the loss, and would cause the loss again if you were to repeat it.

I'm continuing to investigate.

Thanks,
Kosta


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

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: [FlickType] Paying for custom keyboard?

 

Thank you Chuck, and your argument was nicely worded, smile.

I typed it out word for word twice and didn't lose any text, in the Mail app. A couple of things that come to mind:
- You mentioned that the first time, you lost half of your text but not all. Did you do anything special at that half text mark, such as switch or dismiss the keyboard?
- You said this is what you eventually wrote with Classic. Maybe there was a difference in the text that you typed with the custom keyboard? It's a long shot, and a long text, but if you can remember and arrive to steps to reproduce the problem, it will be as good as solved. And maybe it's something only in the later part of the text, the part that you lost, rather then the entire thing. In fact, if you only lost half because you toggled keyboards halfway through, it's almost certainly nothing to do with the text that you didn't lose.
- Some likely culprits could be the presence of new lines, manually capitalizing a common word, manual touch typing and emojis. I wonder if the actual lost text had any of those.
- Finally it could have been unrelated to the exact text. But twice in a row seems suspicious enough to me that I am almost certain there was something specific you repeated both times that caused the loss, and would cause the loss again if you were to repeat it.

I'm continuing to investigate.

Thanks,
Kosta


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

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