FR at ENTA
Member
I used B4a several years ago - very successfully - at another company. Android development only.
Fast forward to today. It has been a long time since I have looked at the product, and of course it has grown leaps over the years. We have some very important work to do to re-engineer similar but grossly different codebases for iOS and Android for an important app for our company that we distribute from the Apple and Google stores.
I have tried to do some reading here before posting. I believe it is true that while all the UI will be different, other middle tier type non UI code can be largely reusable across the two platforms.
Would just like to hear from Erel or other folks who have successfully built the same app using both the B4i and B4a tools.
Any informed commentary greatly appreciated.
Frank
Fast forward to today. It has been a long time since I have looked at the product, and of course it has grown leaps over the years. We have some very important work to do to re-engineer similar but grossly different codebases for iOS and Android for an important app for our company that we distribute from the Apple and Google stores.
I have tried to do some reading here before posting. I believe it is true that while all the UI will be different, other middle tier type non UI code can be largely reusable across the two platforms.
Would just like to hear from Erel or other folks who have successfully built the same app using both the B4i and B4a tools.
- Are you glad you chose these tools?
- Do you think you saved significant time over the native SDKs?
- Did you achieve enough reuse to make it a smart choice, as opposed to choosing a Javascript-based cross platform technology?
- Does the product now contain support for building a single layout in a responsive manner, as opposed to having to essentially hard code to a screen resolution?
Any informed commentary greatly appreciated.
Frank