Lucian, Christopher, thanks for following up on the discussion. I understand your concerns and agree that the switch to iOS 7 did not go as planned. The unexpected time bomb bug forced our hand before we could incorporate iOS 6 support for our brand new engine or even communicate the change appropriately. There is, however, reason why our keyboard service is at this time compatible only with iOS 7. As of today, Fleksy is available as a keyboard option for third party apps. This means that Fleksy can be integrated at the application-level of any iOS app. Any developer can incorporate Fleksy into their app, giving their users the choice to type with Fleksy.
We were able to develop the SDK because of the tools iOS 7 introduced. However, since last week we made progress in porting the new engine to iOS 6 and have built alpha versions since. Pending a few crashes, we will be submitting an update for Fleksy to restore functionality for iOS 6 as soon as possible. Once again, thank you fore your patience and understanding! - Bill from the Fleksy team Read more about our Fleksy SDK and the 4 apps that offer Fleksy as their keyboard right now at http://fleksy.com/blog/android-cant-have-all-the-fun-fleksy-comes-to-ios/ On Wed, Dec 11, 2013 at 7:35 PM, Christopher Chaltain <[email protected]>wrote: > I'm not sure Fleksy is leaving that many people behind. The vast majority > of people have moved up to IOS 7. I think the people with a real beef are > those iPhone 3 users who can't move up to IOS 7 at all. > > Fleksy is by no means the only app that predates IOS 7 which is now only > supported on IOS 7. Obviously, a developer would have to spend testing > resources on IOS 6 and IOS 7 if they're going to continue to support both > levels of the operating system. This cost alone may keep a small company > from supporting both operating systems. It's also my understanding that > Apple changes API's from version to version, so it's not a given that > there's no work involved in supporting both IOS 6 and IOS 7. > > Apple did take a beating when they rolled out IOS 7 updates automatically > to people whether they upgraded or wanted to upgrade or not, so I'm sure > they'd take a beating in the scenario you described below. This doesn't > mean it isn't a good business idea for Apple to keep moving people up and > for developers to assume everyone is on the latest. This model has > obviously been wildly successful for Apple, and there's a lot of benefits > for Apple, developers and users to all be on the latest and greatest > software. > > > On 12/11/2013 12:48 AM, Lucian Fratila wrote: > >> Honestly I can't think of any other app that with no prior notice pulled >> support from a large chunk of its users (those on iOS 6 in this case). >> >> Yes I have an iPhone 4 and no, I don't want to upgrade to 7 for an >> obvious variety of reasons - and most certainly not because an app forces >> me to. What I find absolutely mind-boggling is that we're talking here >> about an offline app, that worked very well thank you on iOS 6 before. >> >> Yes, I did contact Fleksy support and they simply told me that Fleksy >> version 1.9 (the last iOS 6 working version) is not supported anymore. As >> if they had to! >> >> Yes, there are apps that only work on iOS 7 these days. But they either >> started on iOS 7, or they have a backend that no longer supports the iOS 6 >> version. As far as I understand, the technology behind Fleksy is built-in >> inside the app and does not require online presence (heck, if a typing app >> requires you to be connected to their servers, then something is fishy big >> time). >> >> So in short I find no excusable justification to what Fleksy did. They're >> lucky their service is not high profile and they don't affect a real lot of >> paying users. Just think the backlash that, say, Apple would get if >> suddenly iTunes would no longer start on OS X pre-Mavericks, and would give >> you no option but to upgrade, even on a 2007 laptop. Luckily for them >> Fleksy is no Apple. But at this rate, I don't see them even turning >> profitable. What a shame when it's not the technology that buries you, but >> poor customer support. >> >> /end of rant >> >> > -- > Christopher (CJ) > chaltain at Gmail > > > -- > You received this message because you are subscribed to the "VIPhone" > Google Group. > > Post a new message to VIPhone by emailing [email protected]. > > Search and view the VIPhone archives by visiting > http://www.mail-archive.com/[email protected]/. > > Reach the VIPhone owner and moderators by emailing > [email protected]. > > Unsubscribe and leave VIPhone by emailing viphone+unsubscribe@ > googlegroups.com. > > More VIPhone group options can be found by visiting > http://groups.google.com/group/viphone?hl=en. > --- 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/hp1U42rLwyg/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the "VIPhone" Google Group. Post a new message to VIPhone by emailing [email protected]. Search and view the VIPhone archives by visiting http://www.mail-archive.com/[email protected]/. Reach the VIPhone owner and moderators by emailing [email protected]. Unsubscribe and leave VIPhone by emailing [email protected]. More VIPhone group options can be found by visiting http://groups.google.com/group/viphone?hl=en. --- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
