Date   
Re: Another observation

 

I was going to say that 27% of the battery used is a lot, but then I noticed that you've used FlickType for more than eleven hours in a week! If that's correct, you surely are among the most active FlickType users, ever! Thank you! Smile.

I do think we can make FlickType more energy efficient, but before we invest any effort in that area, I will first post the question to the beta group at some point and see how most folks feel about it.

- Kosta

Re: Another observation

Chuck Dean
 

FlickType, 11.4 hrs on screen – 2 min background 27%

Chuck

On Apr 21, 2018, at 10:00 PM, FlickType <@FlickType> wrote:

Thank you Chuck, I was actually not aware of this. Can you or any frequent
FlickType user please report back what kind of battery consumption you get
under Settings, Battery, "Last 7 Days"?

Thanks again!
- Kosta

http://flicktype.com
Invite your friends to beta@... today!
Follow us @FlickType <https://twitter.com/FlickType> for the latest updates!
Join the discussion: https://groups.io/g/flicktype

On Sat, Apr 21, 2018 at 9:42 PM, Chuck Dean <cadean329@...> wrote:

Another observation.
Hello all,
As I remember it, Fleksy VO was a battery eater. Writing a couple of
emails would use 20% of the battery.
I am wondering it is the new app or the newer iphones.



Chuck





Re: Another observation

 

Thank you Chuck, I was actually not aware of this. Can you or any frequent
FlickType user please report back what kind of battery consumption you get
under Settings, Battery, "Last 7 Days"?

Thanks again!
- Kosta

http://flicktype.com
Invite your friends to beta@... today!
Follow us @FlickType <https://twitter.com/FlickType> for the latest updates!
Join the discussion: https://groups.io/g/flicktype

On Sat, Apr 21, 2018 at 9:42 PM, Chuck Dean <cadean329@...> wrote:

Another observation.
Hello all,
As I remember it, Fleksy VO was a battery eater. Writing a couple of
emails would use 20% of the battery.
I am wondering it is the new app or the newer iphones.



Chuck




Another observation

Chuck Dean
 

Another observation.
Hello all,
As I remember it, Fleksy VO was a battery eater. Writing a couple of emails would use 20% of the battery.
I am wondering it is the new app or the newer iphones.



Chuck

Re: Build 44

Ed Worrell
 

Hello,

Will there be an option to make the keyboard fit inside the standard keyboard section when it becomes an extension? I would love to see this as an option.

Thanks,
Ed

On Apr 21, 2018, at 5:00 PM, FlickType <@FlickType> wrote:

Confirming that build 44 just went out to beta.

With regards to the new menu gesture, the idea is that whatever becomes the main gesture to invoke the menu in the standalone FlickType app, is also going to be the gesture to dismiss the keyboard once it's available inside every app. We really want to make this as easy as possible, since the keyboard will be fullscreen, so that you can easily dismiss it if you need to interact with the app you're in, and then quickly resume typing by double tapping on the application's textfield again.

Warmly,
Kosta


Re: Build 44

 

Confirming that build 44 just went out to beta.

With regards to the new menu gesture, the idea is that whatever becomes the main gesture to invoke the menu in the standalone FlickType app, is also going to be the gesture to dismiss the keyboard once it's available inside every app. We really want to make this as easy as possible, since the keyboard will be fullscreen, so that you can easily dismiss it if you need to interact with the app you're in, and then quickly resume typing by double tapping on the application's textfield again.

Warmly,
Kosta

Re: TestFlight down for anyone else?

 

TestFlight has been down for scheduled maintenance between 7am and 3pm PST.

We'll push build 44 to beta as soon as the TestFlight backend is operational again - it's still down for us.

Thank you all for the great feedback!
Kosta

Re: TestFlight down for anyone else?

Chuck Dean
 

Hello Alan,
I went to Test Flight and got the same message as you.

Chuck

On Apr 21, 2018, at 11:28 AM, Alan Lemly <@walemly> wrote:

Hi list,

I've been getting an error message for several hours from TestFlight that it is down for temporary maintenance. Is anyone else getting this? It seems to have been going on for a lot longer than I'd call temporary.

Thanks.

Alan Lemly


TestFlight down for anyone else?

 

Hi list,

I've been getting an error message for several hours from TestFlight that it is down for temporary maintenance. Is anyone else getting this? It seems to have been going on for a lot longer than I'd call temporary.

Thanks.

Alan Lemly

Just a suggestion,

Chuck Dean
 

Just a suggestion,
Hello Kosta,
Could you add @ icloud.com. to the list under the @ sign?
Considering all of us are using iphones, many may be using this as an email address. I use it as a secondary... More private email address.
Thanks,


Chuck

Re: Build 44

Chanelle Allen
 

Hello,
This is another awesome version of FlickType! Thank you, Kosta and Ashley! The new flick down and hold gesture works well and as expected. I am also curious as to why new menu gestures are being introduced. I appreciate that VoiceOver now announces what it should every time the tap and hold gesture is invoked to find letters/numbers/symbols. I am also hearing VoiceOver announce when I delete incorrectly typed characters. Maybe the more we type, the more confident we will become about what is being deleted. I am slightly embarrassed that I have not used FlickType on a regular basis since it is quicker to type short texts using braille screen input directly in the Messages or Mail app, but being a member of the alpha group has given me motivation and excitement for when FlickType becomes a keyboard.
By the way, someday, it would be so neat if we could actually type on our wrists! I think that the apple watch needs more processing power though.
Chanelle

On Apr 21, 2018, at 00:36, Macster <@Macster> wrote:

Hi guys,

I'm very happy to say the two problems I encountered with the previous build are now not an issue. Superb job in a short period of time again. I like the idea of announcing deletion of partial words, though as you say it might be difficult to follow depending on the accuracy or otherwise of my typing.

I genuinely think this is the best the app has ever worked, and I include the old app in that as well. And the new flick down and hold gesture works a treat. Bliss!


Re: Build 44

Chuck Dean
 

I am hoping the stand alone app will be supported after the system wide extension is implemented. I think I'd still use it, although if the system wide keyboard works as well as the app, perhaps not.

Chuck

On Apr 20, 2018, at 10:44 PM, Alan Lemly <@walemly> wrote:

Chuck,

That makes perfect sense. I'm so caught up enjoying the standalone FlickType
that I keep forgetting about the third party keyboard extension and how it
can impact the gesture decisions.

Alan

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf
Of Chuck Dean
Sent: Saturday, April 21, 2018 12:17 AM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 44

Hi Alan,
My best guess is it has something to do with the system wide extension
coming in the future. Perhaps Kosta wants us to be ready with the proper
gesture.

Chuck


On Apr 20, 2018, at 10:11 PM, Alan Lemly <@walemly> wrote:

I can confirm Chuck's findings too. The new gesture to invoke the menu
works as it should with no control center being invoked. I also prefer
the old 2 finger swipe up to invoke the menu. I'm curious, why is
another gesture to invoke the menu needed? Are the plans to have two
different ways to invoke the menu and if not, which one will survive?

Thanks for all your hard work.

Alan Lemly

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On
Behalf Of Chuck Dean
Sent: Friday, April 20, 2018 10:36 PM
To: Alpha
Subject: [FlickType-alpha] Build 44

Build 44
Looks good. The swipe up for caps is working again.
The swipe down and hold brings up the menu and nothing else.
Personally I like the two finger swipe up better.
The keyboard is stable and responsive.

I still do not hear anything when deleting partial words. I may be in
the minority, but I would rather hear gibberish then nothing, at least
I would have an idea where the cursor is. Otherwise, I like it!


Chuck










Re: Build 44

 

Chuck,

That makes perfect sense. I'm so caught up enjoying the standalone FlickType
that I keep forgetting about the third party keyboard extension and how it
can impact the gesture decisions.

Alan

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf
Of Chuck Dean
Sent: Saturday, April 21, 2018 12:17 AM
To: alpha@flicktype.groups.io
Subject: Re: [FlickType-alpha] Build 44

Hi Alan,
My best guess is it has something to do with the system wide extension
coming in the future. Perhaps Kosta wants us to be ready with the proper
gesture.

Chuck


On Apr 20, 2018, at 10:11 PM, Alan Lemly <@walemly> wrote:

I can confirm Chuck's findings too. The new gesture to invoke the menu
works as it should with no control center being invoked. I also prefer
the old 2 finger swipe up to invoke the menu. I'm curious, why is
another gesture to invoke the menu needed? Are the plans to have two
different ways to invoke the menu and if not, which one will survive?

Thanks for all your hard work.

Alan Lemly

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On
Behalf Of Chuck Dean
Sent: Friday, April 20, 2018 10:36 PM
To: Alpha
Subject: [FlickType-alpha] Build 44

Build 44
Looks good. The swipe up for caps is working again.
The swipe down and hold brings up the menu and nothing else.
Personally I like the two finger swipe up better.
The keyboard is stable and responsive.

I still do not hear anything when deleting partial words. I may be in
the minority, but I would rather hear gibberish then nothing, at least
I would have an idea where the cursor is. Otherwise, I like it!


Chuck






Re: Build 44

Macster
 

Hi guys,

I'm very happy to say the two problems I encountered with the previous build are now not an issue. Superb job in a short period of time again. I like the idea of announcing deletion of partial words, though as you say it might be difficult to follow depending on the accuracy or otherwise of my typing.

I genuinely think this is the best the app has ever worked, and I include the old app in that as well. And the new flick down and hold gesture works a treat. Bliss!

Re: Build 44

Chuck Dean
 

Hi Alan,
My best guess is it has something to do with the system wide extension coming in the future. Perhaps Kosta wants us to be ready with the proper gesture.

Chuck

On Apr 20, 2018, at 10:11 PM, Alan Lemly <@walemly> wrote:

I can confirm Chuck's findings too. The new gesture to invoke the menu works
as it should with no control center being invoked. I also prefer the old 2
finger swipe up to invoke the menu. I'm curious, why is another gesture to
invoke the menu needed? Are the plans to have two different ways to invoke
the menu and if not, which one will survive?

Thanks for all your hard work.

Alan Lemly

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf
Of Chuck Dean
Sent: Friday, April 20, 2018 10:36 PM
To: Alpha
Subject: [FlickType-alpha] Build 44

Build 44
Looks good. The swipe up for caps is working again.
The swipe down and hold brings up the menu and nothing else. Personally I
like the two finger swipe up better.
The keyboard is stable and responsive.

I still do not hear anything when deleting partial words. I may be in the
minority, but I would rather hear gibberish then nothing, at least I would
have an idea where the cursor is. Otherwise, I like it!


Chuck






Re: Build 44

 

I can confirm Chuck's findings too. The new gesture to invoke the menu works
as it should with no control center being invoked. I also prefer the old 2
finger swipe up to invoke the menu. I'm curious, why is another gesture to
invoke the menu needed? Are the plans to have two different ways to invoke
the menu and if not, which one will survive?

Thanks for all your hard work.

Alan Lemly

-----Original Message-----
From: alpha@flicktype.groups.io [mailto:alpha@flicktype.groups.io] On Behalf
Of Chuck Dean
Sent: Friday, April 20, 2018 10:36 PM
To: Alpha
Subject: [FlickType-alpha] Build 44

Build 44
Looks good. The swipe up for caps is working again.
The swipe down and hold brings up the menu and nothing else. Personally I
like the two finger swipe up better.
The keyboard is stable and responsive.

I still do not hear anything when deleting partial words. I may be in the
minority, but I would rather hear gibberish then nothing, at least I would
have an idea where the cursor is. Otherwise, I like it!


Chuck

Re: Version 41 what is the haptic feedback?

Chuck Dean
 

Hi,
I tried the haptic feedback last night. You are right, it does give another dimension to typing. Personally, I like it better off. Somewhere in the back of my mind, I know the haptic feedback is eating up batteries. :)

Chuck

On Apr 20, 2018, at 8:35 PM, FlickType <@FlickType> wrote:

Chuck, all jokes aside, my gut feeling is that FlickType on the watch would be quite possible and even fun to use. We have no such plans currently, but it might be worthwhile trying it out at some point.

On the haptic feedback, my opinion is that it literally adds a new dimension to the feedback you get from the device, enriching the interactive experience. Everyone's different, but I personally quite like it. If you'd like, you can temporarily turn on the system option under "Settings", "Sounds & Haptics" and give FlickType a go - we'd love to hear what you think!

Warmly,
Kosta


Re: Build 44

 
Edited

Thanks Chuck, noted on the partial word deletion, this will be addressed soon. - Kosta

Build 44

Chuck Dean
 

Build 44
Looks good. The swipe up for caps is working again.
The swipe down and hold brings up the menu and nothing else. Personally I like the two finger swipe up better.
The keyboard is stable and responsive.

I still do not hear anything when deleting partial words. I may be in the minority, but I would rather hear gibberish then nothing, at least I would have an idea where the cursor is. Otherwise, I like it!


Chuck

Re: Version 41 what is the haptic feedback?

 

Chuck, all jokes aside, my gut feeling is that FlickType on the watch would be quite possible and even fun to use. We have no such plans currently, but it might be worthwhile trying it out at some point.

On the haptic feedback, my opinion is that it literally adds a new dimension to the feedback you get from the device, enriching the interactive experience. Everyone's different, but I personally quite like it. If you'd like, you can temporarily turn on the system option under "Settings", "Sounds & Haptics" and give FlickType a go - we'd love to hear what you think!

Warmly,
Kosta