Tradly is a headless api first solution(Refer below more about this). The hosted web templates or mobile apps consumes the same api to provide the features.
We used to support mobile app as part of subscription, but we moved away from that to focus only on core offering (headless api) and a no-code editor only for web app.
As of now, we don’t offer mobile apps as part of our software subscription. The previous mobile app we had is currently sold as code base. Once you bought that, you will own the code.
You are responsible and can have your developers for
- creating application package to upload App Store and play store (called as bundling)
- Setting up play store and App Store profile
- Buying playstore and App Store license
- Fix if there is any new bugs
- Code for Ui customization
Can I build my own mobile app from scratch?
Yes you can do that. We have clients and development partners who do this method of building from scratch. We provide toolkits to support developing from your side. (Api reference, Js sdk)
Why do I need to buy mobile app source code?
It’s speed up the process. It’s cost-effective to buy a code base where it has most of the features built in. You can go to the market faster. If you want to make customization in UI, then you can use your developers (or our dev partners to customise it.)
Is it bug free?
We have kept tuning the codebase whenever we identified them before. If there is anything new, yes, you might need to have your developers to fix it. We are optimistic, that is not many. Or any big/complex issues.
##I’m building my website using editor, will the changes of what I do be reflected in the mobile app?
There is 4 types of things in mobile app to go through individually.
- Your core data (user, listings, accounts, transactions, etc.) is stored in a database. So it’s the same data that is consumed by apps and websites. So it doesn’t matter whether you use mobile or web. Both are basically same source.
- Application strings : example : the text used in buttons, menus, error messages, etc. are application strings. The existing mobile app codebase and hosted web templates are using the same strings. when you change them from superadmin > strings customization > it will change in both places. There is an exclusion here. For example: you purchased the code on January 2024, your developers added a new screen in the mobile app > that will not be available in the strings customization table.
- Your static blocks in the website: there are cases you have used static blocks like header text, welcome message, a feature section where you are explaining about the product. These blocks you created only for the website. So all of those blocks are not available in mobile app.
In general:
except the core data, all others data are exclusive to each application. That is the purpose of them. Each business might have different design preferences for app and website. So it’s hard for us as of now to unify both.
Reference about headless api from internet
