Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs

Dashboard
Notifications
Mark all as read
Q&A

What's the better way to deal with deprecated feature?

+1
−2

It's a very old question came to my mind. Whenever I start building some applications for Android using Android Studio. In every update, lots of tools get deprecated. I know I can use deprecated "things". But, they don't work in higher version or API level.

I was thinking if there was something that doesn't deprecate anything. I was thinking to switch to Kotlin from Java. Then I noticed tools get deprecated in Kotlin either. Then I was thinking to move to Flutter and Dart. Since I am using Flutter and Dart in Android Studio so simply tools deprecate in those languages either. Then I was thinking to move to C# for android application. I had coded in C# for Game Development. Some articles had said that C# is also good for Android Application.

I think that tool doesn't deprecate for Android Studio. Tools deprecate for new Android Version.

Suppose, I am using a tool called "A". 2 months later it got deprecated so, I must remove "A" from my whole application for better performance. If I don't remove it then everyone can't use it. But, I want everyone to use it.

Then you might say that there's maximum API level and minimum API level and "your" minimum isn't lower than 20 most of time. So why are "you" saying that "you" don't want them to use who uses Android Device which is lower than 20.

Actually everyone move to higher version not lower version. Currently I am using a device which Android Version is 5.1. If I buy a new device will I buy 4.1 or lower than that? Of course not!

now forget about blockquote's text if you don't have anything to say about that. (If you forgot what I said) But, removing "A" tool will take lots of time. Cause, if I remove page "B" then page "C" was linked to page "B" hence I have to remove lots of line. Even implementing another feature will take longer time. What's the better way to deal with deprecated things?

not adding any programming language to tag since my question is not any specific language based. But, my main focus was on Android hence adding Android as tag.

Depends. Your question is not really answerable because it (intentionally?) is written in a way that the very core of your problem is only expressed in the most vague and generic terms. Things change over time. Software tools/tooling is no different. You will have to cope with that. ~ elgonzo

I don't think you understood my question. Cause, if you take a look at NodeJS then you will notice that feature "A" was deprecated in newer version. But, if I don't update my NodeJS then I can use that tool without any problem. But, this doesn't happen for Android. No matter what I do I always have to update my Android Studio. If I don't update then I can't work for newer Android Devices.

New version of Android come to market in every 6 months (sometimes it take longer time either; Sometimes it can be 2 years also). So I have to update my code every 6 months. But, this kind of thing doesn't happen for NodeJS, Python or something else.

Why does this post require moderator attention?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

What's the better way to deal with deprecated things? (2 comments)

0 answers

Sign up to answer this question »