We’ve been dealing with many many different apps. App quality and usability are always our core values we never settle for less.
There are some common UX mistakes that engineers often overlooked. Getting these discovered and handled, one can build greater apps.
Get ready, here are our top 10:
10. Long text is too long in a text field
You’ve probably met this before. Long text can be really loooooooooooooooooooooooooong.
It’s not the text’s fault.
It’s the text field couldn’t handle that.
Yet, there are ways to deal with that:
- Truncate the text.
- Overflow the text field, make it scroll.
- Expand the text field.
- Limit the text length!
Get crash reports from Sentry
We have been using Sentry for collecting crash reports and stack traces for our front-end js, Python, and Rails applications. It is reliable with affordable pricing. Simple to setup with it’s open-source SDK.
However, there’s a fundamental problem when it comes to iOS.
What? No symbolized data returned?
Sentry only returns the crash report with a piece of memory address but not a meaningful method name.
As an iOS developers, you should have noticed that it requires a dSYM file to symbolize the stack trace. It helps to identify these addresses with the appropriate dSYM file.
We thought we can upload dsym files and get symbolized information returned when Sentry claims it works on iOS.
Unfortunately, it is not the case:
No one can understand the iOS Stack trace with memory address only. Proper support of dSym is needed.
(BTW if you can debug with memory address, please consider joining us.)
One of the possible solutions is to fork a piece of Sentry code and get our hands on it, but we don’t want to get into the complexity.
Instead, we write a micro service that will reply to a Sentry notification with de-symbolized stack trace on Slack, here is what we did.