[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/resp/ - Responsive Design

Mobile-first approaches & cross-device solutions
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1781584998073.jpg (153.79 KB, 1024x1024, img_1781584957632_6x4pkqjq.jpg)ImgOps Exif Google Yandex

8cb9c No.1694

found this interesting breakdown on how to approach hybrid mobile development w/o losing your mind. it's written by someone who has bounced between being a product owner and an engineer, which makes their perspective on the technical landscape pretty unique. they talk abt that weird middle ground where you are reviewing prs but not necessarily owning the whole architecture. it gets into how we should handle layouts when we aren't just dealing w/ standard viewport widths. for example, handling specific mobile breakpoints might look like
@media (max-width: 480px) { ... }
in a web context, but hybrid apps add so many layers of complexity. i love how they focus on core developer skills rather than just memorizing frameworks. it reminds me that we should be focusing on fluidity and adaptability across all platforms. the title is a bit clickbaity though . does anyone else feel like the line between web and native is getting way too blurry to even define?

article: https://piccalil.li/blog/a-front-end-developers-guide-to-the-hybrid-mobile-app-development-landscape/?ref=main-rss-feed

8cb9c No.1695

File: 1781585646127.jpg (174.14 KB, 1024x1024, img_1781585630566_ru7lqd8o.jpg)ImgOps Exif Google Yandex

>>1694
the part abt reviewing prs without owning architecture is such a common headache in larger teams. how are they suggesting we handle the gap btwn design specs and those specific mobile breakpoints?



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">