Le 30/11/2018 à 20:45, FlickType a écrit :

Hi JPR,

Following your instructions, I created a definition with over 100 characters. They shouldn't feel like this is a FlickType issue since it does work in FlickType and does not work for the iOS keyboard if it were the other way around then it would make sense if they thought it was a FlickType issue. Here is a link for submitting issues to Apple: https://www.apple.com/feedback/iphone.html

Please let us know how it goes!
Ashley

Hi Brad,

Though it's a great idea, unfortunately, we are not able to invoke the send due to the fact that this is on the app side and not on the keyboard side.

Warmly,
Ashley

On Thu, Nov 29, 2018 at 05:47 AM, Brad Dunse wrote:

It might not even be technically possible, or user plausible ... just a
thought I had while writing.

Le 30/11/2018 à 19:19, FlickType a écrit :

Hi JPR,

Thanks for including such great instructions on your issue, but I am not able to reproduce, my text replacement shortcuts are working in both places. My assumption is this may be on Apple's side.

Anyone else have a similar issue?

Thanks!
Ashley

On Thu, Nov 29, 2018 at 05:47 AM, Brad Dunse wrote:

It might not even be technically possible, or user plausible ... just a
thought I had while writing.

Le 26/11/2018 à 00:00, Jean-Philippe Rykiel a écrit :

Hi friends.
This message is off-topic here, but I would really appreciate the help of an iOS Maestro. Since a few months, I have an issue with one definition in my text replacements.
This one is 302 letters long, and it doesn’t expand anymore. For a moment, I thought it had something to do with FlickType, since it started including text replacements. So I removed flicktype from my phone, but the problem remains.
Then, I restored my phone, and still no luck. Finally I tried removing and re-entering my definition, but no effect yet. This definition works on another friends phone, same iOS, but mine is a seven, and his is an X.
Any idea?
Please ignore this message and except my apologies if you count help. Next line Cheers,
JpR

http://www.jprykiel.com

http://soundcloud.com/ryksounet
http://twitter.com/ryksounet
Http://www.facebook.com/jprykiel

On 22/11/2018, Robert Kingett <kingettr@gmail.com> wrote:

Once Patreon becomes more accessible, perhaps you could offer perks through
that service. I'd say $20 would be good for a one time fee or even $40. I
looked through the app developer guidelines and I just don't get how you
guys are breaking rules? Can't Apple see that by releasing updates as often
as you do, this is actually making you compliant with their guidelines?
Section 3.1.2 of the App Store Review Guidelines states: "Apps may offer
auto-renewing in-app purchase subscriptions, regardless of category on the
App Store." It also goes on to state that "you must provide ongoing value to
the customer" and that "examples of appropriate subscriptions include:
[...], apps that offer consistent, substantive updates;". In my book, you
guys are doing that, hands down.

---

What about a yearly subscription for  around $20. This way there would
be that cash flow, maybe not every month, but at least the cash would
come in for continued development. And maybe Apple would be more willing
to work with you on a yearly subscription.

On 11/21/2018 3:53 PM, Matt Selm wrote:
> As someone who has wanted to see a single price for this app, I would gladly pay thirty or so. I do realize there are many factors that the developer has to consider though. This may be a crazy idea, but would anyone support an egg based model? Perhaps you are asked to watch an add after sending a message or showing discreet banners at the top of the screen. Again, I know this is a crazy idea, but I would rather see something out of the ordinary than to have the development stop entirely.
>
> Matt
>
>> On Nov 21, 2018, at 8:06 AM, Jean-Philippe Rykiel <jprykiel@...> wrote:
>>
>> Hi Jessica.
>>
>> Applevis, like any other words unknown to flick type, can be added to its dictionary. All you have to do is type it manually by holding your finger on the screen, choosing the right letters One by one, releasing your finger from the screen after each letter, and flicking right after the entire word is typed. And your new words will be there ever after. Try it.
>>
>> Best regards,
>>
>> JPR
>>
>> http://jeanphilipperykiel.com
>>
>> http://soundcloud.com/ryksounet
>> http://twitter.com/ryksounet
>> http://facebook.com/jeanphilipperykiel
>>
>>> Le 21/11/2018 à 13:53, Jessica D a écrit :
>>> Hi,
>>> I love Flicktype.
>>>
>>> I'd be willing to pay anything between $0.99, and $9.99.
>>>
>>> If the new price was above that, I'd think about it first, because some of the words I type, like Applevis, aren't recognized by flicktype.
>>>
>>> Flicktype has trouble entering web addresses in Safari.
>>>
>>> Thanks,
>>> Jessica
>>>> On Nov 21, 2018, at 5:07 AM, Mark Davies <mark.davies@...> wrote:
>>>>
>>>> Hello,
>>>> Sorry to read about your problems with Apple. Shame that a company that tries to gain PR credit by telling the world how great they are for doing accessibility seems unable to communicate the need for accessibility to ALL their staff.
>>>> Anyway, regarding pricing, my suggestion would be to try to keep it fairly low but to include a "tip jar" in the app. That way people could still support you in the future. I know a few apps use this method already, although I'm not sure how effective it is financially.
>>>> BTW I use the stand alone version of FT and you could put a donation button there too, with maybe a suggested amount.
>>>>
>>>> Mark
>>>>
>>>> Mark.Davies@...
>>>>
>>>>> On 20 Nov 2018, at 23:20, FlickType <hello@...> wrote:
>>>>>
>>>>> Dear FlickType friends,
>>>>>
>>>>> We have had numerous rejections of FlickType by Apple over the last few months, most often due to the uncommon nature of our app being a keyboard for VoiceOver users. Usually the reviewer is confused by the way they need to operate the keyboard with VoiceOver, and it takes some back-and-forth before they eventually reverse their devision and let us release our updates to the App Store.
>>>>>
>>>>> This past weekend, our update got rejected because, quote, "the app uses auto-renewing subscriptions, but it is not an appropriate use of the service". This has happened before, and after our detailed explanation and position they agreed to reverse their decision at the time. It would seem that they have now either changed their policy, or this is a different person reviewing the app and for some reason they don't have the context of our earlier conversations. This is likely to happen again in the future, even if we succeed in getting the current update through.
>>>>>
>>>>> Either way, App Store rejections and appeals to the App Review Board take a long time to resolve, time that we can better spend developing the app itself. We have therefore decided to drop the subscription model moving forward, and instead introduce a one-off purchasing fee for the system-wide keyboard, so that we at least eliminate one of the potential causes of App Store rejections and delays in the future.
>>>>>
>>>>> We have not yet decided on the pricing, and in fact we'd love to hear some of your ideas on that. We are still hoping that we can find a price that is both reasonable for users, and also sustainable for us as a business. We also wanted to share this background information with you, and for you to be aware of the upcoming pricing changes.
>>>>>
>>>>> Again, we welcome your thoughts in the matter, and we are thankful for all your support so far.
>>>>>
>>>>> Warmly,
>>>>> Kosta
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>>
>>
>
>