Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "mobile-responsive"
-
//
// devRant unofficial UWP update (v2.0.0-beta)
//
After several concepts, about 11 months of development (keep in mind that I released 20 updates for v1 in the meantime, so it wasn't a continous 11 months long development process) and a short closed beta phase, v2 is now available for everyone (as public beta)! :)
I tried to improve the app in every aspect, from finally responsive and good looking UI on Desktop version to backend performance improvements, which means that I almost coded it from scratch.
There are also of course a few new features (like "go to bottom" in rants), and more to come.
It's a very huge update, and unfortunately to move forward, improve the UI (add Fluent Design) and make it at the same level of new UWP apps, I was forced to drop the supported for these old Windows 10 builds:
- Threshold 1 (10240)
- Threshold 2 (10586)
Too many incompatiblity issues with the new UI, and for 1 person with a lot of other commitments outside this project (made for free, just for passion), it's impossible to work at 3 parallel versions of the same app.
I already done something like that during these 11 months (every single of the 20 updates for v1 needed to be implemented a second time for v2).
During the closed beta tests, thanks to the awesome testers who helped me way too much than I ever wished, I found out that there are already incompatiblity issues with Anniversary Update, which means that I will support two versions:
1) One for Creators Update and newer builds.
2) One for Anniversary Update (same features, but missing Fluent Design since it doesn't work on that OS version, and almost completly rewritten XAML styles).
For this reason v2 public beta is out now for Creators Update (and newer) as regular update, and will be out in a near future (can't say when) also for the Anniversary Update.
The users with older OS versions (problem which on PC could be solved in 1-2 days, just download updates) can download only the v1.5.9 (which probably won't be supported with new updates anymore, except for particular critcal bug fixes).
So if you have Windows 10 on PC and want to use v2 today, just be sure you have Creators Update or Fall Creators Update.
If you have Windows 10 PC with Anniversary Update, update it, or if you don't want to do that, wait a few weeks/months for the update with support for your build.
If you have an older version on PC, update it, or enjoy v1.5.9.
If you have Windows 10 Mobile Anniversary Update, update it (if it's possible for your device), or just wait a few weeks/months for the update with support for your build.
If you have Windows 10 Mobile, and because of Microsoft stupid policy, you can't update to Anniversary Update, enjoy v1.5.9, or try the "unofficial" method (registry hack) to update to a newer build.
I hope it's enough clear why not everyone can receive the update today, or at all. :P
Now I would like to thank a few people who made this possible.
As always, @dfox who is always available for help me with API implementations.
@thmnmlist, who helped me a lot during this period with really great UI suggestions (just check out his twitter, it's a really good person, friend, designer and artist: https://twitter.com/thmnmlist).
And of course everyone of the closed beta testers, that reported bugs and precious suggestions (some of them already implemented, others will arrive soon).
The order is random:
@Raamakrishnan
@Telescuffle
@Qaldim
@thmnmlist
@nikola1402
@aayusharyan
@cozyplanes
@Vivaed
@Byte
@RTRMS
@tylerleonhardt
@Seshpengiun
@MEGADROID
@nottoobright
Changelog of v2.0.0-beta:
- New UI with Fluent Design and huge improvements for Desktop;
- Added native support for Fall Creators Update (Build 16299);
- Changed minimum supported version to Creators Update (Build 15063), support for Anniversary Update (Build 14393) will arrive soon;
- Added mouse support for Pull-To-Refresh;
- Added ability to change your username and email;
- Added ability to filter (by 'Day', 'Week', 'Month' and 'All') the top Rants;
- Added ability to open rant links in-app;
- Added ability to zoom GIFs (just tap on them in the Rant View);
- Added 'go to bottom' button in the Rant View (if more than 3 comments);
- Added new theme ('Total Black');
- ...complete changelog in-app and on my website (can't post it here because of the 5000 characters limit)...
What will arrive in future updates:
- 'Active Discussions' screen so you can easily find rants that have recent comments/discussions;
- Support for 'Collabs';
- Push Notifications (it was postponed and announced too many times...);
- More themes and themes options;
- and more...
If you still didn't download devRant unofficial UWP, do it now: https://microsoft.com/store/apps/...
If you find some bugs or you have feature suggestion, post it on the Issue Tracker on GitHub (thanks in advance for your help!): https://github.com/JakubSteplowski/...
I hope you will enjoy it! ;)52 -
I have been a mobile developer working with Android for about 6 years now. In that time, I have endured countless annoyances in the Android development space. I will endure them no more.
My complaints are:
1. Ridiculous build times. In what universe is it acceptable for us to wait 30 seconds for a build to complete. Yes, I've done all the optimisations mentioned on this page and then some. Don't even mention hot reload as it doesn't work fast enough or just does not work at all. Also, buying better hardware should not be a requirement to build a simple Android app, Xcode builds in 2 seconds with a 8GB Macbook Air. A Macbook Air!
2. IDE. Android Studio is a memory hog even if you throw 32GB of RAM at it. The visual editors are janky as hell. If you use Eclipse, you may as well just chop off your fingers right now because you will have no use for them after you try and build an app from afresh. I mean, just look at some of the posts in this subreddit where the common response is to invalidate caches and restart. That should only be used as a last resort, but it's thrown about like as if it solves everything. Truth be told, it's Gradle's fault. Gradle is so annoying I've dedicated the next point to it.
3. Gradle. I am convinced that Gradle causes 50% of an Android developer's pain. From the build times to the integration into various IDEs to its insane package management system. Why do I need to manually exclude dependencies from other dependencies, the build tool should just handle it for me. C'mon it's 2019. Gradle is so bad that it requires approx 54GB of RAM to work out that I have removed a dependency from the list of dependencies. Also I cannot work out what properties I need to put in what block.
4. API. Android API is over-bloated and hellish. How do I schedule a recurring notification? Oh use an AlarmManager. Yes you heard right, an AlarmManager... Not a NotificationManager because that would be too easy. Also has anyone ever tried running a long running task? Or done an asynchronous task? Or dealt with closing/opening a keyboard? Or handling clicks from a RecyclerView? Yes, I know Android Jetpack aims to solve these issues but over the years I have become so jaded by things that have meant to solve other broken things, that there isn't much hope for Jetpack in my mind 😤
5. API 2. A non-insignificant number of Android users are still on Jelly Bean or KitKat! That means we, as developers, have to support some of your shitty API decisions (Fragments, Activities, ListView) from all the way back then!
6. Not reactive enough. Android has support for Databinding recently but this kind of stuff should have been introduced from the very start. Look at React or Flutter as to how easy it is to make shit happen without any effort.
7. Layouts. What the actual hell is going on here. MDPI, XHDPI, XXHDPI, mipmap, drawable. Fuck it, just chuck it all in the drawable folder. Seriously, Android should handle this for me. If I am designing for a larger screen then it should be responsive. I don't want to deal with 50 different layouts spread over 6 different folders.
8. Permission system. Why was this not included from the very start? Rogue apps have abused this and abused your user's privacy and security. Yet you ban us and not them from the Play Store. What's going on? We need answers.
9. In Android, building an app took me 3 months and I had a lot of work left to do but I got so sick of Android dev I dropped it in favour of Flutter. I built the same app in Flutter and it took me around a month and I completed it all.
10. XML.
If you're a new dev, for the love of all that is good in this world, do NOT get into Android development. Start with Flutter or even iOS. On Flutter and build times are insanely fast and the hot reload is under 500ms constantly. It's a breath of fresh air and will save you a lot of headaches AND it builds for iOS flawlessly.
To the people who build Android, advocate it and work on it, sorry to swear, but fuck you! You have created a mess that we have to work with on a day-to-day basis only for us to get banned from the app store! You have sold us a lie that Android development is amazing with all the sweet treat names and conferences that look bubbly and fun. You have allowed to get it so bad that we can't target an API higher than 18 because some Android users are still using devices that support that!
End this misery. End our pain. End our suffering. Throw this abomination away like you do with some of your other projects and migrate your efforts over to Flutter. Please!
#NoToGoogleIO #AndroidSummitBoycott #FlutterDev #ReactNative16 -
When did “responsive“ web design become synonymous with “huge f*cking images, big ass captions and needing to scroll vertically forever“?!
Although sites like that may look good on tiny mobile screens, on desktop screens they are just freaking me out. I am not blind, nor am I too stupid a visitor to handle denser paragraphs of text in a more sophisticated kind of layout! Geez...8 -
I’m a .NET desktop fullstack dev these days… Never worked web unless for my own small needs/personal projects.
I started using tech one way or the other by the time windows was version 3.1 and been through quite a bit ground-breaking changes in the industry of software development and the internet but if there’s one thing I cannot understand of it all, no matter how much thought I put into it is: How the fuck did we manage to make it so fucking complicated to develop anything these days?
I remember like it was yesterday that you could stand a website with HTML, CSS and JS, three fucking files and you’ve made yourself a single page site. Then came the word “Responsive”, “Responsive” written everywhere. Fair enough, grid system popped up. All of the sudden jQuery was summoned… and everything that happened after this point has been a fucking circus of high-pitched teens talking on conferences about fucking libraries and frameworks to make integration with real time, highly scalable, eco-friendly, serverless, data driven, genome aware, genderless, quantum technologies to interact with bio dynamically generated organisms, namely fucking users.
Every fucking bit of the process of building a mobile/web application seems to be stopped by yet another incredibly dumb attempt to suicide a developer. Can you go from starting an app and publishing an app without jumping through a thousand VERY specific hoops? No, fuck no.
I fucking hate it… It’s a bit hard to get Desktop dev jobs these days but for as long as I work on IT I will continue to stick to that area, until someone for the love of life comes up with a fucking solution to all this decadent circus of bureaucratic technocracy.
Fuck big industry, fuck tech giants, fuck javascript and webassembly, fuck kids putting ASCII art on console applications that I DON’T FUCKING NEED to install dependencies THAT I DON’T FUCKING NEED to extend functionality on frameworks that I DON’T FUCKING NEED… oh wait, I do need all this because YOU FUCKING MADE IT MANDATORY NOW! FUUUUUUUUUUUUUUUUUUUUUUUCK YOU!!!9 -
Forget about Internet explorer compatibility, EMAIL TEMPLATES are the actual worst. Outlook uses the same html rendering engine as MS WORD. It's sooo painful. All the bad practices you had to do 15 years ago, you have to do when you write email templates.
YOU WILL NOT KNOW PAIN until you have to make an email template, that works in Gmail, Yahoo Mail, OUTLOOK, outlook.com, outlook for mac, MOBILE, Android, the gmail app, IOS, apple mail, and so on. And after you make an unholy abomination of table garbage, then having to make it responsive/mobile friendly after all that!
If something is broken in one client, fixing it will break something in a different client! And then having to take a stab in the dark to try to fix it and then sending yet another test email (which costs $ per test)
I must have slashed decades off my life having to build email templates. It really is horrendous. There are frameworks like Zurb for email that at least let you feel like you're using a modern workflow. But things break just as often.
Honestly if you have the option, use a wysiwyg editor for building emails. At least when it does break (and they all will) you can at least blame the software.
Which is better than spending 4 hours on why that table cell doesn't line up correctly in outlook.7 -
It's enough. I have to quit my job.
December last year I've started working for a company doing finance. Since it was a serious-sounding field, I tought I'd be better off than with my previous employer. Which was kinda the family-agency where you can do pretty much anything you want without any real concequences, nor structures. I liked it, but the professionalism was missing.
Turns out, they do operate more professionally, but the intern mood and commitment is awful. They all pretty much bash on eachother. And the root cause of this and why it will stay like this is simply the Project Lead.
The plan was that I was positioned as glue between Design/UX and Backend to then make the best Frontend for the situation. Since that is somewhat new and has the most potential to get better. Beside, this is what the customer sees everyday.
After just two months, an retrospective and a hell lot of communication with co-workers, I've decided that there is no other way other than to leave.
I had a weekly productivity of 60h+ (work and private, sometimes up to 80h). I had no problems with that, I was happy to work, but since working in this company, my weekly productivity dropped to 25~30h. Not only can I not work for a whole proper work-week, this time still includes private projects. So in hindsight, I efficiently work less than 20h for my actual job.
The Product lead just wants feature on top of feature, our customers don't want to pay concepts, but also won't give us exact specifications on what they want.
Refactoring is forbidden since we get to many issues/bugs on a daily basis so we won't get time.
An re-design is forbidden because that would mean that all Screens have to be re-designed.
The product should be responsive, but none of the components feel finished on Desktop - don't talk about mobile, it doesn't exist.
The Designer next to me has to make 200+ Screens for Desktop and Mobile JUST so we can change the primary colors for an potential new customer, nothing more. Remember that we don't have responsiveness? Guess what, that should be purposely included on the Designs (and it looks awful).
I may hate PHP, but I can still work with it. But not here, this is worse then any ecommerce. I have to fix legacy backend code that has no test coverage. But I haven't touched php for 4 years, letalone wrote sql (I hate it). There should be no reason whatsoever to let me do this kind of work, as FRONTEND ARCHITECT.
After an (short) analysis of the Frontend, I conclude that it is required to be rewritten to 90%. There have been no performance checks for the Client/UI, therefor not only the components behave badly, but the whole system is slow as FUCK! Back in my days I wrote jQuery, but even that shit was faster than the architecuture of this React Multi-instance app. Nothing is shared, most of the AppState correlate to other instances.
The Backend. Oh boy. Not only do we use an shitty outated open-source project with tons of XSS possibillities as base, no we clone that shit and COPY OUR SOURCES ON TOP. But since these people also don't want to write SQL, they tought using Symfony as base on top of the base would be an good idea.
Generally speaking (and done right), this is true. but not then there will be no time and not properly checked. As I said I'm working on Legacy code. And the more I look into it, the more Bugs I find. Nothing too bad, but it's still a bad sign why the webservices are buggy in general. And therefor, the buggyness has to travel into the frontend.
And now the last goodies:
- Composer itself is commited to the repo (the fucking .phar!)
- Deployments never work and every release is done manually
- We commit an "_TRASH" folder
- There is an secret ongoing refactoring in the root of the Project called "_REFACTORING" (right, no branches)
- I cannot test locally, nor have just the Frontend locally connected to the Staging webservices
- I am required to upload my sources I write to an in-house server that get's shared with the other coworkers
- This is the only Linux server here and all of the permissions are fucked up
- We don't have versions, nor builds, we use the current Date as build number, but nothing simple to read, nonono. It's has to be an german Date, with only numbers and has always to end with "00"
- They take security "super serious" but disable the abillity to unlock your device with your fingerprint sensor ON PURPOSE
My brain hurts, maybe I'll post more on this shit fucking cuntfuck company. Sorry to be rude, but this triggers me sooo much!2 -
It bugs the crap out of me that GitHub.com is not fully responsive.
Mobile?
Check
Desktop?
Check
Everything in between?
Nope nope nope
Also, if you want to waste a huge chunk of time, try to google if you can contribute to GitHub.com. 🙄18 -
Dev: (Watches user print out screenshot of maintenance app to do list, walk across facility to printer. walk across facility to equipment and check things off on paper, then walk across facility back to their terminal and copy the findings over.)
Dev: We made the app responsive so they could do that on a mobile device. Why are they printing?
Manager: Printers are cheaper than getting more tablets.
Dev: …
Dev: Can we at least get a printer at each terminal so they don’t waste so much time walking across the facility?
Manager: That’s too many printers to maintain. It’s easier to just have one.
Dev: …8 -
Ffs Bitbucket, is it really so much to ask for to have a mobile responsive website in 2020 to normally review my pull requests.
Not like we're giving you loads of money for your service already or anything.. 😌6 -
The more I work here the clearer it gets:
I just fucking can't make websites anymore.
I totally can't work on graphics, I can't transform a PSD into responsive HTML.
I fucking despise CSS, computers having different resolutions, having different browsers, doing mobile, doing iOS/safari which is always something extra.
I'm tired of not getting the appropriate resources and then people asking me why it just doesn't look the same.
BECAUSE IT'S NOT MY FUCKING JOB! I MAKE STUFF WORK, I DON'T MAKE IT LOOK PRETTY, I HATE PRETTY THINGS11 -
What you see in that screenshot, that was earned.
I'm on the plane and I want an hour of free Gogo (read: crappy) WiFi on my laptop (so I can push the code I'm probably the most proud of, more on that another time). The problem is that the free T-Mobile WiFi is apparently only available on mobile.
So after trying to just use responsive mode, and that still (almost obviously) not working. I realize it's time to bring in the big guns: A User Agent switcher. Small catch: I don't have an add-on for FF that can do that.
So on my phone I find an add-on that can and download the file. To send it to my computer, I initially thought to go through KDEConnect, but Gogo's network also isolates each system, so that doesn't work. So I try to send it over Bluetooth, except I can't. Why? Because Android's Bluetooth share "doesn't support" the .xpi extension, so I dump it in a zip (in retrospect, I should have just renamed it), and now I can share.
After a few tries, I successfully get the file over, extract the zip, and install the extension. Whew! Now I open up Gogo's page and proceed to try again, but this time I change the user-agent. Doesn't work... Ah! Cookies! I delete the cookies for Gogo (I had a cookie editor add-on already), but I had to try a few times because Gogo's scripts keep trying to, but I got it in the end.
Finally that stupid error saying it's for phones only went away, and I could write this rant for you.22 -
I work at a school and am involved in building the new website. Specifically as an ex Web developer myself I am acting as intermediary between the leadership team and the company we have hired to build the site. The company has a "the customer is always right" approach and will do what they are asked for so my main role is stopping the school from making stupid requests.
For example yesterday they complained that the site looked different on mobile compared to desktop. Then they complained that the (long paragraph) welcome message appeared below the menu and quick links on mobile instead of above them (forcing users to scroll down to get to navigation controls). After many more complaints and mind boggling suggestions, and my attempts to explain responsive design and reducing cognitive load, I left the meeting with a headache and an urge to spend the next three hours drowning Lara Croft.
The most difficult part of any developers role: not throwing the keyboard at the client every time they say something stupid.1 -
New returning client asked for a free mobile app in return for exposure.
Made a native web app that would open their web page (which is responsive)2 -
*senior designer*
Last year I had a meeting with the newly hired Senior Graphics Designer.
She was presenting the new design of the company's website with all the features she wants.
After a few minutes, I asked her, did you design it as a responsive website?
"What is that?" She said. I said that the website should display or have atleast a design for mobile view and desktop view.
And she replied, "is that a requirement?"
Talks to myself: how the hell we hire designers like this?
PS, she earns 4x my salary5 -
This really pisses me off. As a front end developer (ember.js, HTML and Css) colleagues and boss and pm are always making jokes how I just need to change a button or a color and whenever there is a bug in the UI there's always big fun and jokes around it. But when there's a bug in the API, they never joke around, it's just : oh yeah we're getting the wrong data or an exception. But they always like to undervalue UI work even when it involves complex layouts, multi browser compatibility, responsive design, mobile browsers etc.. While they just code their API to connect to a database and everything works they don't really need to worry about what the user is using as a browser. They just get requests and send replies. I don't really think people value the work in front end as much as backend and that pisses me off as I believe there's a lot more going on in the front end.. I know they mean well and they are all cool people but sometimes it pisses me off as they don't value my work..13
-
Client: I want my site to look exactly like the design.
Me: Of course, but I'm assuming you want it responsive...
Client: yes, I want it to look exactly like the design on all devices.
Me: but that's not how...
Project manager: of course the site will be fully responsive and look exactly the same on all devices.
Me: but...fine.
1 week later...
Project manager: The site looks horrible on mobile!
Me: it matches the design perfectly...3 -
On my first week in the internship, I have to create a small website and it has to be finished ASAP. So I used Bootstrap.
After finishing I tested the website in chrome debugger tools for every screen size (design responsiveness), it was working fine. My stupidity was that I haven't tested on actual mobile/tablet.
The site was live, I send the link to one of my friends and he said "why everything is so small? looks like I'm browsing on PC". I quickly grab my phone and visited the site and it was not responsive on mobile. Started to check the code again, tested again on chrome tools it was working. But not on mobile. Changed the bootstrap file but no fucking changes on mobile.
After few moments of thinking, I realized that I haven't included the "meta viewport" tag. I felt so stupid and it was kind of embarrassing for me.
Now I first include meta tags before working on new project.5 -
Updated a website for an older client today. Realized I originally wrote their website in 2002.
That web site is a fucking non-responsive piece of shit... but it is still running normally after 18 years.
Just HTML/CSS and some light JS/PHP for form processing. It's not fancy but it still performs and works perfect on Desktop and OK on mobile. Mobile devices which DID NOT EXIST when I wrote it.
Let this be a lesson to the entire new class of developers who seems to think you need some framework to develop. You don't. And I GUARANTEE if that site used any framework that framework would have been retired or updated to un-useability 10 years ago.
Meanwhile my LAMP ass "web native" shit spaghetti with ZERO DEPENDENCIES is still just chugging the fuck along.4 -
That time you think you found your dream dev job...
But they really just needed a content entry person so the other dev could add 'senior' to his title and work on all the new fun projects, while you're stuck fixing IE7 bugs in his code from 3 years ago.
He used prototype instead of jQuery.
You try to tell them about responsive design, but they think everything needs a separate mobile version.
You spend half the day learning his custom functions to a cms he built 2 years ago, and he's in the process of rebuilding a new cms from the ground up, so you have to learn the new version too.
Was fired 3 days before my birthday, and didn't get my company gift, even though I contributed to every one else's gifts.
Fired 2 months before birth of my child so lost my insurance.
After my time there... They now build responsive, they now use jQuery for everything. I also showed them how to do IE testing with virtual box, instead of them using the secretary's computer.7 -
First few times being made to make mobile responsive emails (from scratch, not generators) was an utter psychedelic mess I never wish to have the pleasure of returning too.
I since have had the pleasure of refusing this, as being able to maintain this chaotic mess created which has to be able to work across the major email clients is just a living nightmare.
There’s hell, then there’s a whole other level.1 -
I just logged into my bank account to see that everything has changed. More basic, primitive styling and in general it is shit. Why am I ranting about this, because I could tell from looking that it has been done to be more mobile friendly. Sure enough I resized the screen and everything snapped into place like it would on a mobile.
Now I've got to put up with an inefficient and more time consuming UX all because some twat in the bank has decided to pander to mobile devices nearly ten years after they've been introduced even though there's already a mobile banking app for that.
Responsive design is like living with a dwarf, because one of you is small, nobody else is allowed to have cupboards on walls anymore. Bastards!4 -
The fact that I have to convert a 90s-ish design into a WordPress theme despite the boss trying to convince our client that WP's shit and we should do it in something else doesn't tilt me as much as it should.
But what DOES tilt me and piss me off is the fact that the shitheads told us to 'make the design better', and so I tried; I made one of their graphics responsive by only designing it with CSS (and for once, I even made it work right) because they wanted a mobile-friendly version but failed to supply a mobile-version PSD so I had to improvise and they had the balls to tell my boss that they're 'disappointed that we failed to follow the guidelines'.
Did you bitchsicles even bother to hire a proper fucking designer who would know how to fucking design a PSD to convert into HTML? There's no fucking grid, the design's all over the fucking place like your mother after a Viagra-fueled Friday night bukakke party at an old home and the colors are an eyesore like your own fucking selves if you ever bothered looking in the fucking mirror. Fuck you all to hell.1 -
Dear Mobile Designers,
There is a difference between mobile first and mobile preferred. Stop being lazy and take advantage of desktop real estate. My monitor is not a big ass tablet.
Thank you,
Desktop End User1 -
Two of my team members were trying to make a website responsive for over an hour. They tested everything. They checked the JavaScript, checked their CSS media queries, tried everything but it just wouldn't work on mobile browsers.
So as usual they decided it was "impossible" due to "WordPress constraints" and told me that it would work on the browser but not desktop.
I just added the meta viewport tag. It literally took 10 seconds. It worked.
I hate people who give up easily. Just hate it.2 -
Working on a side gig - an online clothing store - just finished implementing the cart logic, need to set up both PayPal and mobile money payments plus make sure the whole UI is responsive - fucking images! This is all needed by tomorrow... I haven't slept since Monday, just getting back home from a long day at work and did I mention that the client is also expecting to see a custom blog that I haven't even begun working on...
Fuck12 -
About 3 years ago, my girlfriend had this laptop that she got from her University. She had to give the laptop back to get reset, but didn't want to lose all of her data on it, and a backup would be around 750GB.
So I suggested that I would backup the laptop (was thinking to just dd an image and go from there). So I plugged in my mobile USB and external hard drive, and started the imaging process. Given the amount of data and setup, the process should have taken about 5hours. So we left it there for 5h.
Please be mindful that at this stage in my life I knew very little about boot processes, oses, and hardware.
5h after. The laptop screen is black and it ain't responsive. Not sure what happened, the dd process was completed, but the laptop refused to boot into windows. Tried a number of boot tools, and spent a crazy night hacking at the machine. But the university had some of sort of fail safe to not allow anyone to boot into windows if someone opened bios without entering a password. Whatever this was, I spent over 12h trying to either open mount the windows partition with a Ubuntu usb or mount the corrupt dd image on my laptop.
Long story short, after throwing at it a number of fixes. I was able to mount the image, copy out all of her personal data, and reinstall a new version of Windows on her laptop. The university didnt understand why the laptop was already reset. She still mentions this to me anytime I want to take a "custom approach" to software lol2 -
Warning: I code just for fun.
Today I finished a website and I asked to my friends to tell me what they think about it saying that it wasn't yet properly responsive and that could be some error, so I asked if they could use the computer to view it and all of them sent to me screenshots of the website on mobile.
I hate them.
P.S. Sorry for my english...8 -
When the so called "css expert" ask you why you're implementing so many things in @media all and (max-width: 800px) because it "doesn't change anything"
I had to teach him about responsive web design and chrome developer tools mobile emulation...3 -
Trying to communicate with a client's former "web guy" to transfer the clients domain back to my client so I can make changes to the design and make it mobile friendly.
He emails me "it's on Wordpress, so it's already responsive"
Go to double check on iPad and my phone. design is unresponsive... -
Ok, just built my first hello wold using react and after installing node babel react etc... The resulting folder is 51.7mb big. Makes me wonder what am I doing with my life why should I do this. what's the fucking point of it all.
Don't get me wrong I like react and I think it's really cool, but what is all this going to achieve at the end "build a website to sell rubber poop" like wtf... some company wants to sell shit and some monkey with an MBA is going to set the deadline and add Features. No one understands the shit we go through no one cares and we just build websites and Android apps... maybe there is no point here maybe there is nothing.
I remember when coding was fun now it's just building highly responsive web/Mobile based IT solutions to clients who wouldn't know a good website if it fucked them in the ass5 -
So I was building a WPF standalone software for a subject in uni, and our lecturer (the PhD holder guy) told me to make the GUI responsive in my WPF application, and gave me a long lecture about how everyone uses mobile nowadays.1
-
!rant
I studied BS Computer Science and one of our requirements is our thesis. All of the groups in our section proposed Web Based apps and got rejected because web based apps are too common. So we have no choice so all of us proposed mobile apps. Mobile Development is not in our curriculum so we have to teach ourselves during the development of our thesis.
All of the groups' dev collaborated and taught each other except one group, my group. Since I am a lazy motherfucker, I didn't taught myself how to develop a mobile app (android). So I made a web based app with responsive design, purchased my own domain, used android studio's webview and voila, a mobile app with a web based admin.
P.S. We got the best thesis award.3 -
Week 1 : Be told website needs to be responsive for all main mobile devices. Code and complete.
Week 2 : Go back to previous work
Week 3 : Oh the MD is doing a demo this week (which was arranged in week 1) of the responsive site, can you change almost everything and add all this new functionality before Tuesday.... -
that moment when I browse the Internet via mobile phone and have to request the desktop version (chrome) because that fucking mobile view sucks AF
What a big fail if I choose the desktop view over the "responsive" one on my small device1 -
Each time I try firefox after somebody mentions it again or it's in my rss feed, it still seems to never actually advance
It's stuck and either gets worse or goes back to its stable non improving level again, how come do they still not have a proper mobile responsive tester, why are even the upgraded addons still suffering the same container and rendering bugs
how is it more important getting bad image by implementing mr robot malware, than getting on an actual competitive level
why is it default bloated with random pocket addon bullshit, why did it begin to lag, ..
I remember when I was using firefox for a good portion of my life and laughed at how google chrome is laggy, but nowadays theres simply no competition to chrome, its stability and developer tools
I wish there was competition, the grid tools were a great start, but then nothing followed and they just went back to their never improving flatline16 -
Debugging that responsive website and can't figure out where it is applying the viewport for the mobile layout. Cookie isn't set to view full site, nothing in html....checking Google's Dev Tools even in incog mode...until I notice Chrome is zoomed in....CTRL-0 = fixed. Dammit. Zoom on page just wasted 5 mins. I want my 5 mins back!
-
So a week ago my boss asked me to design + build/write code for our new site from scratch.
Meanwhile the old website they have had for 5 years is still without SSL and looks pre-2000.
It's supposed to be finished and be mobile responsive by tomorrow.
I'm the digital marketer.3 -
WTF with all this full screen popup to promote a mobile app on so many perfectly functional mobile/responsive websites. If I'm the developer of that mobile website and asked to add that kind of popup to my work, I'd be offended.1
-
Got one right now, no idea if it’s the “most” unrealistic, because I’ve been doing this for a while now.
Until recently, I was rewriting a very old, very brittle legacy codebase - we’re talking garbage code from two generations of complete dumbfucks, and hands down the most awful codebase I’ve ever seen. The code itself is quite difficult to describe without seeing it for yourself, but it was written over a period of about a decade by a certifiably insane person, and then maintained and arguably made much worse by a try-hard moron whose only success was making things exponentially harder for his successor to comprehend and maintain. No documentation whatsoever either. One small example of just how fucking stupid these guys were - every function is wrapped in a try catch with an empty catch, variables are declared and redeclared ten times, but never used. Hard coded credentials, hard coded widths and sizes, weird shit like the entire application 500ing if you move a button to another part of the page, or change its width by a pixel, unsanitized inputs, you name it, if it’s a textbook fuck up, it’s in there, and then some.
Because the code is so damn old as well (MySQL 8.0, C#4, and ASP.NET 3), and utterly eschews the vaguest tenets of structured, organized programming - I decided after a month of a disproportionate effort:success ratio, to just extract the SQL queries, sanitize them, and create a new back end and front end that would jointly get things where they need to be, and most importantly, make the application secure, stable, and maintainable. I’m the only developer, but one of the senior employees wrote most of the SQL queries, so I asked for his help in extracting them, to save time. He basically refused, and then told me to make my peace with God if I missed that deadline. Very helpful.
I was making really good time on it too, nearly complete after 60 days of working on it, along with supporting and maintaining the dumpster fire that is the legacy application. Suddenly my phone rings, and I’m told that management wants me to implement a payment processing feature on the site, and because I’ve been so effective at fixing problems thus far, they want to see it inside of a week. I am surprised, because I’ve been regularly communicating my progress and immediate focus to management, so I explain that I might be able to ship the feature by end of Q1, because rather than shoehorn the processor onto the decrepit piece of shit legacy app, it would be far better to just include it in the replacement. I add that PCI compliance is another matter that we must account for, and so there’s not a great chance of shipping this in a week. They tell me that I have a month to do it…and then the Marketing person asks to see my progress and ends up bitching about everything, despite the front end being a pixel perfect reproduction. Despite my making everything mobile responsive, iframe free, secure and encrypted, fast, and void of unpredictable behaviors. I tell her that this is what I was asked to do, and that there should have been no surprises at all, especially since I’ve been sending out weekly updates via email. I guess it needed more suck? But either way, fuck me and my two months of hard work. I mean really, no ego, I made a true enterprise grade app for them.
Short version, I stopped working on the rebuild, and I’m nearly done writing the payment processor as a microservice that I’ll just embed as an iframe, since the legacy build is full of those anyway, and I’m being asked to make bricks without straw. I’m probably glossing over a lot of finer points here too, just because it’s been such an epic of disappointment. The deadline is coming up, and I’m definitely going to make it, now that I have accordingly reduced the scope of work, but this whole thing has just totally pissed me off, and left a bad taste about the organization.10 -
Our new project is a responsive mobile-first web system coded with HTML, CSS, jQuery and AJAX that connects to MySQL, but the main tasks runs trough a huge application written in Visual FoxPro, per client request...the web version could manage the whole business but no, it has to be Fox.
Oh, and it's the version 6, not even using the latest version 9 with all it's "improvements". What are we, back to the past milleniun?3 -
Holy fucking shit are email clients bullshit.
I don't know what happened there but if you thought the chrome-firefox-ie-egde gaps back in the days were sick - let me tell you.. email clients are made by the devil himself. All of them. All of them? Yup. Because he made some of them being owned by apple, working beatuiful and no weird stuff.
But on the same end he made some of them owned by microsoft and their office Studios. They use the word engine to render html emails. Read this again. Read it without starting to cry in agony.
But thats not enough. Let's make some of them use an ie-engine and the mac os variants going to use some webkit based renderer. This way there will be no valid ruleset to make it look good on all of them, isn't this great??
Now this might be hell already. But lets pour more salt into these wide opened wounds.
Let there be Germany and United Internet, owning trash like Web.de and GMX, whose android clients going to work completely different across Android and app-versions!
Once you've mastered these, let me introduce you to gmail. Lets take only the body node of your email and do some fuck up with it, so you have to display a non-responsive variant on mobile.
Now you might be thinking "but there are web-based clients, they'll do good ain't they?" Long story short: fuck you.
Not enough.
Let's go back to ms.
Hey dude lets make it possible to scale up your whole system. So old people can read shit better. And now the funny part: let's make it so that the word rendering engine, rendering emails goes completely mayhem on your mail, so it looks like a completely different thing! (:
If you ever receive a newsletter in your inbox and that shit looks like it's planned to look like.. appreciate that shit. Sacrifice a virgin as thanksgiving for it.
TL;DR:
E-Mail needs to die. I'm doing this for over 2 years now and this shit needs to stop asap.2 -
First time developing an Android app using Android Studio. I wanted to see how it is to make a mobile app. It's very simple, doesn't wow with design and calculates price discounts. First time using Java too, which was cool. Biggest annoyance? Making fields and buttons "responsive" to different screen sizes!1
-
"We don't have a responsive layout so just do what you think is best"
(builds responsive layout)
"This responsive layout doesn't work as we expected"
(sends 5 pages of notes on how mobile layout should work) -
Wtf? Why so much space at Left?
Someone at google don't know how to use css...
I think that is a wrong padding-left
Rendered in firefox Desktop
In full screen window
Chrome is the same
But the view is good in responsive mobile/tablet view1 -
Why is mobile development still a thing?
Hear me out. All these simple apps, like shopping centre discount, eshops, vinted, other kinds of webapi consumers. Many have a website and a phone app.
Why??? Why the phone app? What's wrong with just embedding your responsive webpage into a webview and call it a day ffs?
I mean, maintenance becomes trivial and there's no split brain. No? What am I missing?
Not talking about apps that rely on android/ios api, for like camera, calls, storage access, sensors etc10 -
Why install a native app to use devrant on a mobile phone? Your website is not totally broken in a mobile browser. Responsive web is possible in 2020, believe me and give it a try!11
-
When your sales guy sells your web based platform as an app when you've just finished making it responsive for mobile devices......2
-
What piece of shit coded this site?
https://freefilefillableforms.com//...
This is website people who did not file a tax return can use to get their stimulus check.
It’s not mobile friendly or even responsive in the least bit.
These people are poor and desperate and do you think they have laptop or desktops? No they use their phones.
You could have added some Flex box, now people are freaking out all over the internet.
Who the fuck would do this also this?5 -
It's amazing that SocialBlade is still not mobile responsive...
Are there even any developers working there?
Not anyone who tells them to make the site responsive?
Can someone explain? -
I remember when first iPhone came out, The only broken shit while browsing was panning and pinching(most of the pages did not have responsive design) but they worked. Now every fucking webpage is mobile friendly, except all of them are fucking broken! You don't have safari or Chrome? Then fuck you! Here you have this BIG fucking button that does not work. Fuck all SPA!1
-
Recommendation for mobile css queries?
I want to use one or two queries. Not more. And I find lists of way too many.
Is there a guide that covers like.. two? Two additional widths you should design? How do you do responsive webdesign?5 -
Motherfuck oh clients! My goodness their requirements.
They want a tiny part of an app load inside an iframe in a different app and have the data communicate both ways and the ui should look seamless and mobile responsive too.
What the actual fuck? iframe in 2016 ? Seriously?5 -
wanted to write my own JavaScript base calendar date picker instead of using the jquery one. really hate the idea of requiring jquery in my compiled script just for the calendar.
but the thought of mobile respobsifying the calendar UI kills me.... then there's cross browser support 😫3 -
DevFolio
This is a simple responsive portfolio website template. You can use it and make it yours by changing things and colours to your style and liking! I made it with a lot of hard work, love and of course with code :) I'm not a professional coder, but I tried my best to make it look cool and yet still keep it simple.
Mistakes are proof that we are trying!
I learned so much while making this template, if you use it, please let me know. I would love to see how amazing people can make it! I hope you'll like it!
I have used:
- HTML5 for markup
- Pure CSS3 for styling
- Bit of JavaScript to make a hamburger menu to work on mobile devices
- Font Awesome for Icons
- Unsplash for Images
You can add more things to make it even cooler! The comments in the code will help you navigate through it. Have a nice day! :D
you can view the Github repo at https://github.com/achaljhawar/...1 -
I just want to blow off steam here,
Its hard to make a dynamic form with just 2 and a half day of time considering the coding for backend and front end and also mobile responsive. Its very frustrating and the same time im dissapointed in my self but i think its not entirely my fault its hard to do all those task with such little time and a lot of things to consider -
While at a *coding* conference, with lots and lots of techy devs in attendance, many using mobile devices, a vendor decided to hold a hacking contest. Hack their little problem, get a t-shirt. Hack their big problem, get a bigger prize. I go to their website and notice:
1) they force me to create an account to do either problem.
2) the fucking bag of salty dicks can't even manage to make a responsive website. I mean, I could have fixed that for the cocksuckers while at the conference. But no, the shit company comes to a place full of devs and has a shitty website. Like, make your eyes bleed like a leaky sack of vaginas, bad.
I solved their little problem as fast as I could and deleted my account out of spite. -
Hey guys, need help from some web devs. I have few stores and I coded a php/html table for reporting purposes. I don't like that table, also its not responsive on mobile phone. Any advice how could I change the layout up?14
-
Guys, I would like to learn how to make web design for mobile. But I don't know where to begin, can you help please?13
-
Working on a project for myself and to put in my portfolio. Talking about it with a (non coding) co-worker and discussing where I am in the project as I've been really excited about my progress since I'm working from scratches with no frameworks for the back-end(the only side I've worked on so far). I was talking about the registration page and getting ideas as to what I should let users put on their profiles and she chimes in, "This would actually be better as a mobile app. That would be much easier to use." Well yeah, probably, but I'm a web developer, not a mobile app developer. Plus making it a web app means users will be able to utilize it through any medium rather than just their mobile phone. I can (probably) make it responsive enough that users don't mind it being a web page rather than an app.
I'm still learning, I know PHP, Python and a little JavaScript, not really enough to build a mobile app. Yeah I'd love to make this an app, but then I gotta support multiple products across several hundred different devices in multiple languages and I'm just not ready for that. Let's get the back end finished and we can go from there.1 -
I cannot take this anymore ... The picture on desktop and mobile is not crop equally ....... Please next time I receive that i kill myself. Im so tired of this shit
-
I have an assessment test tomorrow where I need to demonstrate a prototype website that is responsive and show it to a client(interviewer)
I have only done the website prototype at the moment as I got told on Friday. Should i also create the mobile prototype or explain to the client that it will be responsive and works on mobiles4 -
App Review – Zomato 2.0
Some apps are as essential as oxygen by example of https://apps.apple.com/us/app/... . Zomato, for sure, is one of them. If you love to eat outside and you’re not living in a cave, chances are that you’ve already gone through Zomato on the web or used one of their mobile apps. If not – Zomato is the place where you can locate eating joints, scan through their menus, check for home delivery numbers and a lot more than that. If you are diabetic you keep sweets in your pocket, similarly Zomato is something every food-loving person needs to keep in their mobile phones(I agree how PR-ish that sounds but it’s true).
Zomato had recently integrated social features on its website. That was followed by the much needed overhaul of their mobile apps. They’ve also updated their iOS app recently and I decided to give it a shot. Zomato 2.0 on the iPhone is super slick to say the least. The redesign brings a lot of character to the app. The Zomato app is now much more smoother, cleaner and powerful. The added social functionality adds more value to the app.
Design and Features
The 2.0 update completely changes the entire look and feel of the app. Everything from the app’s start screen to restaurant details has been changed. The default menu lets you explore and search eating places. Now there are icons for top 25 restaurants, reviews, favorites and more. The icons have been perfectly placed and it’s very easy to spot what you’re looking for.
Everything is just right. The app is highly responsive and there’s hardly any lag. If any, it will depend on your internet connectivity. Browsing menus is still a breeze and I personally love the way you can toggle between information, menu, photos and last but not the least, the reviews. Everything placed just perfectly to help you make that ultimate make or break decision – to eat or order from here or not?
Social
Everything is getting social. Even the next door Dolly-beauty-parlor apps are getting more social now. Zomato just integrated its social features on the web recently and they’re now a part of their mobile apps. On the iPhone app you need to login to access these social features. There’s a Top Foodies leaderboard that could prove to be a crucial game mechanic for the app. Browsing users’ profiles allows you to follow users. The profile pages tie up a user’s reviews and followers. This is all pretty neat and a part of a major plan at Zomato to take over the world.
With lists, network, user reviews etc. there’s a lot more to the app. I’m hearing that there’s still a lot more to come when it comes to social features on the Zomato iPhone app. I better start following up with people and posting reviews. This just kicked Foursquare where it hurts the most. And with that I’ve lost the little amount of motivation I had to check-in to places on Foursquare1 -
For classified type of website, where user experience differs much in web and mobile, is it better to keep seperate codebase or should I go with 1 codebase having responsive approach? Currently I am using react in mobile and having web codebase in angular. Any suggestions??6
-
tried to use devrant.com on a mobile browser: login only possible when spoofing desktop user agent, although at first sight, the site seems to work well in a responsive view. After upvoting 2 posts, website keeps nagging to install the app and sends disfunctional redirects. How can any website be broken on mobile in 2021?5