1. alpha@flicktype.groups.io
   Date   
Re: Build 212 container app not working on my iPad Mini 2

FlickType
 

Hi Chuck,

Thanks for making us aware. This has nothing to do with the direct touch setting, right? Would you mind expanding on what you mean by this "I exit the app all the things I tried to open, flash open then vanished"?

Warmly,
Ashley
Re: Build 208

FlickType
 

Hi Dave,

Thanks for the detailed explanation. And yes, what you're proposing with removing the bar above the keyboard when the visual announcements are turned off makes sense and something we'd be happy to do. For the mail app, Kosta has attempted a fix for this but had lots of trouble due to some super funky behavior on Apple's side. You bring up a great point that this is more common than we thought since FlickType doesn't do so great with commonly used smaller words like hi or hey. Kosta is going to take another pass at it and will keep us all posted on how it goes.

For the dictionary capitalization, is it when you manually type a word at the beginning of the sentence? Is this a common occurrence? We put lots of thought into how to deal with capitalization at the beginning of the sentence and felt storing the word with a lowercase letter would be correct more often than keeping the capital letter as we do if it is typed in the middle of a sentence.

Warmly,
Ashley
Build 212 container app not working on my iPad Mini 2

Chuck Dean
 

Hi kosta,
I just updated my iPad Mini 2 to the latest ios and the container app does not work. I can not interact with any of the buttons and when I exit the app all the things I tried to open, flash open then vanished.

Not a big deal, I don't use my iPad for typing, I just wanted to try it out, and thought you should know. 

Chuck (mobile)
Pleez x cuze enny tie ping or spelin air ores.
Re: Build 208

David Nason
 

Hi Kosta & Ashley,

I can live with it, but I did prefer the slightly smaller one.
Basically, after typing my message, I have to reach up further to get to the app above the keyboard, which can be awkward. Even when you do that, you often have to swipe left or right to get to where you want, such as the send button. Those swipes generally have to be performed inside that top section, as if my thumb ventures down over the FlickType keyboard, I accidentally enter characters or punctuation.

I use the black colour option for maximum contrast between the keyboard and the app. I've noticed that even when I switch visual announcements off, the bar above the qwerty row remains on screen. If that could be removed it would help my typing, and also achieve my desire for the keyboard footprint to be smaller.
Would that be possible as a compromise?

PS Is there any progress on fixing the issue in Mail with FlickType inserting an unwanted space after the first letter if you manually type the first word on a new line? It's very annoying, especially because I would often start an email with a two or three letter word like Hi or Hey, which FlickType tends to struggle with if tap typed.

PPS I am also seeing the issue with dictionary words that should be capitalised losing their capital letter. I can't figure out any particular pattern to it though... odd.

Many thanks,
Dave

On 17 Nov 2018, at 04:16, Ed Worrell via Groups.Io <ed.worrell=icloud.com@groups.io> wrote:

Hey Kosta and Ashley,

It's going ok. I guess. I really am not in love with the half screen option. Its almost impossible for me to find the send button without typing unwanted characters.

On the plus side the keyboard is feeling really snappy the last few builds. The watch app is fantastic!👍🏻

Thanks,

E Ed
On Nov 16, 2018, at 12:42 PM, FlickType <hello@flicktype.com> wrote:

Hi Dave, Ed,

Hope you guys are well! We wanted to check in regarding the half-screen keyboard size and how it's working for you?

Thanks!
Ashley
Re: Build 208

Ed Worrell
 

Hey Kosta and Ashley,

It's going ok. I guess. I really am not in love with the half screen option. Its almost impossible for me to find the send button without typing unwanted characters.

On the plus side the keyboard is feeling really snappy the last few builds. The watch app is fantastic!👍🏻

Thanks,

E Ed

On Nov 16, 2018, at 12:42 PM, FlickType <hello@flicktype.com> wrote:

Hi Dave, Ed,

Hope you guys are well! We wanted to check in regarding the half-screen keyboard size and how it's working for you?

Thanks!
Ashley
Re: Build 208

FlickType
 

Hi Dave, Ed,

Hope you guys are well! We wanted to check in regarding the half-screen keyboard size and how it's working for you?

Thanks!
Ashley
Re: a few bugs

Rocco Fiorentino
 

Hi!

Congrats on the new baby!! So sorry it has taken me so long to reply, but I’ve also done some testing in the meantime and now have more info:

1. The strange behavior after new line: I’m not sure if this is new or not, but it’s been around for a while, just haven’t had a chance to report it or figure out when/where it came from. Note that I’ve been using half screen mode since it was introduced in Alpha, so maybe this is specific to just that? Not sure, but I can try in other modes and see if the behavior persists.

2. Kind of same as 1, more stuff about entering new lines, but you said that had already been reported. :)

3. The clear taps and/or adding periods is still happening accidentally for some reason. Again, seems to be something that probably started during half screen mode. While I’m on this subject, I’ll also add that I’ve had occasional times, I think when a new line is added, where I’ll type something like:
Ok, cool.
But when I go to change the period to a comma, Flicktype inserts multiple periods every time I swipe down, and doubles as it goes. haha so it will insert 1, then 2, then 4, then 8, etc. and when I go to delete the word I’ve just typed, it will say deleted 8 periods, etc.

4. It’s taken me a while to figure this one out, with different case entries in the dictionary, but it seems to be the second time that I’ve typed the word. So if I add "CSA" to the dictionary, and then type the word using Flicktype normally, it will type CSA. But symaltaniously, Flicktype seems to also enter this as a new entry in the dictionary, as "csa". So the next time I type "csa" into FlickType expecting it to come out as "CSA", it writes it as all lowercase "csa" because there’s now 2 entries of it in the dictionary. Not sure if all that makes sense, a lot to try and explain, but that’s the pattern I’ve noticed so far.

Thanks so much,

Rocco

On Oct 25, 2018, at 3:45 PM, FlickType <hello@flicktype.com> wrote:

Hi Rocco,

Super appreciate the thoughtful feedback and nice words!

For 1, is this something that's new behavior or has it always been this way? Either way, I've added it to our bug list. Another user just reported 2 this week, so we have that on the list and will be addressing it asap. For 3, my assumption is the two taps are quick in succession and the system registers them as a left flick rather than two taps. Will check with Kosta to learn whether we can implement a workaround. For 4, if you manually type a word at the beginning of a sentence you will have the word in the dictionary lowercase because the system assumes the word was meant to be lowercase, but I am unable to reproduce what you're reporting with the double entry. Have you noticed whether this happens when you type the word at the beginning or the middle of the of the sentence? What keyboard size? Anything you can provide to help me reproduce is appreciated!

Thanks for also submitting these suggestions! For the text field, unfortunately, FlickType cannot identify which text field you're typing in. If so, it would be a great idea! Let's keep thinking of fixes for this specific problem because it can get annoying to have every web address or email address added to your dictionary. We've had a few people ask about the number pad, so we'll look into a way of implementing an option, will take some time though due to the complications with the symbols also being displayed currently with the numbers. The reason we originally changed it was because people felt like it was too different from what they were used to with iOS.

Will be excited to hear your thoughts on the watch once you get around to trying it out!

Thanks again for the very helpful feedback!
Ashley

On Wed, Oct 24, 2018 at 02:32 PM, Rocco Fiorentino wrote:


This may very well be human error, but I find that at times when I’m typing
a word, Flicktype instead thinks I’m swiping left, and will say "clear taps"
in the middle of the word. Not necessarily a bug, just wondering why this
might be happening?
Re: A question regarding recent FlickType releases

Salman Haider
 

Hi Kosta,
Thank you for that. Makes sense now.
Salman

On Oct 29, 2018, at 9:21 PM, FlickType <hello@flicktype.com> wrote:

Hi Salman, and thank you for the question.

We send builds to the alpha group when we make changes that we think have a high risk of breaking something important that we miss during testing. If we have more confidence in our changes, we will often release builds straight to beta in the interest of iterating faster. That said, our judgement is not always correct, but we are trying to strike a good balance between developing fast and not breaking everyone's keyboard too often, smile.

Let me know if you have any more questions.

Warmly,
- Kosta
Re: Build 208

Ed Worrell
 

I too an disappointed to see the minimal keyboard size go away. The half screen keyboard seems like I an stretching to far to tap in the proper spots.. I am getting way to many stupid errors with this size of keyboard of which it makes it kind of pointless to use now...

Please find a compromise. With the phones getting bigger and bigger this becomes more of a chore to type. The smaller keyboard really helps out. I also feel like I an stretching way to far to find the post, send and any other buttons I might have to use, and I really dislike the full screen option.

Thanks,

E d

On Oct 29, 2018, at 10:03 PM, FlickType <hello@flicktype.com> wrote:

Thank you Chuck.

Dave, please keep us updated on how the new size feels over the next few days.

Thank you,
Kosta
Re: Build 208

FlickType
 

Thank you Chuck.

Dave, please keep us updated on how the new size feels over the next few days.

Thank you,
Kosta
Re: Build 208

David Nason
 

Hi,

Yes, basically it was just to see more of the app above the keyboard. Especially in messaging apps, it just felt like a good fit.
I will see how I get on with the new size.

I'm using iPhone X.

Dave
  
  


On 30 Oct 2018, at 01:23, Chuck Dean <cadean329@...> wrote:

Hello Kosta,
I was using the minimal keyboard up until a couple of weeks ago, but I was having problems with tapping above the keyboard, so I went to the ½ screen keyboard which is working fine.

This new build is working well on both my iPhone and Apple watch.👍 

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


On Oct 29, 2018, at 6:17 PM, Michael Maslo <michaelmaslo04@...> wrote:

Hello Kosta,

I was using the minimum keyboard but I can use the standard size. The only thing I personally care about is being able to hit the send button on email or text messages. 

Sincerely,

Michael maslo

On Oct 29, 2018, at 20:01, FlickType <hello@...> wrote:

Hi Dave,

We would love to figure out a way to accommodate your preference. 

We removed the minimal size keyboard option because it was used by less than 10% of our users and we want to streamline aspects of the app. Having more settings often makes it much harder for us to test and maintain smooth operation of all possible configurations of the app, which grow exponentially with each added option. Additionally, having more settings can often make the experience for new users feel too complicated.

Please tell us more about what you liked in the minimal size. Is it the ability to have more space for the app above? Or the lack of visual announcements? And what device are you currently using?

Thank you,
- Kosta





On Mon, Oct 29, 2018 at 4:28 PM David Nason <dnason@...> wrote:
Hi Kosta and Ashley,

Can I ask, why have you removed the minimal size keyboard option? Disappointing if it's permanent.

Thanks,
Dave
Re: Build 208

Chuck Dean
 

Hello Kosta,
I was using the minimal keyboard up until a couple of weeks ago, but I was having problems with tapping above the keyboard, so I went to the ½ screen keyboard which is working fine.

This new build is working well on both my iPhone and Apple watch.👍 

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


On Oct 29, 2018, at 6:17 PM, Michael Maslo <michaelmaslo04@...> wrote:

Hello Kosta,

I was using the minimum keyboard but I can use the standard size. The only thing I personally care about is being able to hit the send button on email or text messages. 

Sincerely,

Michael maslo

On Oct 29, 2018, at 20:01, FlickType <hello@...> wrote:

Hi Dave,

We would love to figure out a way to accommodate your preference. 

We removed the minimal size keyboard option because it was used by less than 10% of our users and we want to streamline aspects of the app. Having more settings often makes it much harder for us to test and maintain smooth operation of all possible configurations of the app, which grow exponentially with each added option. Additionally, having more settings can often make the experience for new users feel too complicated.

Please tell us more about what you liked in the minimal size. Is it the ability to have more space for the app above? Or the lack of visual announcements? And what device are you currently using?

Thank you,
- Kosta





On Mon, Oct 29, 2018 at 4:28 PM David Nason <dnason@...> wrote:
Hi Kosta and Ashley,

Can I ask, why have you removed the minimal size keyboard option? Disappointing if it's permanent.

Thanks,
Dave
Re: Build 208

FlickType
 

Thank you for the feedback, Michael.

Let's continue the conversation in the beta group where build 208 was released, so that everyone can benefit from the exchange.

Warmly,
Kosta
Re: A question regarding recent FlickType releases

FlickType
 

Hi Salman, and thank you for the question.

We send builds to the alpha group when we make changes that we think have a high risk of breaking something important that we miss during testing. If we have more confidence in our changes, we will often release builds straight to beta in the interest of iterating faster. That said, our judgement is not always correct, but we are trying to strike a good balance between developing fast and not breaking everyone's keyboard too often, smile.

Let me know if you have any more questions.

Warmly,
- Kosta
Re: Build 208

Michael Maslo
 

Hello Kosta,

I was using the minimum keyboard but I can use the standard size. The only thing I personally care about is being able to hit the send button on email or text messages. 

Sincerely,

Michael maslo

On Oct 29, 2018, at 20:01, FlickType <hello@...> wrote:

Hi Dave,

We would love to figure out a way to accommodate your preference. 

We removed the minimal size keyboard option because it was used by less than 10% of our users and we want to streamline aspects of the app. Having more settings often makes it much harder for us to test and maintain smooth operation of all possible configurations of the app, which grow exponentially with each added option. Additionally, having more settings can often make the experience for new users feel too complicated.

Please tell us more about what you liked in the minimal size. Is it the ability to have more space for the app above? Or the lack of visual announcements? And what device are you currently using?

Thank you,
- Kosta





On Mon, Oct 29, 2018 at 4:28 PM David Nason <dnason@...> wrote:
Hi Kosta and Ashley,

Can I ask, why have you removed the minimal size keyboard option? Disappointing if it's permanent.

Thanks,
Dave
Re: Build 208

FlickType
 

Hi Dave,

We would love to figure out a way to accommodate your preference. 

We removed the minimal size keyboard option because it was used by less than 10% of our users and we want to streamline aspects of the app. Having more settings often makes it much harder for us to test and maintain smooth operation of all possible configurations of the app, which grow exponentially with each added option. Additionally, having more settings can often make the experience for new users feel too complicated.

Please tell us more about what you liked in the minimal size. Is it the ability to have more space for the app above? Or the lack of visual announcements? And what device are you currently using?

Thank you,
- Kosta





On Mon, Oct 29, 2018 at 4:28 PM David Nason <dnason@...> wrote:
Hi Kosta and Ashley,

Can I ask, why have you removed the minimal size keyboard option? Disappointing if it's permanent.

Thanks,
Dave
Build 208

David Nason
 

Hi Kosta and Ashley,

Can I ask, why have you removed the minimal size keyboard option? Disappointing if it's permanent.

Thanks,
Dave
A question regarding recent FlickType releases

Salman Haider
 

Hi Kosta and Ashley,
I had a question about the recent updates that I have been receiving on the Alpha group and Testflight. Just a bit confused about the sequence of the releases and I wanted to simply confirm this; The last couple of releases (208 and 204) have not been sent out to the Alpha group, and have been sent directly to Beta, is that how it was supposed to be, or is there something that I missed on the alpha group? Also, I noticed that releases for the Alpha group have been a lot more spaced out off late. The last one that I seem to have seen anything about on the Alpha group was version 201. Again, just wanting to confirm that I haven’t been missing anything on the Alpha group. It’s not been very active lately either, so was curious.
Thanks,
Salman
Re: Build 201

David Nason
 

Coolio, thanks Ashley.

On 25 Oct 2018, at 22:01, FlickType <hello@flicktype.com> wrote:

Thanks, David! NOw have had someone else report the same. Kosta will look into it as soon as he gets the chance, he's currently working on a couple of the other issues you reported.

Thanks again!
Ashley

On Mon, Oct 22, 2018 at 12:45 PM, David Nason wrote:


So if I were to type "Ashley" manually at the start of a line. As I type the
letters, all seems well. But when I swipe right to complete the word,
VoiceOver will say "shley", and navigating back, I will discover that what has
been typed is "A shley".
Re: Build 201

FlickType
 

Thanks, David! NOw have had someone else report the same. Kosta will look into it as soon as he gets the chance, he's currently working on a couple of the other issues you reported.

Thanks again!
Ashley

On Mon, Oct 22, 2018 at 12:45 PM, David Nason wrote:


So if I were to type "Ashley" manually at the start of a line. As I type the
letters, all seems well. But when I swipe right to complete the word,
VoiceOver will say "shley", and navigating back, I will discover that what has
been typed is "A shley".
41 - 60 of 2168  
More
Home Messages Hashtags Wiki About Features Pricing Updates Terms Help Twitter