3

Wasted all day on trying to make my layout for android app responsive. Basically I have a background image which is scalable and then I have these textview widgets which need to be at exact positions ontop of background. Because of different screen sizes, the bg image scales and widgets go off. Cant find a way to do this with percentages, looks like I will have to support 10+ major screen sizes which means 10 separate hardcodes layout files. FML

Comments
  • 0
    This is what happens when people expect the web to act like print.
  • 2
    Viewport units ftw?
  • 0
    @Fast-Nop what do you mean?
  • 2
    @baeovvulf mh yeah you're right, technically that's somewhat nonsense because it's about an app and not a website. But there are years of experience with responsive design from the web, and going for pixel perfect design optimised for every screen size has long been abandoned exactly because it's too much work, and new screen sizes appear nearly as fast as new Javascript frameworks.
  • 2
    To be clear Im doing native android guys,not js
  • 0
    It's the ideas that matter, not the technology. I had a similar problem 25 years ago when I did some graphics application in Turbo Pascal under DOS that was supposed to work with EGA, Hercules and VGA.
  • 1
    @Fast-Nop bruhhh, people who implement ideas matter, and so far u didnt even provide any solid idea. Go home, youre drunk.
  • 0
    @zemaitis if you are unable to deduce core ideas from responsive design, which I did actually mention, maybe you should consider something simpler, like selling roses.
  • 3
    @Fast-Nop

    OP: I'm having trouble building a car with. Adjustable seats.

    You: Well chairs have existed for eons so adjustable car seats can be deduced from that.

    This is what your sound like.

    OP, if the text doesn't change, could you place it in the image?

    Otherwise, your could use invisible views with weights as spacers? Maybe this is helpful https://stackoverflow.com/a/...?

    Have you tried constraints?
  • 1
    @Fast-Nop You've been in programming 25 years?! Shit.
  • 0
    @polaroidkidd nah, the point is that responsive shit has been around for years, and everyone surfing the web has seen it in action over and over. The "optimised for 1024x768" days are gone long since.

    The reason is exactly what the OP is running into - too many screen sizes. The pain now with 10 layouts is already bad, but maintenance and testing with subsequent app versions will be even harder.

    Usually, you design screen relative, and you introduce graceful breakpoints. Don't try to completely fight the breaks because that's an uphill battle that you can't win. It may also help to remember that numbers like 6 and 12 have many nice divisors.
  • 1
    @Hu-bot0x58 yeah, and I'm still innovative... in finding new ways to make old mistakes. ;-)
  • 0
    @Fast-Nop you really like to listen to your own voice dont you. You dont know shit and probably never built an android native app. Im gonna say this just once: pull out your head from your arse and stop acting like a smartass with your useless condescending comments. Youre not funny. Youre not smart. You brought nothing to this convo, just came here to gain attention. You are being delusional man and you are making no sense. Just stop. Get some help.
  • 0
    @zemaitis Yeah, go forward with 10 layouts. That will at least prevent you from further stupid posts.
  • 0
    @Fast-Nop problem is already solved with 1 layout and percentage based guidelines. Now you are free to go.
  • 0
    @zemaitis So you are using a screen relative layout. Wow. Not that this ignorant me hadn't been using literally that term in my last comment that you had ranted on.
  • 0
    @Fast-Nop Just kys pls
Your Job Suck?
Get a Better Job
Add Comment