How can I enable “miles” or loyalty points in an Android app for a Western wear e-commerce site in Pakistan?
Hi everyone, I run an e-commerce website specializing in Western wear in Pakistan and I want to add a “miles” or loyalty-points system in my Android app. The goal is to reward customers for purchases, encourage repeat orders, and increase customer retention. Here are some of the features I’m considering: Customers earn a certain number of miles / points per purchase, depending on cart value. Miles can be redeemed for discounts or free items. Displaying miles balance in the user’s profile. Ensuring security / preventing fraud (e.g. fake orders just to collect miles). Possibly integrating the miles system across website + Android app. My questions are: What Android- or backend-side frameworks / libraries can help me build or integrate a loyalty-points system? How do others handle storing and syncing points (offline vs online)? What are good patterns to avoid abuse / fraud in such loyalty systems? Any advice for making the UI/UX for loyalty points (especially for customers in Pakistan) intuitive and engaging?Zero Touch Enrollment Network Specifications
Hello! I'm looking for information regarding the network specifications for the Zero Touch Enrollment as well as any phone-home network requests. Are there any logs we can pull from ZTE or the Android device during enrollment? The reason I'm asking: We have thousands of devices that have been enrolled in SOTI MobiControl over the last few years, and about 1000 of these were enrolled via ZTE. We've had no issues with this until early March. I can't find a rhyme or reason for this, but certain devices that were successfully enrolled, configured by an MDM, QC'd, boxed up, shipped to the end user, and then powered on will get the message below before the eSIM is activated. These are Honeywell CT47 devices with dual SIM cards (1 physical Nano SIM and 1 eSIM). The device above was added to ZTE using the IMEI number over a month ago and was successfully enrolled, but when powered on later and connected to Wi-Fi, it reset itself before the eSIM could be activated. This issue is only happening to devices that are factory reset while on-site and connected to the Wi-Fi only. My best guess is that the Wi-Fi network is blocking something during the enrollment process, as this reset issue is not happening on devices that have been enrolled and working for months. Thanks for your time!Managed configuration to Gboard has disappeared from MDM
The ability to apply a managed configuration to Gbaord has disappeared. We think this is due to a recent change to the Gboard app where Google has removed this ability. Environment: MDM = Omnissa Workspace One UEM (we are also hearing reports of this impacting SOTI customers as well) Rugged Zebra Mobile devices, majority running either A11 or A13 Leads: Managed App configs are still present on Chrome & ServiceNow Now Agent, hence why we believe this is not an MDM Console issue. We have escalated to Omnissa support anyway, who have in turn escalated to Google. Is anyone else seeing this issue?
"This item isn't available in your country" showing on isolated apps on isolated devices.
All of a sudden I'm having issues installing apps through Managed Play on isolated devices. When navigating to the app directly I can see "This item isn't available in your country." The devices are in the US. Location services confirms this, the external device IP is also US based as well. I have cleared cache and app storage of Google Play and Google Play Services. I have upgraded Google Play Services. The devices are fully managed with manage service accounts. I have reset the account assigned to the device. I have tried to set the Country manually in Google Play setting but am unable to do so. It does not show a current country. I also see an option for "Switch to the United States Play Store" but tapping on it doesn't do anything. Any ideas or suggestions here?
Google services
We have a cloud customer on SoTI mobicontrol who wants to block all outbound traffic in their firewall and only allow what is strictly required. I’ve provided the customer with the official system requirements for SOTI MobiControl and Android Enterprise. However, the customer is only familiar with managing Apple devices and is looking to open the absolute minimum necessary for Android Enterprise to function — particularly avoiding wildcard domains (*) where possible. Can anyone help clarify which Android Enterprise network requirements are actually essential, especially when it comes to Google services, and which ones we can safely leave out? No file sharings, and remote control will be allowed by the customer.
Google Play account: Account creation failed
Hi, I would like to ask you if there´s any Google check or limitation if the device has been enrolled to MobiControl with Google Play Account but after the enrollment device is connected in company closed network (without access to google services). Randomly on these devices after several months is displayed error message: Google Play Account: Account creation failed. Please click to try again. So of course on closed network it´s not possible to create it and it seems it´s fixed on hotspot but it takes a long time to create an account. Now I´m not sure if this notification will be displayed on these devices in closed network after several days or months. Right step is to enroll the device to MDM as AOSP but I would like to know if somebody enroll the device with google services but after that the device is moved to closed network. Is there any limitation after xx days / months? Thank you
