Why is Modern Android Development So Hard?
And How to Stay in the Top 10% of Developers Worldwide
itnext.io
-
Welcome to B4X forum!
B4X is a set of simple and powerful cross platform RAD tools:
- B4A (free) - Android development
- B4J (free) - Desktop and Server development
- B4i - iOS development
- B4R (free) - Arduino, ESP8266 and ESP32 development
How lucky we have B4A?
- Thread starter aeric
- Start date
- Similar Threads Similar Threads
itnext.io
True. In that article there are some things mentioned that I don't know what they are (I'll look).Why is Modern Android Development So Hard?
And How to Stay in the Top 10% of Developers Worldwide
We don't need to edit xml layout and Jetpack Compose.
We don't need to know Java and Kotlin.
We don't need to know Java patterns.
It's easier to work with cross platform.
It is because @Erel is doing all the hard work and giving us tool which is simple and easy, to say the least.
Thanks all to him
We must hope that he lives another 30 years at least!
(Erel, you are allowed to cross your fingers
).
Don't get me started about that again...
Thank to Erel and Anywhere Software, have done a great job for B4X developers.It is because @Erel is doing all the hard work and giving us tool which is simple and easy, to say the least.
Thanks all to him
I am very much appreciate to what we have today.
So I have always support by buying B4i (B4A) license a few times and donated to B4J once and twice.
I have nothing much to ask for.
Also thanks to some members who also contribute to the community like me.
I keep contributing back to the community.
I urge any other members start to contribute if not already done so.
Don't just take more without giving back.
Ever since the beginning of Android it was clear that it is an over-engineered OS. Many clever Google developers did their best to create very innovative and sophisticated solutions to (sometimes) non-existent problems. The mess related to Activities and Services is the result of this and one can see how their behavior changes with each Android version.
There is a relatively big change in front of us, related to the way apps need to respond to screen size changes. The advantage is that it will make the behavior of B4A more similar to B4i and B4J, however the transition will introduce some challenges.
There is a relatively big change in front of us, related to the way apps need to respond to screen size changes. The advantage is that it will make the behavior of B4A more similar to B4i and B4J, however the transition will introduce some challenges.
I am very grateful that you repeatedly take the complex issues and make it simple for us who use B4X.
you love challenges, don't you
Exciting... can't wait to see.
You mean for B4X developers?
For me, I am willing to move on and learn the curve.
As example, it used to be difficult to understand B4XPages but now I like it. Furthermore, there are alternatives if one doesn't want to use it.
My crystal ball shows:
- single process- single activity always running (it goes automatically in backgroud when another app is launched and eventually it gets killed by OS when needed)
- no more services (the breaking change) as we know them
- limited changes in B4XPages events
- something new about Home Widgets
It may account for our Xmas gift
- single process- single activity always running (it goes automatically in backgroud when another app is launched and eventually it gets killed by OS when needed)
- no more services (the breaking change) as we know them
- limited changes in B4XPages events
- something new about Home Widgets
It may account for our Xmas gift
All are welcome changes/enhancementsMy crystal ball shows:
- single process- single activity always running (it goes automatically in backgroud when another app is launched and eventually it gets killed by OS when needed)
- no more services (the breaking change) as we know them
- limited changes in B4XPages events
- something new about Home Widgets
It may account for our Xmas gift
Maybe time to create a Suite, and have all 4 IDE launch from a common interface?
it makes more than sense to me now that all 3 IDE's have/create folders to the other IDE's...
SO, if a B4A project creates a B4J and B4i folder, "changing" IDE's should be easier than having to launch a new one, at the risk of changing code in one IDE that may be "forgotten" by the other open IDE
it makes more than sense to me now that all 3 IDE's have/create folders to the other IDE's...
SO, if a B4A project creates a B4J and B4i folder, "changing" IDE's should be easier than having to launch a new one, at the risk of changing code in one IDE that may be "forgotten" by the other open IDE