|
Hi List, I’ve been following the various threads regarding removal of the FlickType keyboard from the App Store as well as those discussing the latest FlickType watch app and its operation on iOS 15. Before I update my iPhone SE 2020 to iOS 15 or consider purchasing a new iPhone, I want to understand this group’s consensus of FlickType availability going forward. I have not upgraded to the recently released FlickType Watch/Container app on my iPhone because the FlickType keyboard is working very well on my iPhone and the new update removes the keyboard. Also, I get better results with the FlickType keyboard than I do with the FlickType container app because punctuation is spoken when typing with the keyboard but not with the container app. My questions follow: - Does the group believe that the recently released FlickType Watch/Container app will continue to be available in the App Store for purchased new devices?
- Does the group believe that the container app will remain a component of the FlickType Watch app going forward?
- Has anyone upgraded to iOS 15 and can comment on FlickType’s performance with it whether using the FlickType keyboard or the FlickType Watch/Container app either recently updated or not?
I have tried using the iOS on screen keyboard in slide to type mode and will confess with the expletives omitted that I don’t consider it a viable option going forward. I certainly don’t mind using the FlickType container app going forward since this was the method used with both the original Fleksy and FlickType and I can type, copy, and paste and get results more than twice as fast as typing on the on screen keyboard. Thanks in advance for your comments. Alan Lemly
|
|
|
Hello Alan, Here is an exchange I had with Kosta last week: From Kosta: My plan has always been to keep and maintain the container keyboard so as to provide the full functionality of FlickType Classic with a share button to export text. I've been trying to get an update out since August 11 but Apple has been dragging their feet, so I'm not quite sure when this will be out. my reply: The update showed up in the App Store this morning. From Kosta: Thank you for letting me know. Unfortunately, Apple approved the wrong version - but at least this should have the share button. Since it's not the version I intended to release, I have paused the update so that existing users won't automatically get it. Kosta Chuck
Pleez x cuze enny tie ping or spelin air ores.
On Sat, Sep 25, 2021 at 9:39 AM Alan Lemly < walemly@...> wrote: Hi List, I’ve been following the various threads regarding removal of the FlickType keyboard from the App Store as well as those discussing the latest FlickType watch app and its operation on iOS 15. Before I update my iPhone SE 2020 to iOS 15 or consider purchasing a new iPhone, I want to understand this group’s consensus of FlickType availability going forward. I have not upgraded to the recently released FlickType Watch/Container app on my iPhone because the FlickType keyboard is working very well on my iPhone and the new update removes the keyboard. Also, I get better results with the FlickType keyboard than I do with the FlickType container app because punctuation is spoken when typing with the keyboard but not with the container app. My questions follow: - Does the group believe that the recently released FlickType Watch/Container app will continue to be available in the App Store for purchased new devices?
- Does the group believe that the container app will remain a component of the FlickType Watch app going forward?
- Has anyone upgraded to iOS 15 and can comment on FlickType’s performance with it whether using the FlickType keyboard or the FlickType Watch/Container app either recently updated or not?
I have tried using the iOS on screen keyboard in slide to type mode and will confess with the expletives omitted that I don’t consider it a viable option going forward. I certainly don’t mind using the FlickType container app going forward since this was the method used with both the original Fleksy and FlickType and I can type, copy, and paste and get results more than twice as fast as typing on the on screen keyboard. Thanks in advance for your comments. Alan Lemly
|
|
|
Hi Chuck, Thanks for sharing your exchange with Kosta. This is very encouraging because unless I’m misreading something, he intends for the container app to remain in the App Store. I assume it will continue as part of the FlickType watch app as it was with the last update. I hope his dispute with Apple over their latest watch and its quick path functionality doesn’t torpedo access to the container app in the future. I can type so much faster having access to FlickType and it would be a shame to lose it. Alan
From: hello@flicktype.groups.io <hello@flicktype.groups.io> On Behalf Of Chuck Dean Sent: Saturday, September 25, 2021 1:41 PM To: hello@flicktype.groups.io Subject: Re: [FlickType] Need to confirm my understanding of FlickType container availability in iOS 15 and on new iDevices Hello Alan,
Here is an exchange I had with Kosta last week:
From Kosta:
My plan has always been to keep and maintain the container keyboard so
as to provide the full functionality of FlickType Classic with a share
button to export text.
I've been trying to get an update out since August 11 but Apple has
been dragging their feet, so I'm not quite sure when this will be out.
my reply:
The update showed up in the App Store this morning.
From Kosta:
Thank you for letting me know.
Unfortunately, Apple approved the wrong version - but at least this
should have the share button.
Since it's not the version I intended to release, I have paused the
update so that existing users won't automatically get it.
Kosta Pleez x cuze enny tie ping or spelin air ores. On Sat, Sep 25, 2021 at 9:39 AM Alan Lemly <walemly@...> wrote: Hi List, I’ve been following the various threads regarding removal of the FlickType keyboard from the App Store as well as those discussing the latest FlickType watch app and its operation on iOS 15. Before I update my iPhone SE 2020 to iOS 15 or consider purchasing a new iPhone, I want to understand this group’s consensus of FlickType availability going forward. I have not upgraded to the recently released FlickType Watch/Container app on my iPhone because the FlickType keyboard is working very well on my iPhone and the new update removes the keyboard. Also, I get better results with the FlickType keyboard than I do with the FlickType container app because punctuation is spoken when typing with the keyboard but not with the container app. My questions follow: - Does the group believe that the recently released FlickType Watch/Container app will continue to be available in the App Store for purchased new devices?
- Does the group believe that the container app will remain a component of the FlickType Watch app going forward?
- Has anyone upgraded to iOS 15 and can comment on FlickType’s performance with it whether using the FlickType keyboard or the FlickType Watch/Container app either recently updated or not?
I have tried using the iOS on screen keyboard in slide to type mode and will confess with the expletives omitted that I don’t consider it a viable option going forward. I certainly don’t mind using the FlickType container app going forward since this was the method used with both the original Fleksy and FlickType and I can type, copy, and paste and get results more than twice as fast as typing on the on screen keyboard. Thanks in advance for your comments. Alan Lemly
|
|
|
Hello Alan, Yes, it has always been Kosta's intention to keep an accessible version of FlickType in the app store.
BTW: when you are typing in the container app and you flick right to insert a period, the container app will repeat the last word you typed, instead of saying period, but it does insert the period. If you flick down you will hear. Comma, question mark, etc. And when you flick back up you will hear comma, period. This is a little glitch that will be fixed in the future. Chuck (mobile) Pleez x cuze enny tie ping or spelin air ores.
On Sep 25, 2021, at 8:58 PM, Alan Lemly <walemly@...> wrote:
Hi Chuck, Thanks for sharing your exchange with Kosta. This is very encouraging because unless I’m misreading something, he intends for the container app to remain in the App Store. I assume it will continue as part of the FlickType watch app as it was with the last update. I hope his dispute with Apple over their latest watch and its quick path functionality doesn’t torpedo access to the container app in the future. I can type so much faster having access to FlickType and it would be a shame to lose it. Alan From: hello@flicktype.groups.io <hello@flicktype.groups.io> On Behalf Of Chuck Dean
Sent: Saturday, September 25, 2021 1:41 PM
To: hello@flicktype.groups.io
Subject: Re: [FlickType] Need to confirm my understanding of FlickType container availability in iOS 15 and on new iDevices Hello Alan,
Here is an exchange I had with Kosta last week:
From Kosta:
My plan has always been to keep and maintain the container keyboard so
as to provide the full functionality of FlickType Classic with a share
button to export text.
I've been trying to get an update out since August 11 but Apple has
been dragging their feet, so I'm not quite sure when this will be out.
my reply:
The update showed up in the App Store this morning.
From Kosta:
Thank you for letting me know.
Unfortunately, Apple approved the wrong version - but at least this
should have the share button.
Since it's not the version I intended to release, I have paused the
update so that existing users won't automatically get it.
Kosta Pleez x cuze enny tie ping or spelin air ores. On Sat, Sep 25, 2021 at 9:39 AM Alan Lemly <walemly@...> wrote: Hi List, I’ve been following the various threads regarding removal of the FlickType keyboard from the App Store as well as those discussing the latest FlickType watch app and its operation on iOS 15. Before I update my iPhone SE 2020 to iOS 15 or consider purchasing a new iPhone, I want to understand this group’s consensus of FlickType availability going forward. I have not upgraded to the recently released FlickType Watch/Container app on my iPhone because the FlickType keyboard is working very well on my iPhone and the new update removes the keyboard. Also, I get better results with the FlickType keyboard than I do with the FlickType container app because punctuation is spoken when typing with the keyboard but not with the container app. My questions follow: - Does the group believe that the recently released FlickType Watch/Container app will continue to be available in the App Store for purchased new devices?
- Does the group believe that the container app will remain a component of the FlickType Watch app going forward?
- Has anyone upgraded to iOS 15 and can comment on FlickType’s performance with it whether using the FlickType keyboard or the FlickType Watch/Container app either recently updated or not?
I have tried using the iOS on screen keyboard in slide to type mode and will confess with the expletives omitted that I don’t consider it a viable option going forward. I certainly don’t mind using the FlickType container app going forward since this was the method used with both the original Fleksy and FlickType and I can type, copy, and paste and get results more than twice as fast as typing on the on screen keyboard. Thanks in advance for your comments. Alan Lemly
|
|
|
Chuck, That’s good to know and I’ll get used to typing with the container app again. Keeping it running in the app switcher will enable me to type about as quickly as I can with the FlickType keyboard in full screen mode. And thanks for recapping how the punctuation is currently handled. Alan
From: hello@flicktype.groups.io <hello@flicktype.groups.io> On Behalf Of Chuck Dean Sent: Saturday, September 25, 2021 11:28 PM To: hello@flicktype.groups.io Subject: Re: [FlickType] Need to confirm my understanding of FlickType container availability in iOS 15 and on new iDevices Yes, it has always been Kosta's intention to keep an accessible version of FlickType in the app store. BTW: when you are typing in the container app and you flick right to insert a period, the container app will repeat the last word you typed, instead of saying period, but it does insert the period. If you flick down you will hear. Comma, question mark, etc. And when you flick back up you will hear comma, period. This is a little glitch that will be fixed in the future. Pleez x cuze enny tie ping or spelin air ores.
On Sep 25, 2021, at 8:58 PM, Alan Lemly <walemly@...> wrote:
Hi Chuck, Thanks for sharing your exchange with Kosta. This is very encouraging because unless I’m misreading something, he intends for the container app to remain in the App Store. I assume it will continue as part of the FlickType watch app as it was with the last update. I hope his dispute with Apple over their latest watch and its quick path functionality doesn’t torpedo access to the container app in the future. I can type so much faster having access to FlickType and it would be a shame to lose it. Alan Hello Alan,
Here is an exchange I had with Kosta last week:
From Kosta:
My plan has always been to keep and maintain the container keyboard so
as to provide the full functionality of FlickType Classic with a share
button to export text.
I've been trying to get an update out since August 11 but Apple has
been dragging their feet, so I'm not quite sure when this will be out.
my reply:
The update showed up in the App Store this morning.
From Kosta:
Thank you for letting me know.
Unfortunately, Apple approved the wrong version - but at least this
should have the share button.
Since it's not the version I intended to release, I have paused the
update so that existing users won't automatically get it.
Kosta Pleez x cuze enny tie ping or spelin air ores. On Sat, Sep 25, 2021 at 9:39 AM Alan Lemly <walemly@...> wrote: Hi List, I’ve been following the various threads regarding removal of the FlickType keyboard from the App Store as well as those discussing the latest FlickType watch app and its operation on iOS 15. Before I update my iPhone SE 2020 to iOS 15 or consider purchasing a new iPhone, I want to understand this group’s consensus of FlickType availability going forward. I have not upgraded to the recently released FlickType Watch/Container app on my iPhone because the FlickType keyboard is working very well on my iPhone and the new update removes the keyboard. Also, I get better results with the FlickType keyboard than I do with the FlickType container app because punctuation is spoken when typing with the keyboard but not with the container app. My questions follow: - Does the group believe that the recently released FlickType Watch/Container app will continue to be available in the App Store for purchased new devices?
- Does the group believe that the container app will remain a component of the FlickType Watch app going forward?
- Has anyone upgraded to iOS 15 and can comment on FlickType’s performance with it whether using the FlickType keyboard or the FlickType Watch/Container app either recently updated or not?
I have tried using the iOS on screen keyboard in slide to type mode and will confess with the expletives omitted that I don’t consider it a viable option going forward. I certainly don’t mind using the FlickType container app going forward since this was the method used with both the original Fleksy and FlickType and I can type, copy, and paste and get results more than twice as fast as typing on the on screen keyboard. Thanks in advance for your comments. Alan Lemly
|
|
|
Hi Chuck
Thank you for describing the slight Punctuation bug with the container app. using the container app again won't be a problem for ne, as I've been using it ever since that bug cropped up with the apple mail app. Plus i hate to say it but safari didn't work well on certain sites with the keyboard extention. So again, I just returned to the container app and copy paste text respectively.
Going to wait till ios 15.2 as it has been in my experience that most of the bugs of an ios major version has been iron out by then.
On 26 Sep 2021, at 06:31, Alan Lemly <walemly@...> wrote:
Chuck, That’s good to know and I’ll get used to typing with the container app again. Keeping it running in the app switcher will enable me to type about as quickly as I can with the FlickType keyboard in full screen mode. And thanks for recapping how the punctuation is currently handled. Alan From: hello@flicktype.groups.io <hello@flicktype.groups.io> On Behalf Of Chuck Dean
Sent: Saturday, September 25, 2021 11:28 PM
To: hello@flicktype.groups.io
Subject: Re: [FlickType] Need to confirm my understanding of FlickType container availability in iOS 15 and on new iDevices Yes, it has always been Kosta's intention to keep an accessible version of FlickType in the app store. BTW: when you are typing in the container app and you flick right to insert a period, the container app will repeat the last word you typed, instead of saying period, but it does insert the period. If you flick down you will hear. Comma, question mark, etc. And when you flick back up you will hear comma, period. This is a little glitch that will be fixed in the future. Pleez x cuze enny tie ping or spelin air ores.
On Sep 25, 2021, at 8:58 PM, Alan Lemly <walemly@...> wrote:
Hi Chuck, Thanks for sharing your exchange with Kosta. This is very encouraging because unless I’m misreading something, he intends for the container app to remain in the App Store. I assume it will continue as part of the FlickType watch app as it was with the last update. I hope his dispute with Apple over their latest watch and its quick path functionality doesn’t torpedo access to the container app in the future. I can type so much faster having access to FlickType and it would be a shame to lose it. Alan Hello Alan,
Here is an exchange I had with Kosta last week:
From Kosta:
My plan has always been to keep and maintain the container keyboard so
as to provide the full functionality of FlickType Classic with a share
button to export text.
I've been trying to get an update out since August 11 but Apple has
been dragging their feet, so I'm not quite sure when this will be out.
my reply:
The update showed up in the App Store this morning.
From Kosta:
Thank you for letting me know.
Unfortunately, Apple approved the wrong version - but at least this
should have the share button.
Since it's not the version I intended to release, I have paused the
update so that existing users won't automatically get it.
Kosta Pleez x cuze enny tie ping or spelin air ores. On Sat, Sep 25, 2021 at 9:39 AM Alan Lemly <walemly@...> wrote: Hi List, I’ve been following the various threads regarding removal of the FlickType keyboard from the App Store as well as those discussing the latest FlickType watch app and its operation on iOS 15. Before I update my iPhone SE 2020 to iOS 15 or consider purchasing a new iPhone, I want to understand this group’s consensus of FlickType availability going forward. I have not upgraded to the recently released FlickType Watch/Container app on my iPhone because the FlickType keyboard is working very well on my iPhone and the new update removes the keyboard. Also, I get better results with the FlickType keyboard than I do with the FlickType container app because punctuation is spoken when typing with the keyboard but not with the container app. My questions follow: - Does the group believe that the recently released FlickType Watch/Container app will continue to be available in the App Store for purchased new devices?
- Does the group believe that the container app will remain a component of the FlickType Watch app going forward?
- Has anyone upgraded to iOS 15 and can comment on FlickType’s performance with it whether using the FlickType keyboard or the FlickType Watch/Container app either recently updated or not?
I have tried using the iOS on screen keyboard in slide to type mode and will confess with the expletives omitted that I don’t consider it a viable option going forward. I certainly don’t mind using the FlickType container app going forward since this was the method used with both the original Fleksy and FlickType and I can type, copy, and paste and get results more than twice as fast as typing on the on screen keyboard. Thanks in advance for your comments. Alan Lemly
|
|
|
Hello Daniel, Waiting for the de-bugged version is a good idea.
BTW the container app has a done button in the upper right corner. Hit this after you typed what you want and a share button will appear in the same place. Hit this button to export your text to various apps. You can configure this panel, to some degree. I find it a little faster than closing FlickType and opening another app. Try it... You'll like it! : Chuck (mobile) Pleez x cuze enny tie ping or spelin air ores.
On Sep 26, 2021, at 12:56 AM, Daniel McGee <danielmcgee134@...> wrote:
Hi Chuck
Thank you for describing the slight Punctuation bug with the container app. using the container app again won't be a problem for ne, as I've been using it ever since that bug cropped up with the apple mail app. Plus i hate to say it but safari didn't work well on certain sites with the keyboard extention. So again, I just returned to the container app and copy paste text respectively.
Going to wait till ios 15.2 as it has been in my experience that most of the bugs of an ios major version has been iron out by then. On 26 Sep 2021, at 06:31, Alan Lemly <walemly@...> wrote:
Chuck, That’s good to know and I’ll get used to typing with the container app again. Keeping it running in the app switcher will enable me to type about as quickly as I can with the FlickType keyboard in full screen mode. And thanks for recapping how the punctuation is currently handled. Alan From: hello@flicktype.groups.io <hello@flicktype.groups.io> On Behalf Of Chuck Dean
Sent: Saturday, September 25, 2021 11:28 PM
To: hello@flicktype.groups.io
Subject: Re: [FlickType] Need to confirm my understanding of FlickType container availability in iOS 15 and on new iDevices Yes, it has always been Kosta's intention to keep an accessible version of FlickType in the app store. BTW: when you are typing in the container app and you flick right to insert a period, the container app will repeat the last word you typed, instead of saying period, but it does insert the period. If you flick down you will hear. Comma, question mark, etc. And when you flick back up you will hear comma, period. This is a little glitch that will be fixed in the future. Pleez x cuze enny tie ping or spelin air ores.
On Sep 25, 2021, at 8:58 PM, Alan Lemly <walemly@...> wrote:
Hi Chuck, Thanks for sharing your exchange with Kosta. This is very encouraging because unless I’m misreading something, he intends for the container app to remain in the App Store. I assume it will continue as part of the FlickType watch app as it was with the last update. I hope his dispute with Apple over their latest watch and its quick path functionality doesn’t torpedo access to the container app in the future. I can type so much faster having access to FlickType and it would be a shame to lose it. Alan Hello Alan,
Here is an exchange I had with Kosta last week:
From Kosta:
My plan has always been to keep and maintain the container keyboard so
as to provide the full functionality of FlickType Classic with a share
button to export text.
I've been trying to get an update out since August 11 but Apple has
been dragging their feet, so I'm not quite sure when this will be out.
my reply:
The update showed up in the App Store this morning.
From Kosta:
Thank you for letting me know.
Unfortunately, Apple approved the wrong version - but at least this
should have the share button.
Since it's not the version I intended to release, I have paused the
update so that existing users won't automatically get it.
Kosta Pleez x cuze enny tie ping or spelin air ores. On Sat, Sep 25, 2021 at 9:39 AM Alan Lemly <walemly@...> wrote: Hi List, I’ve been following the various threads regarding removal of the FlickType keyboard from the App Store as well as those discussing the latest FlickType watch app and its operation on iOS 15. Before I update my iPhone SE 2020 to iOS 15 or consider purchasing a new iPhone, I want to understand this group’s consensus of FlickType availability going forward. I have not upgraded to the recently released FlickType Watch/Container app on my iPhone because the FlickType keyboard is working very well on my iPhone and the new update removes the keyboard. Also, I get better results with the FlickType keyboard than I do with the FlickType container app because punctuation is spoken when typing with the keyboard but not with the container app. My questions follow: - Does the group believe that the recently released FlickType Watch/Container app will continue to be available in the App Store for purchased new devices?
- Does the group believe that the container app will remain a component of the FlickType Watch app going forward?
- Has anyone upgraded to iOS 15 and can comment on FlickType’s performance with it whether using the FlickType keyboard or the FlickType Watch/Container app either recently updated or not?
I have tried using the iOS on screen keyboard in slide to type mode and will confess with the expletives omitted that I don’t consider it a viable option going forward. I certainly don’t mind using the FlickType container app going forward since this was the method used with both the original Fleksy and FlickType and I can type, copy, and paste and get results more than twice as fast as typing on the on screen keyboard. Thanks in advance for your comments. Alan Lemly
|
|
|
Hi all,
I would like to ask a question, especially from all those who are now on iOS 15 and are using the Flicktype container app. Does anyone experience an incredibly long load time for the Flicktype app, whenever they try to launch it? Or even try to switch back to it from a different app from within the App Switcher? I say this because I have always experienced this on my phones, even on iOS 14 and prior. It takes quite a long time for it to launch, and I am saying up to 20 plus seconds at times on older phones. It is one of the reasons why I have refrained from using the container app since it just took so long to launch.
I have a first generation iPhone SE and the second generation iPhone SE. The load time is better on the newer SE but still quite long; definitely within the 15 second range.
Of course, Up to iOS 14, we had the keyboard extension available. Hence one could get around this issue by simply launching the keyboard within the app that they were using, rather than using the container app. However, with iOS 15, we are limited to using the container app, and so I was wondering if this behavior has changed or improved? Or if anyone has a solution/reason/suggestion for this? As you can imagine, it really doesn't help your productivity if the container app is going to take that long to load, each time you need to type even a short sentence.
Also yes, I agree, using the container app is kind of like going back to Flicktype Classic, which honestly, I can definitely work with. Considering how much I need and use Flicktype for literally everything on my phones, I'm grateful that that option is still available to us. Hopefully some of these bugs that others have described previously pertaining to the container app can be ironed out. And of course, this load-time issue that I have described above. For what it's worth, I didn't ever run into this particular issue with Flicktype Classic.
Any help would greatly be appreciated.
Salman
|
|
|
Hello, I have found that FlickType load time increases with the size of my dictionary. When FlickType takes more than a few seconds to load, I go into settings and the custom dictionary and clean out the garbage. Sometimes it is too big a task to clean it out word by word, so I just clear the dictionary and start over. I hope this helps, Chuck (mobile) Pleez x cuze enny tie ping or spelin air ores.
On Sep 27, 2021, at 6:59 AM, Salman Haider <salmanhaider.purdue@...> wrote:
Hi all,
I would like to ask a question, especially from all those who are now on iOS 15 and are using the Flicktype container app. Does anyone experience an incredibly long load time for the Flicktype app, whenever they try to launch it? Or even try to switch back to it from a different app from within the App Switcher? I say this because I have always experienced this on my phones, even on iOS 14 and prior. It takes quite a long time for it to launch, and I am saying up to 20 plus seconds at times on older phones. It is one of the reasons why I have refrained from using the container app since it just took so long to launch.
I have a first generation iPhone SE and the second generation iPhone SE. The load time is better on the newer SE but still quite long; definitely within the 15 second range.
Of course, Up to iOS 14, we had the keyboard extension available. Hence one could get around this issue by simply launching the keyboard within the app that they were using, rather than using the container app. However, with iOS 15, we are limited to using the container app, and so I was wondering if this behavior has changed or improved? Or if anyone has a solution/reason/suggestion for this? As you can imagine, it really doesn't help your productivity if the container app is going to take that long to load, each time you need to type even a short sentence.
Also yes, I agree, using the container app is kind of like going back to Flicktype Classic, which honestly, I can definitely work with. Considering how much I need and use Flicktype for literally everything on my phones, I'm grateful that that option is still available to us. Hopefully some of these bugs that others have described previously pertaining to the container app can be ironed out. And of course, this load-time issue that I have described above. For what it's worth, I didn't ever run into this particular issue with Flicktype Classic.
Any help would greatly be appreciated.
Salman
|
|
|
BTW: if you are like me and manually type some misspelled words on a regular basis it may be a wise idea to turn off Automatically learn new words in settings. This may prevent your dictionary from becoming overloaded. Chuck (mobile) Pleez x cuze enny tie ping or spelin air ores.
On Sep 27, 2021, at 8:13 AM, Chuck Dean <cadean329@...> wrote:
Hello, I have found that FlickType load time increases with the size of my dictionary. When FlickType takes more than a few seconds to load, I go into settings and the custom dictionary and clean out the garbage. Sometimes it is too big a task to clean it out word by word, so I just clear the dictionary and start over. I hope this helps, Chuck (mobile) Pleez x cuze enny tie ping or spelin air ores.
On Sep 27, 2021, at 6:59 AM, Salman Haider <salmanhaider.purdue@...> wrote:
Hi all,
I would like to ask a question, especially from all those who are now on iOS 15 and are using the Flicktype container app. Does anyone experience an incredibly long load time for the Flicktype app, whenever they try to launch it? Or even try to switch back to it from a different app from within the App Switcher? I say this because I have always experienced this on my phones, even on iOS 14 and prior. It takes quite a long time for it to launch, and I am saying up to 20 plus seconds at times on older phones. It is one of the reasons why I have refrained from using the container app since it just took so long to launch.
I have a first generation iPhone SE and the second generation iPhone SE. The load time is better on the newer SE but still quite long; definitely within the 15 second range.
Of course, Up to iOS 14, we had the keyboard extension available. Hence one could get around this issue by simply launching the keyboard within the app that they were using, rather than using the container app. However, with iOS 15, we are limited to using the container app, and so I was wondering if this behavior has changed or improved? Or if anyone has a solution/reason/suggestion for this? As you can imagine, it really doesn't help your productivity if the container app is going to take that long to load, each time you need to type even a short sentence.
Also yes, I agree, using the container app is kind of like going back to Flicktype Classic, which honestly, I can definitely work with. Considering how much I need and use Flicktype for literally everything on my phones, I'm grateful that that option is still available to us. Hopefully some of these bugs that others have described previously pertaining to the container app can be ironed out. And of course, this load-time issue that I have described above. For what it's worth, I didn't ever run into this particular issue with Flicktype Classic.
Any help would greatly be appreciated.
Salman
|
|
|
