Why are the iOS apps so badly designed?
Okay, so there's no simple answer that kind of a question, but I'll explain what I mean in asking it. For the most part I enjoy the PC and Mac versions of Logos 5, but whenever I pick up my iPad or iPhone to follow along, I find myself constantly annoyed at how it's designed. I've been using it for a long time and it does allow me to do a lot from a practical point of view. So that's good. And for things I feel need adjusting I have cast my few votes on a number of suggestions which I'm sure will be heard.
But the app really does cry out for a full redesign. I don't understand why the iOS apps lack so much of the basic functionality the computer versions do. And I know it's not because of technical limitations. Although I could, I won't list every difference because it takes about five seconds of looking at a computer version of Logos to see the giant gulf between the two. Under iOS we have no book organisation system, barely any way to prioritise resources for study, and a UI that has looks and operates like its been designed by 12 different people, to name a few.
This post isn't a flame bait or a "I don't like the app because it lacks my favourite feature" rant. I just feel like the iOS apps are by far the weakest part of the Logos lineup. For something like Faithlife or Vyrso, the current apps do the job. But other developers put the iOS version of Logos to shame. It feels like a badly designed toy by comparison. There's just no need for such a dumbed down version, and is why I hope the Logos devs are thinking hard about starting one from scratch. If they aren't, then hopefully this post will make them consider the idea.
Comments
-
Don't bellyache. Name your issues. No one except for your therapist can deal with the way you "feel" about the app!
0 -
Joel.. If you feel its bad now, just as well thou didn't try it 12-18 months ago, seriously, there have been giant leaps forward, much more productive for my workflow/study
Never Deprive Anyone of Hope.. It Might Be ALL They Have
0 -
I just have hope, soon or later, they will reconsider how important is the iOS usage of LOGOS. Maybe it is not so simple to see...but I noticed so many ppl in the forum, saying they mainly use Logos as an app, so WE ALL need a good one UI app.
I would even consider to pay for a well made 1st class app.
0 -
Why are the iOS apps so badly designed?
Really?
- The iOS apps aren't designed poorly. To the contrary! Certainly there are some features which would be nice to be added, but that isn't the same thing as saying the current apps are "designed poorly."
- An iPad IS NOT a computer. A Computer IS NOT a tablet. They have different FORMS and will therefore have different FUNCTIONS.
- An iPad does not meet the minimum requirements for L5. You shouldn't expect the mobile apps to be the same.
- I agree we have no reason for a "dumbed down" version of L5... BUT THAT IS WHAT YOU ARE ASKING FOR! The mobile apps aren't a "dumbed down" version of L5. They are distinct apps that hold their own. Almost all of my reading is done on my iPad. It is superior in most every way for that function. Nearly all of my "study" and "research" is done on my MacBook or iMac. L5 is superior in most every way for that function. Each part of the body has it's place. [;)]
- If you really want a computer/tablet, pony up for a surface PRO 2, or really pony up for a ModBook. Then you can run L5.
0 -
So a few things. The first is that in my past I've been a software developer. I know a good UI when I see one. The Logos iOS app doesn't have a well designed UI. That's not debatable. Do some research and you'll see that by all UI design standards it fails quite badly.
The iPad is a computer. It just runs a different OS. Sure, you can't have an app that is built using bits from a PC operating system's UI. But you can create an app that works the same way, even down to the menu. Many apps do this. The 'minimum system requirements' are a moot point, since as you point out alabama24, the iPad's system is different to a PC. In fact there are a ton of different factors involved. But if you're saying that an iOS device can't handle a normal UI, display text and create a library index, you might want to get on the phone and call all of the other app developers who've managed that quite easily, and tell them what they've achieved isn't possible.
Can I just say that I don't want Logos 5 on a tablet. I just think the current version is pointlessly limited, with a crazy amount of functions missing. I have been using it for years, so yes I have seen the improvements to it. But some of the most obvious things are still missing. And as I've said, it all works in a very non standard way. It was an oddly designed app in the first place, and it's still that with stuff bolted on to that base. That's why I say it needs a full redesign.
And for those who ask for an entire list of 'what's wrong', I can add that, but as I said, that's not really the point of this thread, since I'd also be commenting on what's odd with the UI.
0 -
And DHG, I may add a list of things, but the Logos devs aren't morons. I'm not whining for a list of features. I'm asking they go back to the drawing board because I know they make something better.
0 -
I think alabama got "hot" for so many other complainers around. No?
I agree that the UX/UI is very lacking for some minimum levels of service we are kind of used to see in other apps (ie why I can do "download all" and I cant do "delete all" for any specific selection?)
I agree that devs are good devs, especially from the time they talk about the beta or the app features, and so I hope they can pour some more time in the UX/UI (re)design like Joel said.
0 -
I too have had experience as a developer and I am well familiar with interface design. I think the new UI on iOS and Android is terrific, esp compared to the older version. There are a few things I would change, but overall it is a good design and is totally consistent with the platform.
BUT, this conversation is too generic. Without stating specifics, no one can address your issues. There are lots of good ideas that could be implemented, but you will need to make specific suggestions if you want them addressed.
0 -
I think the metric of a good interface and feature set is simply attractiveness to users in general ... otherwise known as 'downloads'/no-deletes.
Personally, I agree the UI is not intuitive. Even worse, inconsistent across platforms (I'm really not sure why the Logos google platform consistently lags the iOS one, from what I can see).
But having mucho apps on my iPad (like everyone else), and being a former developer (like everyone else), my impression is very few apps are well designed. I'm not even sure why. My guess (and a serious one) is that most devs loved game-playing with hidden doors, etc. Prettyboy apps are far more important than ease-of-use.
But proof in the pudding ... come Sunday morning, the Logos app isn't my reach for, trying to follow the pastor's key points. Laridian's considerably faster (UI-wise) followed by OliveTree. We're talking 'the Bible'.
Reading-wise, Logos is my fav.
EDIT: Thinking about this some more, when I'm reading on my Logos app, I actually pull up Laridian app to check out the Bible text (which is far less powerful than Logos). Also reading on my Kindle app, I use the Laridian for Bible text, etc. I just don't have the patience for Logos. Too slow use-wise.
"If myth is ideology in narrative form, then scholarship is myth with footnotes." B. Lincolm 1999.
0 -
Randy, I wouldn't consider the UI fantastic. The Logos iOS app gets trumped very easily by a more standard design. Try PocketSword by CrossWire for iPhone sometime. It's an iOS6 UI, but being more standardised, it allows me to switch from bible to commentary to dictionary and between all of my resources very quickly. It's not a perfect UI and the app could learn a thing or two from Logos in terms of features and options, but trying to pull that off in the current Logos app is maddening. Logos' current UI is fancy pants non standard when it has no reason to be, other than to look funky. It's slow to use (both technically and from a usability point of view), limited in basic functionality (like swapping between stuff quickly or bookmarking), and is missing a huge chunk of features that are meat and potato features for Logos on a PC, like being able to order your library with the same options. Features can obviously be added in (and should have been included a looooooong time ago, truth be told) but the main issue is the app needing a redesign, so it's a whole lot less restrictive in use.
BUT, this conversation is too generic. Without stating specifics, no one can address your issues. There are lots of good ideas that could be implemented, but you will need to make specific suggestions if you want them addressed.
Maybe. I'll come back and list a few more examples of how the Logos UI could be improved. But honestly, if the devs can't figure that one out for themselves, nothing I say will help them understand. I'm just here to say, "Come on guys. It's time to think 'next level' for Logos iOS, because it's far from perfect."
0 -
But having mucho apps on my iPad (like everyone else), and being a former developer (like everyone else), my impression is very few apps are well designed. I'm not even sure why. My guess (and a serious one) is that most devs loved game-playing with hidden doors, etc. Prettyboy apps are far more important than ease-of-use.
I'm sure there's truth in that.
On a side note, UI design isn't easy, but there is a reason most guys stick to established conventions, and that's because they've been proven to work and can be expanded on easily with consistent, predictable design. Logos' iOS UI feels pieced together with a bunch of random ideas. For example, why swipe up for a popup menu that is the same as a button on the down swipe menu? Why does the iPhone have a cancel button on the menu but not the iPad? Why can I swipe down to dismiss the menu on the iPad but not on the iPhone? There's no consistency, because it's a pieced together UI instead of a standard one I can use predictably.
0 -
OliveTree BibleReader is much better on iOS. The Resource Guide is much better than say the Exegetical Guide for example.
However Logos has made huge improvements over the past 18 months. It is infinitely better than it was. More improvements I am sure will come.
So I tried OliveTree again recently with a substantial amount of resources. Loved it, but they do not have the resources available that Logos has - and on the Catholic resource side, well, OT has not even started!!
So agreed Logos iOS can improve, but it ain't terrible and you need to take the (no pun intended) whole package into account - software and resources.
Regards,
Richard.
0 -
Personally, I agree the UI is not intuitive. Even worse, inconsistent across platforms (I'm really not sure why the Logos google platform consistently lags the iOS one, from what I can see).
I'm coming from the Android platform. I'm only somewhat familiar with the iOS version having toyed with it a bit on my older iPod Touch, but the new UI is seems pretty consistent with both platforms. Though, I'm probably missing a lot of nuance since I'm not a hardcore iOS user. From what I understand though the apps are at near parity on both platforms.
But proof in the pudding ... come Sunday morning, the Logos app isn't my reach for
That's definitely a good indicator, but it also has a lot to do with what your most familiar with and comfortable with, I think because have a number of bible apps on my tablet (and many others I've tried and dismissed) but I tend to reach for Logos. With the exception that our church (ELFBC) uses YouVersion to broadcast sermon notes, so I'll use it to look at the notes and switch to Logos to follow along in the bible. Where I run from Logos is when there is no wifi available. I go straight to OliveTree.
I'm going to have to take some time to have a better look at Laridian after reading your continual high praise of it.
0 -
Randy, I wouldn't consider the UI fantastic. The Logos iOS app gets trumped very easily by a more standard design. Try PocketSword by CrossWire for iPhone sometime. It's an iOS6 UI, but being more standardised, it allows me to switch from bible to commentary to dictionary and between all of my resources very quickly. It's not a perfect UI and the app could learn a thing or two from Logos in terms of features and options, but trying to pull that off in the current Logos app is maddening. Logos' current UI is fancy pants non standard when it has no reason to be, other than to look funky. It's slow to use (both technically and from a usability point of view), limited in basic functionality (like swapping between stuff quickly or bookmarking), and is missing a huge chunk of features that are meat and potato features for Logos on a PC, like being able to order your library with the same options. Features can obviously be added in (and should have been included a looooooong time ago, truth be told) but the main issue is the app needing a redesign, so it's a whole lot less restrictive in use.
Thanks for posting back with more detail.
Again, I'm more from the Android camp and am only somewhat familiar with iOS, but the interface is very standard for an Android app and I thought it fit very well within iOS also. Now, I'm completely in agreement that it could do more to make access easier, but as far as what exists at this moment it seems fairly standard to me across both systems for the most part. It's just incomplete (and they are most definitely working on that). For example, I've long wanted more, more, more gesture support to add easier access to features (two finger swipes left/right for next/prev chapter, three fingers for next/prev parallel resource, two finger swipe down for TOC, etc., etc). I've posted this before, but here's link to an OliveTree demo that shows how gesture support can make a huge difference in ease of access.
Is that what you are saying? Not that the app as is is necessarily broken but that it needs more fine tuning to be complete? Logos culture, esp in the desktop and resource production seems to be hugely focused on the big stuff, the next big feature/resource. While they minimize or put off all the fine details. Unfortunately, it's all those fine details that turn a useful application into an application that is a joy to use. The apps have made huge strides over the last year. The developers have done awesome work are still pounding out the features. Hopefully, they can find some time to add a little more fine tuning.
0 -
Randy ... my reference to download/no-delete is simply that users have opinions; but results count. Results that none of us have access to. For all we know, the Logos app is downloading so fast, Bellingham is out of stock. I do know that in corporate-land, lack of results is rarely traced to 'the product'. More often 'must be the marketing'.
But app designers almost always track design-guidelines initially ... until the crazy users want functionality. So the growth of inconsistencies.
I'd not recommend Laridian from many standpoints; I only mention them because when 'criticizing' Logos, people want DETAILS!! So the easiest way is to simply reference a competing product/store.
Laridian is easy because the menu is always there (optional). The cutie apps (Kindle, Logos, etc) want to hide the interface (certainly a good idea), and not allow the user to choose (bad idea). Hidden interfaces make sense, if the app is your only app. But in my case, I use 5 or 6 readers, 7 or so imaging apps, and probably 20 or so synth apps. Moving across apps demands devs that aren't so cutie-pie oriented.
"If myth is ideology in narrative form, then scholarship is myth with footnotes." B. Lincolm 1999.
0 -
I'm going to have to take some time to have a better look at Laridian after reading your continual high praise of it.
I've tried Laridian's PocketBible on my iPad several times because I have several licenses in their format from my Palm OS days, but I find their text layout to be difficult for me compared to Logos. PocketBible doesn't support fully justified text, but has a jagged right margin. The verse numbers 32 are the same size as the 33 text, and footnote marks are *underlined *asterisks. Section titles in Bibles are large and intrusive, and poetry formatting doesn't have proper indenting. All of these things make reading in PocketBible uneasy for me (At least in the ESV. I haven't examined other Bibles closely, but I imagine they're the same).
I do find the slowness of Logos annoying sometimes, especially when I open the app and I have to wait for the library to sync up before it starts responding to taps. But in general, I find the Logos interface pretty usable on the iPad (the iPhone interface is a bit fiddly for me). I especially like the two-finger history swipes, and I find myself wanting to use them in the Kindle app.
MacBook Pro (2019), ThinkPad E540
0 -
Considering that a year ago the iOS app was basically akin to the kindle. One book at a time, only good for reading, I feel like its come a long way. Room for improvement? sure. But I am not unhappy. Its quite a bit better than it once was.
You can be certain that the new versions coming down the pipe will bring even more improvements.
Finally, I grow annoyed with my professors when they ask questions that require me to guess what they are really thinking on tests. I'm certain its the same for developers. You said and I quote "If the devs can't figure that one out for themselves nothing I say will help them understand". I feel like your insinuating they should be able to read your mind here as well. Perhaps one day we will be able to do such things, but for now we can't (fortunately). So until then perhaps posting things in the suggestion forum to the effect of "Suggestion: Improve the ease of switching between books on iOS". Or something like that and then explain how you think it should work.
Then we (forum users) get to weigh in and say what we think, and the devs decide if its worthy.
Saying "You're product is terrible, but if you want to know why you must develop the ability to read minds" helps no one
L2 lvl4 (...) WORDsearch, all the way through L10,
0 -
-
I actually liked how the app is designed, it does have a longer learning curve then other apps but once you learn the gestures and how it works, it's quite amazing how powerful the app really is.
I do agree that they has some improvements to make, probably they have to label/organize certain functions a little better. An online guide explaining how to use the app would be great. If there's one feature I wish they implement it would be allowing us to adjust the highlighted verse range; add, reduce, add other verse from the other books. I really enjoyed seeing that little yellow note and when you click it, it shows the notes you wrote as a pop up.
0 -
If there's one feature I wish they implement it would be allowing us to adjust the highlighted verse range;
I'm not sure what you mean by this. Do you mean "adjust the length of a highlighted passage (bible or else)? If so, you can ADD to the length, but not subtract. If you highlighted too short of a passage, you can highlight the added section and overlap with the rest of the passage and the two will merge... but make sure you are using the same highlighting pen! If not, a new highlighting note will be created instead of extending the existing one.
0 -
I think alabama got "hot" for so many other complainers around. No?
I was upset with someone for rude and inconsiderate behavior. It is one thing to suggest improvements. It is quite another to come in here and behave as the OP did.
Seriously? My original post wasn't even remotely rude. What did you find so offensive about it?
0 -
Is that what you are saying? Not that the app as is is necessarily broken but that it needs more fine tuning to be complete?
Yeah, pretty much. It certainly isn't broken (in some ways it's great!), but I think the app needs more than fine tuning. It has some really badly designed elements, and that means going back to the drawing board to redesign the base. Tacking on features won't help to resolve the things that I put under the category of bad design. That's why I keep harping on about how this thread isn't for feature requests. I know where to do that, and that's a place where they can be voted on and tracked easily by the devs.
Christians are really good at defending developers and what they make. But to anyone that's been paying attention to what's possible on mobile platforms, Logos apps could hold their own against their PC counterparts quite easily. It may sound harsh or sensationalist throwing around terms like, 'badly designed', but that's just what the mobile apps are in many ways.
I'm just hopeful for more. The Logos devs should move on from using feature requests as the only way to improve Logos on mobile, and instead look at taking as much as possible from the PC, and building it into a much more flexible base.
0 -
I'm wondering about ones perspective. Historically (the last few years), the feature flow would be from Logos4/5 to a mobile (the latter being a subset of the former, with users demanding a greater look-alike).
But I wouldn't be surprised if the future is the opposite direction; the customer entry is the mobile version (remembering the 'customer' is supposed to buy books ... not just help design free software).
So, I'd suspect either Logos would need to introduce an easy-to-use mobile version, paired with a high-power version, or keep the lid on the present one.
I'd like to say the Faithlife one is the easy-to-use version, but I deleted it after an hour or so. Too complicated for me and didn't respect our cellular line.
I kept the Vyrso, Noet, Bible! and Biblia. My favorite, oddly enough, is Biblia. I'm looking forward to a Japanese one. Mmmm, that would be so good.
"If myth is ideology in narrative form, then scholarship is myth with footnotes." B. Lincolm 1999.
0 -
Seriously? My original post wasn't even remotely rude. What did you find so offensive about it?
For starters, read the title of your thread!
Why are the iOS apps so badly designed?
If you have specific suggestions, feel free to make them. If you are the programming master par excellence, apply to work for Logos and "fix" what [you think] is broken. How can coming in here trashing the work of the programers (especially when you haven't suggested a single improvement) be considered anything other than rude and inconsiderate?
Personally, I think there are many areas where the app can be improved... but I certainly don't think that it is "so badly designed." I use it every day and think quite the contrary.
0 -
There's just no need for such a dumbed down version,
I very much would like to hear specific complaints; it's very hard to just start-over based on your broad complaint. We have the same people -- what if our next design isn't any better? I think we need more detail in order to address your concerns.
I do confess that we are at a bit of a disadvantage organizationally, compare to starting completely from scratch: when we designed the mobile apps we had to accommodate our existing user base, our existing data and technology, etc. Mobile devices have far less memory and power than desktop computers, and people (rightly) have different expectations for apps on mobile devices.
We didn't feel at liberty, though, to throw away some of our data, re-build our entire library, and ignore existing user data.
Examples:
- A built-from-scratch mobile app would probably ignore versification, and use a simple (fast, low-memory footprint) versification scheme. John 3:16 is John 3:16. Logos has built, over twenty years, support for complex reference ranges and data tables that handle the versification differences in ancient manuscripts, other language Bibles, etc. This code takes longer to run; the versification data tables are larger than 20 megabytes. All of our existing Bibles support (correctly) their own versification, and expect the app can map things. But when the iPhone arrived with custom apps, 20 megs was the maximum size an app could be -- code, data, everything! -- and be delivered over a cell connection. We had to do some compression, internal hacks, etc. just to support our existing books, and we still don't support all the functionality on mobile.
- Our books have rich layout and typography support. Many 'built-from-scratch' mobile apps simple use a rich text box, or HTML control, to display a single chapter at a time. We have to support a complete custom text display engine in order to display our 40,000 existing resources, many built more than a decade before the iPhone existed. Compare PocketSword's iPad display (http://a4.mzstatic.com/us/r30/Purple/v4/d2/5d/a5/d25da574-e953-d6c0-9e96-ed89f7cf8b9d/screen480x480.jpeg) to our Faithlife Study Bible (http://a1.mzstatic.com/us/r30/Purple6/v4/e2/1f/1f/e21f1fee-972c-8e09-8dde-b5684037d58c/screen480x480.jpeg). PocketSword appears to use a generic system control for text display. That's fast -- but I'd argue not as useful or elegant as FSB's.
- Our users expected their notes and highlights to work on mobile. Our note and highlighting system is sophisticated, cloud-synced, granular enough to work at the character level, rich in formatting options, and adapts automatically to resource updates which insert or delete text, messing up character counts. Most built-from-scratch mobile apps tie notes to whole Bible verses (in one global versification scheme) and only offer simple solid color highlighting, which is fast, flexible, and easy. If I was building a mobile app from scratch, I'd do that too, but we had to support our users' historical data.
I hope this doesn't come across as defensive; I don't feel the need to be defensive. (Especially since the all time rating for our Bible! app is 4.5 stars from 37,000 users, to PocketSword's 4 stars from < 1,000. <smile>) I'm just trying to explain how we got here.
We would love to make the app more useful, and easier to use, and if you give specific input we can address your specific concerns.
0 -
(ie why I can do "download all" and I cant do "delete all" for any specific selection?)
We don't offer Download All for resources intentionally; most of our base package customers have hundreds of resources, and many, many of our customers have thousands. On earlier iPhones we would use all of the available storage; even now that button would make it too easy to fill your phone's space and even to blow past the limits of your data plan.
We offer control of what is downloaded via the Library in the desktop software, but think we should hold off 'Download All' on the mobile app until more users would find it useful and not a super-dangerous/expensive button to press. (I suppose we could add warnings, confirmations, etc.... we can look at that.)
0 -
(ie why I can do "download all" and I cant do "delete all" for any specific selection?)
We don't offer Download All for resources intentionally; most of our base package customers have hundreds of resources, and many, many of our customers have thousands. On earlier iPhones we would use all of the available storage; even now that button would make it too easy to fill your phone's space and even to blow past the limits of your data plan.
We offer control of what is downloaded via the Library in the desktop software, but think we should hold off 'Download All' on the mobile app until more users would find it useful and not a super-dangerous/expensive button to press. (I suppose we could add warnings, confirmations, etc.... we can look at that.)
Actually... You do offer "download all" (Which I routinely warn against) [;)] Paolo was asking about "delete all."
TIP: the "download all" button is hidden. To make it appear, pull the library page slightly downwards from the top. Actually using the "download all" should be cautioned against unless you absolutely must. You can still take advantage of the button, however. Filtering your library for a user tag, for example, will allow you to use the button to download that subset of your library.
0 -
I understand your concern about Download All, but still...I go using logos on iPad for weeks, without turning on a PC. That is why I would love (pay) for a mobile app which doesnt need any PC to operate fully and completely.
anyway, thx always for your time, answering us. seriously!
0 -
Just a few replies here, because the quoting on this forum is really bad (and the entire forum doesn't work on under iOS... somewhat ironic).
For starters, read the title of your thread!
That wasn't rude. Blunt, yes. But if a person like me thinks the apps are badly designed then the title is pretty much on par. Anyone who thinks any part of my post is rude is clearly enjoying their first week on the internet. I know rude, and my post was nothing of the sort. I just didn't sugar coat it with diplomatic language. But clearly we just disagree. Moving on...
If you are the programming master par excellence, apply to work for Logos and "fix" what [you think] is broken. How can coming in here trashing the work of the programers (especially when you haven't suggested a single improvement) be considered anything other than rude and inconsiderate?
Ah, the old, "If you can do better get a job at Logos and magically change everything.", as if that's both God's calling for me and the way the world works. Also, I didn't say I was a master programmer. I said I'd been a software developer, meaning that I'm not ignorant to much of what goes into app development. And for the record, I have suggested some improvements. But I'll make a giant list soon.
0 -
Hey Bob, I appreciate the detailed reply and the info about why you guys have taken the steps to get where you are. Your post doesn't sound defensive at all. As much as I feel parts of the app are badly designed, I am also asking the question, "Why?" So, thanks
Obviously there's a certain part of the app that I wouldn't want to throw into the 'badly designed' pot I mentioned in my initial post- I can see you guys have worked hard on the engine side of things! (although I do wonder at the speed of a few things in it, but that's a side thing). For me it's the usability of the app, from a UI perspective. I have no complaints about text formatting. I recognise PocketSword isn't a wonder in that department or has to deal with what Logos does.
So here are a few thoughts. I expect this thread will momentarily fill with comments from people about one thing or another. That's not why I've posted this. It's for you guys to consider. I've lumped in some basic things that are pretty unimportant in the grand scheme of things, but some of the points are pretty much what I think are the main issues.
- Only four methods for organising a library, and those four lack the fifth on the PC (Most Used). No collections. No series. No prioritising of resources, or cloud syncing of either. No organising by type. No organising by downloaded. No rating or tagging in the app. Searching is good, but isn't always helpful when you have a large library to look through. Most importantly, aside from searching there is no filtering of resources! So, dealing with a library with more than a few books isn't great.
- I'm not sure if there's a technical reason for this, but for resources like the ESV there are no inline (or otherwise) strongs/louw-nida, or manuscript display options.
- Searching options are pretty basic. Even PocketSword has a fuzzy search
So onto the big one. The general UI. This is all about what makes the app confusing to use, as well as restrictive in use.
- Button layouts and menu options are inconsistent between the iPhone and iPad. (this is a minor quibble)
- The three and four line icons look almost the same. Sometimes I have to do a double take to figure out whether I'm opening the side menu menu, choosing from a table of contents or something else, because the resource name is hidden. The whole top menu and the way it changes when it appears and disappears is inelegantly designed. Because it looks like the four line icon is shifting to the left when the resource names appear, it's hard to figure out at a glance. I have figured out hundred of UIs for apps and programs, and even I get caught out by it from time to time. I can see it's a similar design to iBooks, but it's nowhere near as logical to figure at a glance.
- The down swipe buttons have options duplicated from the up swipe menu. For example, the share button has sharing options, but also a random bunch of options that don't belong under it, instead duplicated from the up swipe.
- There's no way to add a folder under mobile favourites. This would be fine if the favourites were per resource, but since they aren't, this menu could get really messy when a computer isn't involved to clean things up.
- When you use the 'back' button on the top left, there's no indication as to which resource it is you've travelled back to, for the reason mentioned above (the name isn't visible). It is cool you can hold down on it to bring up the history, but I wonder how many people know you can do that (I only just found out!) . Obviously I could just go through tools -> history. But, even that looks different from the history view from the back button! It's that kind of inconsistency that can be frustrating, especially when you've been off using other apps and have forgotten Logos' little quirks.
- To expand on the above, the Logos app's UI feels like it's had lots of little features bolted on to it. Things are inconsistent right throughout the app. Things becomes frustrating over time because it's more about learning how each page works on every device, instead of being able to rely on consistency throughout the app. That's why in this thread I've mentioned a more tried and tested UI design, that allows you to expand things with consistency. Right now there are lots of little shortcuts seemingly hidden away in the app, with their own little way of working.
- No linking of resources when using a split screen.
- No preferred dictionary, or commentary.
- To go with the above, the whole multiple resources for study is really hard to use. If I have a bible open and I want to use a dictionary to look up a word in front of me, the process is frustrating. I can open a dictionary and search for a word (if I remember I need to click on the page to bring up the search box, and not click on a line icon, which is mostly useless). But if that word is right in front of me I can search the built in iPad/iPhone dictionary by holding on the word (great!), or I can do a search, which means I need to choose the resource I'm currently using (it always defaults to 'Entire Library') and look through the list of results to find a basic definition. Then I need to hit the back button to go back to where I was. If I compare this to PocketSword, I type the word into the dictionary and I'm done. Then I click back onto the bible. It's not perfect, but it's fast and not at all confusing along the way. And, I can go back to my commentary, dictionary, and look up the same word in multiple dictionaries too without much effort. There's a reason I reach for my laptop, and this is one of them. Logos' app UI is just slow to use, and makes the task of quickly jumping between multiple resources (that just aren't aware of each other) require a lot more thought than it should.
I'm not going to say too much about anything else, because that last point is probably the main one I wanted to make. The general idea is this. There are some annoying aspects of the Logos app, and there are some missing options- both listed. For me the part I consider to be bad design is how hard it is to move around the app when you're moving between resources with some speed. It's akin to drawing a masterpiece with boxing gloves. I'm sure a lot of it would possible, but it'd be a heck of a lot harder to do than it needs to be.
I have no problem if you guys have the same team. The app has come a long, long way. Props to you guys for that! But I'd really like to see a rethinking of the UI. You might have garnered lots of positive ratings for it, but whenever I get that little popup in the app (kind of annoying, but that's another thing
) that asks if I like the app, I answer no to the yes or no question, because I'm often in the middle of being frustrated at it. If there are people like me out there, then there's a better design even still, despite the improvements. I hope that makes sense.0
