What technology do you build with?
For most corporate and e-commerce apps we use a single codebase with Flutter or React Native, so iOS and Android ship together. For screens with heavy camera, sensor or performance requirements we use Swift and Kotlin. We decide in discovery by looking at the screen list.
Will the app connect to our existing ERP?
Yes. Whether it is Panda ERP, Logo, Netsis, Mikro or SAP, the back-end API connects to the ERP's database or service. The app does not keep its own stock or customer accounts; it reads and writes the record in the ERP. The integration point is defined in writing during discovery.
Does the app work if there is no internet in the field?
Yes. Screens marked offline keep forms, photos and orders on the device and send them to the head office when a connection returns. Stock and prices show the values from the last sync; conflicting records come back to the user as a list and they decide.
Where does AI fit into the app?
In repetitive data entry. Steps such as reading a value from a meter photo, extracting a task from a visit note, or asking the user for a missing form field are handed to the agent. The result appears on screen and the user approves it; records that break the rules go to the head office, and the agent never closes a record on its own.
Can you also build a dealer or customer app?
Yes. A dealer ordering app, a customer service tracking app or a B2C shopping app is built with the same method. If you have a Panda Toptan B2B portal, the app uses the same records; the price list and the customer statement appear in the app, so the dealer does not need to phone.
How are store release and updates handled?
App Store and Google Play releases are made from your own developer account; the account and the app belong to you. Updates go to your team as a test build first and reach the store after your approval. Under a maintenance contract we track operating system updates.
When do we see the first result?
Within 3 business days of the screen list being ready, the main flow is shown on a prototype running with your own data. You decide on development after this demo, and the first team that goes live is measured for 30 days. We do not give any other delivery date before the scope is written.
What does the agent do in the mobile app?
Photos, forms and orders entered in the mobile app are written to the ERP record, and the user is asked for any missing field. The approval screen is inside the app; records that break the rules go to a person. The agent does not approve orders, change prices or message customers on its own. Scenario: order entry.