• Avatar
    Permanently Deleted User

    I would agree with this. The Swiftkey keyboard is tiny in size compared to the Apple keyboard on the 6 Plus. I find myself only using SwiftKey on WhatsApp these days as it is still hasn't been updated and is therefore magnified and bigger.

    0
    Comment actions Permalink
  • Avatar
    Brandon O'Berry

    Thanks for the suggestions, guys! As you know, SwiftKey is still relatively in its early stages in the app store, so features are still severely limited. Based on the latest update, I'd say the SwiftKey team is currently hard at work resolving some bugs that are plaguing users throughout the iOS platform. Rest assured, they are also actively trying to improve/update the app as best/quickly as possible with features that users want! If there's a specific feature you feel should be added first and foremost, I encourage you to submit a feature request ticket here so that the SwiftKey team receives it directly. 😄

    1
    Comment actions Permalink
  • Avatar
    Permanently Deleted User

    Yeah, i also joined this forum to ask for these same functionalities, all presented on Swiftkey for Android, and still missing on iOS. Particularly, i'm missing most whe number row on top (holding W key, for instance, will bring me the option to enter "2" or "W".

    1
    Comment actions Permalink
  • Avatar
    Subliminal5oh2

    Yeah, i also joined this forum to ask for these same functionalities, all presented on Swiftkey for Android, and still missing on iOS. Particularly, i'm missing most whe number row on top (holding W key, for instance, will bring me the option to enter "2" or "W".

    Thank you for your feedback iOS users.

    Understand that there are many differences between iOS and Android. The first and biggest hurdle being Closed-Source vs Open-Source.

    Source codes are imperative when developing an application that needs as many permissions as a keyboard.

    Understand that because Apple and iOS are closed source and set limitations very high for third-party developers. This causes issues to arise that wouldn't be a factor in Android.

    Also please know that this is a new version of SwiftKey and should be looked at as a beta. SwiftKey is attempting one of the most intensive crossovers of all time.

    Apple does not help in anyway to this, all they do is give the bare minimum up and leave the rest of their projects closed source. Most of these features will be available in time, but you have to give it just that, TIME.

    iOS has not been known for its willingness to give up attributes of its hardware, and because of this SwiftKey developers are half blind to issues that may or may not arise based on the new operating system they are attempting to become a part of.

    Your patience and understanding is appreciated and please make sure to read the post of Boberry up above for  more information regarding iOS development.

    Thanks and kind regards,

    Mike

    1
    Comment actions Permalink
  • Avatar
    Josh

    @Phillybizzle,

    Whatsapp just released an update today to make it compatibly with iO8. I've heard that update makes it more compatible with iOS8.

    0
    Comment actions Permalink
  • Avatar
    Permanently Deleted User

    Same questions here. I love this keyboard on Android, but i cannot say the same thing about iOS yet. Can you please add the feature to enlarge the keyboard?

    0
    Comment actions Permalink
  • Avatar
    Subliminal5oh2

    Same questions here. I love this keyboard on Android, but i cannot say the same thing about iOS yet. Can you please add the feature to enlarge the keyboard?

    Hello AirJonn,

    The iOS development team is very passionate about releasing a quality product. Due to the original restrictions of time and new ground for iOS, SwiftKey is still very new.

    Apple, has not been known for its willingness to open up its device to third-party applications such as this one.

    The are quite a few features that SwiftKey simply CANNOT have access to. (such as voice command, I believe speaker output, etc.)

    I can assure you that the relationship between Apple and SwiftKey is ideal for this kind of development, and you will see features from Android make there way over, eventually.

    Please, be patient and you will see more and more features come.

    Remember Android SwiftKey has been being developed for the better part of 5 years now. iOS SwiftKey has had less than half a year.

    Thanks for your feedback,

    Mike

    Sent from my SM-N900P | Android 4.4.4 | Tapatalk | SwiftKey Beta

    0
    Comment actions Permalink
  • Avatar
    Permanently Deleted User

    TouchPal and Swype are almost like on Android.

    Swype has an extra Number Layout. TouchPal has swipe up on top row to get numbers, down in lowest row for special keys and long press on return to bring up emojis.

    And what does layout have to do with closed source?

    SwiftKey on Android is great. I love it and want the same number layout, extra number row and emoji, etc. on iOS.

    1
    Comment actions Permalink
  • Avatar
    Subliminal5oh2

    TouchPal and Swype are almost like on Android.

    Swype has an extra Number Layout. TouchPal has swipe up on top row to get numbers, down in lowest row for special keys and long press on return to bring up emojis.

    And what does layout have to do with closed source?

    SwiftKey on Android is great. I love it and want the same number layout, extra number row and emoji, etc. on iOS.

    There was a short period of time to make it available, the iOS developers are working on it constantly, and passionately.

    The Android version has been in development for going on 5 years now while the iOS version has been there for less than 6 months.

    I wasn't attributing all of the shortcomings on iOS to closed source development, that is just a large part of it.

    While I'm not a developer and have limited knowledge of iOS, I can say that you shouldn't expect a perfect product immediately.

    Touchpal and Swype are in my opinion, inferior applications with very, very limited abilities with predictions far more off base than even the most obscure predictions from SwiftKey. That is purely my opinion after using all three, and forever returning to SwiftKey.

    My best suggestion is patience iOS users, I assure you I've rarely been disappointed by SwiftKey and I don't see them starting that trend soon.

    Another suggestion is to visit https://support.swiftkey.com and file a support ticket including any features and the priority in which they take toward your experience with SwiftKey.

    I hope that clears up my meaning to the third party development reference.

    Sent from my SM-N900P | Android 4.4.4 | Tapatalk | SwiftKey Beta

    1
    Comment actions Permalink
  • Avatar
    Permanently Deleted User

    @Subliminal5oh2:

    I've been using all of them. Prediction takes time to be learned for all keyboards. If you just switch and test. The results will not be good. You have to be go using them for a while.

    Prediction of Swype and TouchPal work great for me. I've never had any problems with that with any of them.

    1
    Comment actions Permalink
  • Avatar
    Subliminal5oh2

    @Subliminal5oh2:

    I've been using all of them. Prediction takes time to be learned for all keyboards. If you just switch and test. The results will not be good. You have to be go using them for a while.

    Prediction of Swype and TouchPal work great for me. I've never had any problems with that with any of them.

    With the exception of Swype (which I found unusable from the get go) I've used any other keyboard for at least a month before passing any kind of judgement.

    This includes ai.type, Google keyboard, Samsung stock, HTC stock, flexy, and just a few others.

    I still end up coming back home to SwiftKey everytime! It's just the best for my purposes.

    Sent from my SM-N900P | Android 4.4.4 | Tapatalk | SwiftKey Beta

    1
    Comment actions Permalink
  • Avatar
    Permanently Deleted User

    There was a short period of time to make it available, the iOS developers are working on it constantly, and passionately.

    The Android version has been in development for going on 5 years now while the iOS version has been there for less than 6 months.

    I wasn't attributing all of the shortcomings on iOS to closed source development, that is just a large part of it.

    While I'm not a developer and have limited knowledge of iOS, I can say that you shouldn't expect a perfect product immediately.

    Touchpal and Swype are in my opinion, inferior applications with very, very limited abilities with predictions far more off base than even the most obscure predictions from SwiftKey. That is purely my opinion after using all three, and forever returning to SwiftKey.

    My best suggestion is patience iOS users, I assure you I've rarely been disappointed by SwiftKey and I don't see them starting that trend soon.

    Another suggestion is to visit https://support.swiftkey.com and file a support ticket including any features and the priority in which they take toward your experience with SwiftKey.

    I hope that clears up my meaning to the third party development reference.

    Sent from my SM-N900P | Android 4.4.4 | Tapatalk | SwiftKey Beta

    I suspect this is because you are on an Android. I have swiftkey on my Nexus 5 and have been using it as my only keyboard since it was released, and I agree whole heartedly with you, that no other keyboard compares or comes close to comparing. On IOS however, there is a lot of disappointment. I can't see how the size of the keys would be limited by apple, when other keyboards are different sizes. Touchpal and Flesky both have audible feedback so it would seem that is permitted. Flesky has swipe left to delete, and touchpal has second characters on their keys so that's possible too, and finally Go keyboard has upper and lower case fonts. What none of them have is everything together and top notch text prediction which is what makes Swiftkey so great...on an Android. Predictions work great, but when they keyboard is layed out such that the word typed is so far off the actual word wanted, it just can't keep up.

    I have no doubt swiftkey is working hard to add features, but the risk remains that if people use it now and are turned off, they might find an alternative.

    1
    Comment actions Permalink
  • Avatar
    Permanently Deleted User

    I am so pleased to find this discussion topic, as it's something, for which, I've been looking to find answers for some time.

    Texting/Emails and What's App are a major part of my phone experience and I was thrilled when I discovered Swiftkey, which kind of kicked Swype, which I also loved, into touch.

    I love Swiftkey, which has, for me, revolutionized the whole experience of texting etc.

    I've introduced a number of friends to Swiftkey and they all love it and use it as much as I do.

    I've never, having seen the texting set up on Apple devices, been tempted to make the switch from Android and have been at great pains to explain the reasons why to friends who've tried to convince me I should, as I watch them furiously typing away with single letters and digits etc.

    However, I was fascinated when I found out that Apple would be adopting 3rd party keyboards and in particular Swiftkey in iOS8 and looked into it on YouTube and am awfully glad I did, as it soon became obvious, as others have noted that the experience on the iPhone is significantly different from that on the most basic Android device.

    Some of my friends have also been kind enough to download Swiftkey onto their devices, so that I could play around with it, none of them, unlike my Android buddies have been impressed,or interested in adopting it.

    The main problem for me, is the use of the stock Apple keyboard.

    And the issues are as follows:

    1. On Android, Swiftkey changes the keyboard, in particular allowing access to punctuation and numbers via a harder press on the main keyboard where you can actually see them there on the keyboard and there's no need to constantly toggle between two keyboards, wasting time in doing so, in order to access different characters.
    2. I find the use, in Apple, of upper case letters, which remain upper case, once you've started a sentence,  particularly vexing.

    On my Android keyboard, once I've begun a sentence, the letters for typing revert to lower case until I start a new sentence, or choose to write a whole word in upper case, for example.

    I'm aware that in the word suggestions in iOS8 are in lower case, when needed, but the keyboard remains stuck in upper case, regardless.

    Call me old fashioned, but that's not how I  would write on paper and I find it confusing to look at a bank of upper case letters, when my brain is telling me it wants to see lower case.

    I'm really hoping these issues will be ironed out, but knowing the grip Apple has on the world, in general, I'm not holding my breath! 😜

    My guess/suspicion is, that this has much more to do with Apple being in control of the situation than Swiftkey still being in the "developing," stage in iOS.

    We shall see!

    So, regardless of exhortations from friends and the temptation gnawing at me, on this, I'm determined to stay with Android and Swiftkey on my beloved Moto G as and until this issue is dealt with.

    And, if not, then it's a serious deal breaker in any debate about switching from Android to Apple.

    The glass, at the moment, is definitely half empty! 😜

    As for any attempt to contact Swiftkey,well I'll try the ticket approach mentioned above, but I do remember contacting them via their Webpage and getting a bizarre "reply," which bore no relation to the questions I asked and then ended up saying that I should not hesitate to contact them again,if I needed any further "help!"

    Well, some sort of considered reply would've been nice, in the first place, rather than the sort of stock nonsense we've all become so accustomed to in this day and age.

    Still, I'll give it another go 😜

    1
    Comment actions Permalink
  • Avatar
    Ryan P

    Hi Wildheart,

    Thanks for the post.

    There are a lot of factors involved but come down to a few main things. The Android app is nearly 5 years old, the iOS app is about 5 or 6 months. It takes time to build thing which our iOS dev team is working very hard on doing so.

    Android users and iOS users are used to different user experiences. It's not as simple as just making the Android app into the iOS app. There is user testing and product decisions involved.

    We are all excited to make the SwiftKey Keyboard for iOS on par with the Android one but in due time.

    I'm sorry you had a strange support experience. Most of the time any direct emails do not work as they go to unmonitored inboxes.

    Your best bet is to go to support.swiftkey.com and fill out the info and someone from our team will get in touch. I'm curious to what site you went to and got this funky response.

    Best,

    Ryan

    1
    Comment actions Permalink
  • Avatar
    SkuterPL

    Hello,

    Could you finally add comma on left side like it is on android version? It is very usefull for faster typing a sentence, another important missing thing is automatic space after sings like dot.

    I hope I will see it in near future.

    1
    Comment actions Permalink
  • Avatar
    Brandon O'Berry

    Thanks for the suggestion, SkuterPL. If you would be so kind as to visit the link Prado has provided in the past above yours, and fill out a Support Ticket, it would be very helpful.

    As a little insight: the comma was replaced by the emoji key to better match that of the stock keyboard. On Android, as I'm sure you're aware, the emoji key is embedded into the enter key; however, this is not as easy to achieve on iOS, and so has not been implemented in the same way.

    1
    Comment actions Permalink
  • Avatar
    SkuterPL

    so, on iOS you can't  move emoji to enter key by long pressing it?

    0
    Comment actions Permalink
  • Avatar
    Subliminal5oh2

    so, on iOS you can't move emoji to enter key by long pressing it?

    No, simply because the idea behind SwiftKey iOS is to make a fluid change from stock Apple keyboard to SwiftKey. It also caters to a different type of user. The Android and iOS apps probably won't ever be identical.
    1
    Comment actions Permalink
  • Avatar
    SkuterPL

    it's shame, it's very usefull for better typing.

    Okey so for automat space after sings I can expert that?

    0
    Comment actions Permalink
  • Avatar
    Subliminal5oh2

    it's shame, it's very usefull for better typing.

    Okey so for automat space after sings I can expert that?

    I'm not quite sure what you mean here.

    Also, I'm not at liberty to say exact changes being made, until they are made. Same with timelines, I can't guarantee or offer any insight as to what is coming, all I undoubtedly know is that the iOS team is very passionate about their product and are working diligently on solutions for common issues.

    1
    Comment actions Permalink
  • Avatar
    SkuterPL

    On android when I write some sentence and on end of it I will write dot, automactly I get space and I can write next sentence without click space button, on iOS I can't do this.

    0
    Comment actions Permalink
  • Avatar
    Brandon O'Berry

    On android when I write some sentence and on end of it I will write dot, automactly I get space and I can write next sentence without click space button, on iOS I can't do this.

    I'm actually pretty sure (don't quote me) that this was an intentional move by SwiftKey. Why? I'm very uncertain (which is why I'm " pretty sure "), but it's my best guess. I'll see if I can't squeeze out an answer from one of the staff for ya, if they're allowed to divulge such a reasoning. [emoji6]
    1
    Comment actions Permalink
  • Avatar
    Ryan P

    Subliminal said it best.

    But I will say it again.

    iOS users and Android users are not the same. They expect different things on different platforms. You can just port an app from one platform to the next and expect people to 'get it.'

    iOS users having only used the iOS keyboard for so long are used to certain things working a certain way. As we build out the iOS product more we have to take into account how iOS users interact with their device and keyboard.

    As roadmaps often change, I can't say what we are building and releasing, but feedback will always be recorded and will shape the product.

    So, even though things may not be in the product now - even they are in Android - this does not mean they will never make an appearance (even though it might come in a slightly different form).

    The possibilities are endless.

    As part of the community team, we are always listening and relaying quality feedback to the dev teams and product managers.

    Best,

    Ryan

    1
    Comment actions Permalink
  • Avatar
    Permanently Deleted User

    I vote that team add an option for current dot key be able to be mapped to comma as default hit.

    Double hit gives us dot.

    I understand there maybe users who want dot to be there easily accessible. However, there are other people like myself who want to access comma fast.

    Sent from my iPhone using Tapatalk

    1
    Comment actions Permalink
  • Avatar
    SkuterPL

    here I can find page for vote it?

    1
    Comment actions Permalink
  • Avatar
    Subliminal5oh2

    You can visit http://support.swiftkey.com and fill out a feature request, these forums are meant for trouble shooting and discussions.

    1
    Comment actions Permalink
  • Avatar
    Permanently Deleted User

    I came on to this forum looking for basic answers to questions such as:

    When will Swiftkey iOS have arrows and numbers like on Android?

    When will Swiftkey iOS allow for multilanguage support like on Android?

    When will Swiftkey iOS allow switching between languages like on Android?

    I don't mean to be rude, but all I'm reading is excuse after excuse. It is now MAY 2015! Where are all these alleged changes in the works that the iOS team is "passionately" working on?

    Swiftkey for iOS is a complete joke compared to the Android version. I use Swiftkey mainly because it has good predictive capabilities, has the ability to change the keyboard layout to include arrows and numbers, and has the ability to switch easily between languages. Other than its predictive capabilities, which unfortunately apply only to English, the iOS version has nothing else.

    For how much longer should iOS users be patient, a year? Two years?

    The reality is Apple is a pain to work with but if you're not going to release features in a timely manner, don't patronize your users with calls for patience to justify a subpar product.

    1
    Comment actions Permalink
  • Avatar
    Ryan P

    I came on to this forum looking for basic answers to questions such as:

    When will Swiftkey iOS have arrows and numbers like on Android?

    When will Swiftkey iOS allow for multilanguage support like on Android?

    When will Swiftkey iOS allow switching between languages like on Android?

    I don't mean to be rude, but all I'm reading is excuse after excuse. It is now MAY 2015! Where are all these alleged changes in the works that the iOS team is "passionately" working on?

    Swiftkey for iOS is a complete joke compared to the Android version. I use Swiftkey mainly because it has good predictive capabilities, has the ability to change the keyboard layout to include arrows and numbers, and has the ability to switch easily between languages. Other than its predictive capabilities, which unfortunately apply only to English, the iOS version has nothing else.

    For how much longer should iOS users be patient, a year? Two years?

    The reality is Apple is a pain to work with but if you're not going to release features in a timely manner, don't patronize your users with calls for patience to justify a subpar product.

    I can understand your frustration, but there are expectations that people seem to have that have never been said by us at SwiftKey.

    iOS is not Android and it never will be. If you jump from one platform to the other, I would believe there are hardly any apps that work exactly the same on each platform.

    Building the iOS app is about taking into account how iPhones users are used to using their phones and building off that. This is not an excuse for not adding features that are being discussed here.

    If anyone wants to submit a proper feature request, I've pointed them to support.swiftkey.com where we organize all these and then prioritize them with the iOS devs.

    Currently, this is a theme store and more themes, which is currently being built and in beta.

    As far as languages, the iOS app does support up to two languages at the same time and provides predictions in two. You can (like the Android app) change the layout and use the spacebar to switch.

    The iOS app currently supports two of the three questions you were seeking answers for. These were part of the app when it launched.

    As for your arrow keys, please submit that as a feature request and it will be recorded.

    I am no means trying to patronize anyone with saying be patient. I am not here to promise things to the community that I cannot guarantee.

    I still stand by the fact that our iOS team is working hard and passionately building up the product. I am currently sitting next to them as I write this.

    1
    Comment actions Permalink
  • Avatar
    Permanently Deleted User

    That comment was about what I expected, although I praise your politeness.

    It is NOT true that two of the three things I discussed are possible on iOS. I use Asian language features extensively and if you happen to type in Mandarin (which, by the way, is only the third most spoken language in the entire world or so...), you are SOL, as they say. Same goes for Japanese, Korean, etc. etc.

    So to correct what you stated, only one of the three things I discussed is possible with the exception of a very limited range of supported languages.

    Regarding the arrow and number features of an expanded keyboard, I won't submit the feature request because countless others have already and there has been zero progress made, so I suppose I will check back in six more months to see if your developers have finally started to listen to their consumers. Until then, this keyboard is not a good choice (or a choice at all) for those who want to use more than one language as they type (with few exceptions for a short list of supported languages).

    1
    Comment actions Permalink
  • Avatar
    Ryan P

    Ahh, well this is where it gets interesting. Technically, we do support multilingual use but just not those languages on iOS, which yes, as you stated puts us at a disadvantage.

    Thanks for your feedback. I assure you we take note of everything.

    See you in 6 months time (maybe sooner).

    Cheers,

    Ryan

    1
    Comment actions Permalink

Please sign in to leave a comment.