Hacker News Reader

Comment by DigitalSea | Hacker News Reader

It would have been nice to hear how they went about solving all of the different device UI issues they ran into. Looking at the screenshot in the article, there seemed to be a lot of inconsistencies amongst devices. How did they come up with a solution to fix each issue? Did they target screen sizes and pixel densities like the app were a webpage and styled things differently depending on those factors?

View on HN

I don't know how they did it but I know how I would do it: stop fighting Android and work with it. "Issue 1" is a classic example of someone trying to have a lot of control over their layout and ultimately creating a lot of work for themselves. Instead of trying to lay things out exactly, use the built in layout managers in Android. In this example one could use a LinearLayout to stack items one below the other, ensuring the "Connect with Facebook" button would never overlap the text above it.

I think they were using libGDX* previously for the rendering - that could explain the layout-related problems.

*I can't see any references to it now, but previously one of their job postings required knowledge of libGDX.

Yeah, it seems like this article is a perfect example of why trying to do it your own way, instead of the Android way, is going to cause a lot of problems.

Yep, same with the keyboard problem. I've never had that problem in my apps because I always use the attribute that lets you scroll a view if the screen is too small to show it all.

That's what I was hoping to read as well. Nothing against their work, but to me it read more like an advertisement for the service than actual look into how they solved all these problems.

Reply on news.ycombinator.com