When you catch Facebook Devs testing in prod (beta app though)

This is just my token of appreciation for the Skype devs. Can't begin to say how much I hate it. Your android app is a joke even after a host of updates, your desktop client is an even bigger joke (atleast Linux Beta version, I know betas aren't supposed to be stable but this is ridiculous).

You have reinvented chat clients to be extremely bulky, cumbersome and very hard to sync across devices. And you have managed to make it "buffer" more than a YouTube video does on a 2G network. I for one, am blown over by how you did that. And to top it all, you can't close the client on Linux atleast! All you did is just override the close button so that it only minimises it. Brilliant piece of work right there!

Why the hell can't you just close the client and run it in the background the proper way like everyone else does? Why does it have to take 20 *** seconds to open a message? The only reason I am stuck with this is some wierdos in the office still only use this. Get your shit together 😡

Ahh.. I feel much better now.

Act I

Me (Lead Developer), Boss (Head of IT), CEO

> enter stage left CEO

CEO > "Alright Boss, give it to me straight. Are we going to be able to release app x by this date?"

Boss > "Yup we'll have a beta release on that date"

> exit stage right CEO

Me > types long email to Boss outlining exactly why we won't be able to release app x anywhere near that date, beta or otherwise, because:
1. We have a development team of 2
2. I've never developed an iOS app before
3. Developer 2 is still trying to understand git, because
3a. Developer 2 isn't even a developer (but he's doing iOS front-end so w/e)
4. We don't have the required database systems in place
5. Or CRM
6. Or CPQ
7. We'll need to conduct a security audit

Boss > "yeah, but CEO is gonna need to hear that date a few more times before he can fully understand"

Me > *internally screaming BUT YOU HAVEN'T TOLD HIM THAT AT ALL*
"ok cool just glad we're on the same page on that one"

ɴᴏᴡ ᴘʟᴀʏɪɴɢ: devRant Podcast #3 (Feat: Mark Zuckerberg)
─●──────────────────────────
◄◄⠀▐▐ ⠀►►⠀⠀　　⠀ 4:𝟷𝟾 / 𝟷𝟹:37 ᴴᴰ Sound ❐ ⊏⊐

6 months ago:

Boss: We have this idea to improve our onboarding to avoid drop off in the new app. See this section here? Were going to take that out of the onboarding and just let them pass straight through to the app. Then when they get into the app, there will be a banner telling them they should go to settings and set this up. That way they can ignore it for a while and get into the app sooner

Me: Get into the app sooner to do what?

Boss: Explore it

Me: Explore an empty app with no content, as they are a brand new user with nothing setup? While theres a big banner on the screen saying "You have insecure settings" ... basically forcing them to do it straight away anyway?

Boss: Yeah, we can give them some recommendations or something while they click around. It will be good. This is months away anyway, we'll talk again

Yesterday:

Boss: So this weird unexpected thing happened. We showed some beta users our plans to remove this section from onboarding and they felt weird about it. They said they didn't like the idea of the banner telling them they haven't set it up correctly

Me: Thats not weird, I said the same thing 6 months ago

Boss: ......... oh, really?

Me: Yep. Its not an improvement to get them through onboarding quicker, just to tell them they have to now go do it somewhere else

Boss: ... right. Ok maybe we'll build it anyway and see how they feel with it in there hands?

Me: nope

Boss: ... what do you mean?

Me: We are behind, you've asked me 3 times in the last week if we are going to be able to get everything in on time ... and now you want me to build something that everyone, apart from you, says they don't like. So realistically, i'm going to build it, and then remove it next week ... and we'll have a discussion about what has to be dropped because of this

Boss: ........ right .... ok .... hhhmmm

Me: *sits with resting bitch face*

Boss: ... maybe we can hide the banner until later. Not show it to them until they've done something in the app?

Me: ... maybe we can not do any of this?

Boss: right but then the onboarding will ...

Me: *talks louder* ... yes will be the way our users want it to be

Boss: ... hhmm i'm not sure

Me: Ok heres what we'll do, so long as it doesn't delay me getting the designs I need, feel free to have the designer mock up what it would look like using that figma on device preview thing. If users say they like it, i'll build it

Boss: ... right but it won't be real on device app so ...

Me: Its that or we cut feature X

Boss: ... well we need that

Me: ok glad we agree, let me know what feedback the designer gets

Boss: ... ok

After 8 iTunes Testflight Beta approvals for my app ... better still, I got hte app approved for the App Store a week ago to "de-risk" our "final submission" ... That's 9 approvals for my app, and we're ready to submit version 1.0.0 and actually release on the store. We take last week approved app and "developer reject" if to make room for the final tweaked version (minor tweaks, minor bugfixes). Submit version 1.0.0., plenty of time before it needs to be released.

But, what's this? "Meta Data rejected" for v1.0.0 because some piece of shit at Apple wants to watch a video of the app working with our hardware. What about the previous 9 approvals with the demo account connected to the demo hardware?

So we send a video within 1 hour of their unexpected request about the very foundational fucntionality of our app. That was 24 hours ago and these fucking assholes haven't even responded, no sign of when they will trouble themselves to respond. Pure limbo.

All the work up to this point was to "de-risk" their infamously shitty review process and all of it was in vain because it's somehow brand new information that our app works with our hardware.

Holy fuck, what a bunch of power-tripping assholes. All I can do is pace around and review the previous 2 months in my head to figure out what I could have done better. But I could not possibly have expected that after all the Testflight Beta approvals and after the recent App Store approval, that they would suddenly doubt that our software actually works with our hardware!!!!!

FUCK YOU APPLE!!!! FUCK YOU WITH ALL MY HEART!!!!!!

don't you just love it when apple takes 20+ days to review an app in beta...

That moment when a user tells you that your app has zero value...I have ~30 beta users and everyone I've heard from loves it except the one.

But the one is still nagging at me.

This is a friend's story:

So I've been trying to upload a free sticker pack for iMessage to AppStore for a while now. Why "trying"? because it keeps getting declined for the silliest reasons. It's nothing complex: just a bunch of our company's stickers about dev life. "Stickers for devs, from devs."

The first time Apple has declined the app because of the overall design, the second time it was because we used iMessage in the title. But this time it makes no sense at all. This is the message I got from Apple:

"Your app contains references to test, trial, demo, beta, pre-release or other incomplete content.
Specifically, some of your app’s stickers have “beta” references."

Huh? Check out the pic - one of our dev-related stickers says "still in beta". I guess Apple took that way too literally. Good thing they didn't tell me my app was too buggy because it has a sticker of a bug which says "it's not a bug, it's a feature"...

On second thought, what if AppStore is a modern-day Genie? Maybe I should add a sticker that says "Apple owns me $20 million in stock"? Or just one that says "Apple approves this sticker pack".

#Thisneverhappens_on_googleplay #appstore_make_a_wish #rookout

I am a people people pleaser.

Especially when it comes to deadlines. I struggle heavily with them. For example:

My boss: 'Will the app be done by Friday?'

Me: 'well some features won't be ready but overall yes.'

The truth: "No even if I work on it 24/7 there are just so many things in the background that are too technical to explain to my boss that it will be impossible for me to hit that deadline. It will most likely take over a month to be ready for beta testing...."

I just don't know how to deal with those kinds of questions. I don't want to say 'most likely over a month' because it makes me look like a bad dev but at the same time I know that that is way more realistic than 'it will be done by Friday'

The truth is: even if it just looks like 3 buttons to you, in reality I need to change thousands of lines of code to accomplish the expected goals...

P.S:

I wanted to write this rant for a long time. Now I am drunk. There will be a sober more ordered version of this rant.

Worst collaboration experience story?

I was not directly involved, it was a Delphi -> C# conversion of our customer returns application.

The dev manager was out to prove waterfall was the only development methodology that could make convert the monolith app to a lean, multi-tier, enterprise-worthy application.

Starting out with a team of 7 (3 devs, 2 dbas, team mgr, and the dev department mgr), they spent around 3 months designing, meetings, and more meetings. Armed with 50+ page specification Word document (not counting the countless Visio workflow diagrams and Microsoft Project timeline/ghantt charts), the team was ready to start coding.
The database design, workflow, and UI design (using Visio), was well done/thought out, but problems started on day one.
- Team mgr and Dev mgr split up the 3 devs, 1 dev wrote the database access library tier, 1 wrote the service tier, the other dev wrote the UI (I'll add this was the dev's first experience with WPF).
- Per the specification, all the layers wouldn't be integrated until all of them met the standards (unit tested, free from errors from VS's code analyzer, etc)
- By the time the devs where ready to code, the DBAs were already tasked with other projects, so the Returns app was prioritized to "when we get around to it"

Fast forward 6 months later, all the devs were 'done' coding, having very little/no communication with one another, then the integration. The service and database layers assumed different design patterns and different database relationships and the UI layer required functionality neither layers anticipated (ex. multi-users and the service maintaining some sort of state between them).

Those issues took about a month to work out, then the app began beta testing with real end users. App didn't make it 10 minutes before users gave up. Numerous UI logic errors, runtime errors, and overall app stability. Because the UI was so bad, the dev mgr brought in one of the web developers (she was pretty good at UI design). You might guess how useful someone is being dropped in on complex project , months after-the-fact and being told "Fix it!".

Couple of months of UI re-design and many other changes, the app was ready for beta testing.

In the mean time, the company hired a new customer service manager. When he saw the application, he rejected the app because he re-designed the entire returns process to be more efficient. The application UI was written to the exact step-by-step old returns process with little/no deviation.

With a tremendous amount of push-back (TL;DR), the dev mgr promised to change the app, but only after it was deployed into production (using "we can fix it later" excuse).

Still plagued with numerous bugs, the app was finally deployed. In attempts to save face, there was a company-wide party to celebrate the 'death' of the "old Delphi returns app" and the birth of the new. Cake, drinks, certificates of achievements for the devs, etc.

By the end of the project, the devs hated each other. Finger pointing, petty squabbles, out-right "FU!"s across the cube walls, etc. All the team members were re-assigned to other teams to separate them, leaving a single new hire to fix all the issues.

Two years ago, I developed an security app for Android as a school project. I didn't like teamwork at school (you know, you do all the work and everyone else is getting the same grade you receive, specially if you are the nerd of the class), actually I hated it, so I made it alone.

Its name was "Alex" and was a simple "panic button". You can configure two emergency emails and phone numbers (contacts only, not police) and, if you're in danger, you just have to press the button and the app is gonna send two messages/emails to your contacts: the first one, to tell where are you (GPS, only the name of the place) and that you're in problems. The second one with an audio/photo file of the situation.

Sounds like a great app, and I tested it few times. The reason I didn't continue with this is that I got my first job and I had not time, and that, tree or four months later, the government (of the city) launched a similar app. Less sophisticated, but I think it's still useful: "No estoy sola"(I'm not alone). I haven't tested it cause I don't trust on the authorities, I'd preffer to send my location to a friend through messenger app instead.

I don't know if I should re-work this app (I didn't released it, I just have the beta) or work on something else. I'm afraid that, if I release it, someone could die or get kidnapped because of a bug or something going wrong with the app :c What do you think?

When you accidentally publish the testing version of your app to the production channel instead of the beta channel... 😣

I've talked in past rants about how marketing loves showing off features to customers that are still in Beta to give us devs more pressure to finish them earlier, but it really just ends up screwing up our schedule since we have to push back on other features.

We had warned them not to do so for a series of reasons. But this time, this time their bad practices has come back to bite them in their butts.

They've been bragging all over to customers about this API integration we've been developing. They caught a reasonable amount of customers whose main reason for hopping in with us was this API integration. We finished the code on time, and submitted to the API provider for them to revise our "app". It's been a long back-and-forth conversation clarifying purposes and trying to fix tiny details and, of course, the providers' emails take almost a week to come back. We're waayy past the deadline marketing had promised customers, and they know they can't really blame the devs.

Sucks to lose these customers, but it feels so good to show these marketing pricks a lesson.

IOS 11 Beta 2 can play gifs in the default Photos app!!!

I was just about to post on here asking for a final round of beta testers for my web app before launch, and just before I hit “post” I thought of a massive issue.

FUCKING CUNTSTICK

Im the only dev at our app company. Beta due tomorrow. Im learning im astonishingly bad at handling stress

The app I'm using right now... devRant unofficial UWP.

It started by chance, I wanted since years to release an app for Windows 10, but never something like this.
I found devRant in 2016 and I just wanted to use it on my Lumia 950, so I opened Visual Studio and created a very simple client to get data from the web version.
After a few builds I decided to release it on the Microsoft Store as "devFeed (Beta)" (a bit later renamed to "devRant unofficial UWP").

Today, after almost 2 years, thanks to the huge support from @dfox and all the users, I'm releasing the 55th update. 😁

Thanks!

I've learned over the years that there's no such thing as a Proof of Concept app. You might as well call them beta versions since some salesperson or manager will see it and immediately tell clients about it who will buy it and then you have to support and expand it.

!rant

Goodbye Java I will not miss you at all! I swear ...

I do like it when making web services (especially that I can use Java8) but for Android you have been a torture. Hello sweet Kotlin! I shall embrace you and treat you like my newly born baby!!

Story is:
Working on a new project where I need to talk to a web service (also made by me).
Started writing in Java, all is cool and unit tests pass.
Downloaded Android Studio 3 Beta 1 and converted my Java code to Kotlin, That AsyncTask did not look nice in kotlin, converted it to async & await feature and I must admit lots of code removed, no more need to create a new fucking AsyncTask every time the app sneezes for data!

I feel like I'm working with C# but with difference in syntax.
My life is now complete :)

Lots of questions going on about devRant. Just want to make devRant better.

1. Please tell the update intervals of upvotes and downvotes. Is there a delay? Doesnt really matter but i see many times i got a upvote notif but my score didnt increased...

2. Duplicate image algo is so poor. I know it is only in beta, but i see so many reposts which has the same pic but only with the resolution different or the image with the devrant watermark.

3. Minor, tags should be also saved when exitting the post rant activity.

4. Feature request : go to top, bottom in rant

5. Please make web app accessible in mobile. I think you check the user agent for the web app, but can you make it available to mobile users who cant download the app?

6. When accessing the web app in mobile, i type devrant.io/feed
Then, by the wonderful intent you made, it opens the app automatically. I was writing a rant, but it was all deleted.

7. Any new podcasts and cartoons planned?

8. Still bug not fixed.
Write a comment in a long rant.
Delete the comment you just wrote.
You cant reply to the last person comment.

Thanks.

When I got the current job I started to work on an Android app that a coworker which left the company was doing.
The app was ready at about 40% and was barely usable, it lacked a lot of features and multithreading so with a huge amount of data it used to crash (Android doesn't allow you to make the app freeze for more than 2-3 seconds, it considers that the app is not responding anymore).
After a week or two the work to do was still huge, but one day one of my coworkers came in and ask me if I was able to release a beta for a client the same day... Unexpected deadline.
I spent 8 hour fixing as many bugs as possible and adding multithreading in the most weak parts.
I did it but it was so stressful and the result wasn't even great. In fact I finished the stable version 7 months later.

Client: Hey new iOS 11 is coming soon, is out app compatible?
Me: Not sure, let me shift the development to new Xcode 9 and test it out.
Client: So, how was it?
Me: pretty straight forward. all seems fine a couple of bugs.

But then when trying to fold a big function to make things easier to read, you discover that Xcode 9 beta 1,2,3 & 4 DOESN'T FUCKING SUPPORT THAT YET. How on earth is this not yet implemented?

So, I work in a game development studio, right?
We're trying to launch the title on as many platforms as reasonable, because as a social VR app we're kinda rowing upstream.
So far, Steam and Oculus have been fairly reasonable, if oddly broken and inconsistent.
Enter store 3.
Basically no in-game transaction support (our asking prompted them to *start* developing it. No, it's not very complete). No patch-update system (You want an update? Gotta download the whole fsckin' thing!). No beta-testing functionality for most of their stuff ("Just write the code like the example, it will work, trust us!"). No tools besides the buggy SDK (Wanna upload that new build? Say hello to this page in your web browser!).
So, in other words: Fun.

We've been trying to get actively launched for two months now. Keep in mind that the build has been up on Steam and Oculus for over a year and half a year (respectively), so the actual binary functionality is, presumably fine.

The best feedback we get back tends to be "Well, when we click the Launch button it crashes, so fail."
Meanwhile we're going back and forth, dealing with other-side-of-the-world timezone lag, trying to figure out what is so different from their machines as ours. Eventually we get them to start sending logs (and no, Windows Event logs are not sufficient for GAMES, where did you even get that idea????) except the logs indicate that the program is getting killed so terribly that the engine's built-in crash handler can't even kick in to generate memory dumps or even know it died.

All this boils down to today, where I get a screenshot of their latest attempt.

I just can't even right now.

1 - Spend 6 months building an app with Flutter
2 - Try to add in-app purchase. Must upload an apk to google console and register a product
3 - Must launch the app so the product is activated
4 - Console complains apk must contain 64 bits version
5 - Go to the issues tab on github and find a solution
6 - Implement the solution, recompile and send 2 apk files to Console
7 - Did not work...
8 - Find out maybe the console will allow just on closed alpha and beyond
9 - Put apks on closed alpha and fail because the Console wants a new apks with increased version codes...
10 - Recompile and send apks
11 - Console won't allow launching unless the format is using the new App Bundle
12 - Flutter does not support App Bundle with 32 and 64 bits...
13 - See issue about it saying the possible fix is in beta version, just need to update... What could go wrong?

I just wanted to release a damn app

I hate that shit

!dev !rant

Personal life update:

Like I said a few rants ago, I got a job in a call center for a national Japanese food chain. I am getting a pretty good salary for a teenager, and I am being paid the same amount as the other call center agents.

What I didn’t tell you is that I am doing a pre-university SAT, and it’s pretty much destroying me. I regret choosing to do it.

About AltRant: currently on short hiatus, though I swear to god that I will DEFINITELY upload it to TestFlight so you can get a taste of the app. All I ask is patience. I think I will wait until iOS 15 is out because the latest betas created a massive issue in a few parts of the app. All of them are aesthetic but damn it, I want to fix them only when they are officially there to stay because right now iOS 15 is still in beta.

We had a closed beta today for a product I've worked on for the last 6 months. We've been working late nights for the last week to make sure we get all the kinks out and make sure our demo went smoothly.

After a bit of hyping via a power point presentation by my colleague, we finally start the demo and of course the login fails. Both the API and database were offline. The servers were on but we just couldn't reach the applications. My colleague stalls and I get to debugging.

We were standing in front of 50 people who were hyped-up on a product that was failing in front of them.

But after 10 minutes (felt like an hour) of hemming and hawing, the app just decides to start running again.

What in the actual fuck? Does this happen to anyone else? Coz it feels like it happens to me every time.

let RANT = $state(true);

Don't even get me started on frontend engineering right now. It's like the wild wild west out here, with no rules or regulations.

I mean seriously, what is going on with frontend engineering these days? It's like we're stuck in some sort of weird limbo state where nothing seems to make sense and everything is a struggle. And to top it all off, the project I've been working on for the past two years has the same damn issues as an existing codebase that I was hoping to leave behind.

For some reason the npm build runs when container starts. Are you kidding me? Every time I have to restart the app, I have to wait for 30+ minutes just for the damn thing to build. And what's worse, it's not even a complex app. It's a simple frontend for a research website. So why the heck does it take so long to build?

I'll tell you why, because some genius thought it would be a good idea to build the entire codebase every time the container starts. And I have no doubt that this same genius probably thought it would be efficient and time-saving. Well let me tell you, it's neither efficient nor time-saving. It's just plain infuriating.

And don't even get me started on the codebase itself. It's like a labyrinth of tangled and convoluted code (multiple versions of React and now rewriting on Nextjs). Trying to make even the simplest changes feels like unraveling a giant knot (every freaking component have it's only style and everything from React is being used - hooks, Redux, whatever else is popular). And heaven forbid you make a mistake, because then you have to wait another 30 minutes for the whole thing to build and see if your change even worked.

And let's not forget about the old codebase that is still being used, because the new one wasn't ready in time. So we're constantly having to switch back and forth between two different codebases, trying to remember which one has which functionality, and hoping that we don't break anything in the process.

Don't get me wrong, I'm not against rewrites. In fact, sometimes they are necessary for a project to move forward. But when frontend engineers can't seem to make up their mind and constantly want to rewrite the code, it's a recipe for disaster.

And don't even get me started on the experience level of the frontend engineers who started this project. Most of them only had 2-3 years of experience (at the time of inception some of them has less than 1 year of experience), and yet they managed to convince management to approve this mess. It's like the blind leading the blind.

But hey, who needs experience and expertise when you have shiny new technologies and frameworks to play with, right? Isn't that what matters most in frontend engineering these days? Keeping up with the latest trends and constantly jumping on the "hype train" without any real understanding of how it will impact the project in the long run.

As a backend engineer (so I kinda don't give a flying freak about frontend) with almost two decades of experience and who was doing frontend with jQuery back in 2005 - that's frustrating and all the inconsistency is literally killing people (a couple of clients literally dropped the contract because of frontend quality).

RANT = false;

PS: why I used Svelte runes? Because some freaking genius suggested to port new (unreleased, only beta version) frontend UI to Svelte 5 because of runes.

I didn't posted something in a long time so...

TL;DR: FUCK YOU ANDROID STUDIO YOU FUCKING SHIT PIECE OF SOFTWARE

Thank you for your time.

I am running my own meme social network. For quite some time I wished I knew a Android developer, which could help me.

Because I know java I tried it myself, and Android studio is one of the worst programms I've ever seen.

My app crashed the whole time, just because my studio version was 1 behind. Updated studio, everything worked.

My layout wasn't showing correctly, reopened Studio, all layouts deleted.

For no good reason video views aren't resizing, so I need to use exoplayer.

One video on my platform nearly crashes the app when creating a thumbnail.

And so one....

I fucking hate Android studio...

(PS: if your a German, Swiss, Austrian you could check out my network and may become a beta tester of the app)

Found this on the play store

Does anyone have any idea where I can find beta testers for my android app

**Ps**

For free.

fucking flutter.

i'm trying to make a simple app. it would be an easier to do both natively.
for fucks sake flutter, add some functionality. flutter recently got out of beta but it's not fucking done. no native webviews, no native push notifications. fuck that.

however, i do have to give credit where credit is due. coming into flutter i expected a different feel of the app on iphone and android. it was exactly the same, and it was smooth too. in that respect, i love flutter.

also guys, i have an app (not finished yet) i built with flutter and i would like some constructive criticism for changing the ui. only android right now though, i can't afford ios.

dictive.app/download

When I try to build our app on Xcode 8 beta simulator :/

I don't know if our QA is good enough. We were developing an app for both ios and android. I, an ios developer, told the QA guy that it will take long before uploading the app in the testflight (convert swift2 to swift3). After a week the app is now uploaded in the test flight and at the same time my partner, an android developer, uploaded the android version of the app in the play store beta. The QA guy started to raise bug issues about the android version. He wanted to fix the bugs immediately since our boss needed to upload it in the play store and appstore. The QA guy kept on complaining to my partner why the android version is buggy. Then he said something we, me and my partner, facepalm.

The QA guy said " You shouldn't convert the app to swift 3. The ios version is fine when converted why the android version is buggy. You need to revert it back to swift 2"

We sit there in silence, thinking if we pity the QA guy or laugh at him.

I had a project idea for creating my own cloud service based on DO spaces. Today I started.

Had the webapp done in several hours and it's already deployed. Next step: the mobile app. I tried out Flutter and I have to say, for beta it's really good! So I'll work with Flutter for the mobile app.

Excited dev here!

The project started as a series of individual prototypes. The client the wanted a beta app for a few selected clients, and someone had the great idea of just merging the prototypes into a single app. The attitude of the devs was always "whatever, this will be rebuilt for public release"

Over one year later, and after many different developers touched the project, the client wants it to go live, there was never a rebuild, and there won't be one until a few months after it goes live, and the project is buggier than it ever was.

A rebuild would have been quicker and safer than fixing the huge backlog of bugs, still the client won't accept a rebuild.

A few people already quit over this project and I think I will be the next one to hand in my resignation.

Does anybody knows if. An android app looks the same on android s8/9/10 as on A30/40 ?
I need to beta test on s8/9/10 but i dont want to buy them, so expensive. But the A series are affordable.
The samsung remote test servers never worked for me

Facebook Beta App is not working on my Android. Anyway, who needs Facebook when you have devRant and everyone understands your posts? Haha

Cons of using an unmaintained app! :/

[About: This is Nokia's Z Launcher. Its development stopped before it even went out of beta, but it's so good I use it anyway. If interested, you can find it on APKMirror.]

Me (Km) - I develop android applications in my company.
TM - Dumbest technical manager taking care of backend for company products(app).
PM - Product Manager

Incident - PM went to some event to give demo on our App but due to some backend issue there was wrong data for his account. PM reported this TM. And the conversation between Me and TM went like this.

TM : Km app is not working for PM, its not showing anything to him.

Me : Okay let me check...

I logged in with PM credential and checked the logs and i found that there was some error message saying that there was no data. I copy-pasted the error message to TM.

After few minutes (TM added dummy data to PM account)...

TM : Km app is working now, what was the issue for not working previously ?

Yes she asked me like this even though it was related backend issue.

Me : Its backend issue...!

TM : But I did'nt change anything at backend.

Me : Neither I, I did'nt build new APK and uploaded to Crashlytics Beta and he(PM) is not using new build.

I copy-pasted the previous error message again and asked her (TM)

Me : Why was this error message coming ?

TM : There was some wrong data for his account, So i added some dummy data.

Me : (FacePalm) How come its not called as change in Backend.

The worst part is TM still thinks it not a backend issue.

So we have spent the last ~3 weeks creating workarounds for bugs that were found during testing against iOS 11 beta 1.
Today I had to go in and undo all the merges because as of beta 7 Apple have fixed the issues we were seeing.
Weeks of effort wasted that could have been spent upskilling or fixing build issues with an app that will have a release due in the coming weeks and we currently know little about.

We are currently debugging the most ridiculous issue. We have an eForm embedded in a native iOS app, and in the iOS 11 beta, every time we tap a dropdown list it takes 4 taps to dismiss it because it keeps reappearing. The final time it reappears with no data in it. The dropdowns are generated by Safari. We have replaced the Safari native dropdowns with a custom view and now the issue doesn't occur. What the hell Apple? What change did you make to Safari to cause such a random issue in a web view?

When you're in the beta version of our web app, there is water marking at font size 48 that floods the background with "beta". One day, one of our users did all of her work in beta, when asked about it, she said she didn't realize it was beta.

today my friend wanted to publish his swift 3 library in cocoapods, set up proper github repository, made a releass/tag then tried to upload cocoa pods. first was success but somehow it turned out to be empty then we changed some settings in cocoapods (moved paths etc) then it started to give errors and such. strangely every fkin time different kind of error.
first realized he is using xcode 7 build tools which lacks support of swift3, then switchex to xcode8-beta tools but again that shit wasnt working. so i noticed that their app switching repo origin to their specs origin.
removed cocoapods from sys entirely, xcode7 as same as cocoapods and installed git cmd tools from homebrew to make it updated. started from scratch same shit also happened.

so i give up and fired chrome to look up issue, it turns out it was problem with xcode-beta and cocoapods entirely, even somebody just 30mins before us also commented on issue with exact same output problems
5hrs for shitty bugs fml...

Although 80% of the company is on vacation, we were forced to put out a beta version of the biggest part of our app that's used by tens of thousands of people.

The best is that everyone knows this is a terrible idea but they still don't give a shit.

Google play console is so fucking confusing, I'm trying to get my app to open beta testing stage, I've completed all the steps and done the full roll out, but the status of the app is still pending publication (3 days), wtf does "Pending publication" means do I need to publish the app for production in order for beta testing release to work, or I have to wait for google to approve the beta release for publish?
I'm lost

I'll have to make some tough choices over the next 6 months. With my tech career beginning and my college education ramping up, time is of the essence, and the skills I develop now will be at the forefront of my future. So what does this have to do with Microsoft?

Well, the story begins in the Spring of 2016. Social Forums was about to turn a year old, Trump's campaign was ramping up, and I had just found my love for technology. With all my friends having phones, I had to get a phone and get working on development. The year before, Windows 10 was launched, and I was psyched. I found Microsoft's products to be underrated with potential. That day, I purchased a Lumia 640, upgraded it to Windows 10, and immediately began working. After another year-and-a-half gone by, I went from loving Microsoft, to defending Microsoft, to tolerating Microsoft. I could go on and on about the lousy structure, the privacy issues, the forced upgrades, the redundant developer platform, and other such issues that is leading me away from them. But if there is one thing they have proven over the years, is that the they are completely out of touch with its developers and its customers. They spent years ramping up their phones. They failed. They spend years ramping up their phones. They failed. They spend years ramping up their semi-annual OS updates. They failed. So why did they fail? It's not that they made the wrong prediction out of chance. They legitimately don't care about feedback. It's their way or the highway. This sounds vaguely familiar. They have been spending a decade ignoring feedback from the community because they want to become just like Apple. Right now, Apple LIVES off of brand loyalty and its stable, useful ecosystem. This cannot work for Microsoft as they don't have a lot of brand loyalty. But most of all, they don't have a working ecosystem. They have Windows Insiders, which provides them with hundreds of feedback messages per day. These include suggestions, bug reports, and constructive criticism. The feedback is public. You can have several pages of the same complaint, and they still won't do anything about it. They say they have a good relationship with their community, and that this Beta program helps Windows become better for all. But in the end, we are nothing more than a glorified unpaid labor force. They fired hundreds of professional debuggers just before the Insider Program took off. We are only here to provide bug reports for free. Now that their phones, AR headsets, browser, online services, and VR headsets are failing for all these reasons, I see little reason to develop for Windows anymore. I don't just mean their UWP and App Store platforms, I mean Windows as a whole. I'm definitely not a Mac guy either. I never see myself going to Mac either, as they are really no different in terms of how they treat their Developers and PC users. If things continue down this route, I will leave the platform all together. I've always wanted to be a Systems Programmer, so I don't really need an established paid platform to be successful. Even now, I'm not certain about leaving Windows altogether but as a developer, I need to find my place. Time is of the essence in my life, and I need to find out my place in the software world. Now I think it isn't on the Windows platform like I had dreamed it would be. But where do I go?

Hello family,

what do you think about publishing unfinished apps? I dont mean beta versions, but apps where you could implement more features bit by bit. So the main app is fully functional, but you could implement more and more..
So what's your opinion?
thanks fam
regards

I need help.

Since few days I've been thinking to go for cross platform app development. I've heard some names like Xamarin, Flutter & React Native. But I'm confused in choosing one of them. Below are few things I've read about them.

Xamarin is more like native, but It needs more effort to make it cross platform.

Flutter is still in beta, but Its backed by google, So it can be future. + it has performance issues and it lacks many important libs.

React native uses Javascript. and It's kinda less native.

So, I'm confused to choose in of them. I need to choose the one with many libraries and is good at performance, and it must have less effort for making it for another platform.

Computer science in high school...
Creating algorythm block diagrams using a beta version of app that is 15 years old
and is FULL of bugs.
You do not even have conjunction or disjunction
operators, so you have to create more blocks in order to check more complex conditions, for example.
So I asked the teacher if I can solve those tasks
in C++ and the answer was NO ...
:(

In google play store we enabled internal testing track of my app for my testing account. when I visit the page with testing account it says "Internal beta", and few lines below it says I am a "beta tester". Is beta tester the same as internal tester? can't google even consolidate the terms?

Is this is a beta version of devRant? 😕 My app doesn't works perfectly. Most of the time the back buttons in the app doesn't work and most of the times I can't even post the rants and I can never post an image 😶😖 sometimes I can't even upvote a rant. Everytime I read a rant, I've to close the app and open again to continue to the next one. 😑 I've tried so many times to uninstall and install again and the problem fixes for 1-2 minutes but then again everything stops to work 😑 I've many rants to post but i can't attach a image. If it also happens to you then please comment down and give me a solution for this 😄

"Nuxt 3 is currently in beta, keep in mind that it is not yet production-ready."
How about I use it in production anyway, huh? You can't stop me anyway and the client pays too little to care about resiliency of the app compared to my fun of learning, thenks.