AppiReview
Chilis
Lifestyle

Chilis

by Brinker International
4.3Rated 4.3 out of 5
Ratings
42K
Downloads
5M+
Advertisement
Screenshot 1Screenshot 2Screenshot 3Screenshot 4Screenshot 5Screenshot 6Screenshot 7
Advertisement

Overview

Chilis serves as the official mobile storefront and customer loyalty ecosystem for Chili's Grill & Bar, operated by Brinker International. Designed to facilitate takeout, curbside pickup, and direct home delivery, the platform functions as an omnichannel digital touchpoint bridging consumer mobile devices with physical restaurant kitchens. Constructed on a native Android development framework, the software integrates location-based mapping, digitized point management via the "My Chili's Rewards" program, and localized dynamic menu rendering.

Chilis relies on RESTful API integrations that query centralized database clusters to synchronize store-specific menus, localized item pricing, and ingredient availability with store-level Point of Sale (POS) infrastructure in real time. Users navigating the menu encounter structured categories showcasing flagship culinary items such as Baby Back Ribs, Big QP burgers, and Chicken Crispers. The application incorporates geofencing functionality through device location permissions, sending automated arrival triggers to restaurant kitchen management terminals when curbside pickup customers arrive, thereby minimizing order hold times and temperature degradation.

Despite a clean UI overhaul aimed at streamlining cart assembly and checkout paths, persistent backend integration friction remains visible. Systemic weaknesses surface primarily in cross-platform state synchronization between web sessions and mobile application profiles. Users frequently experience authentication drops and database state desynchronization, wherein accumulated perks—such as free Chips & Salsa—fail to populate within the mobile cart despite showing as active on the web desktop portal. Furthermore, automated reCAPTCHA verification loops and sudden item inventory locks during final checkout indicate execution bottlenecks within the payment gateway API layers.

Compared to competing fast-casual and casual dining applications, Chilis delivers fast reordering workflows for repeat customers, but exhibits higher operational friction regarding cross-platform account state persistence and payment session handling. To maintain user trust, future iterations must prioritize backend API reliability, cart state persistence, and seamless session handoffs.

Pros & Cons

Pros
  • Single-tap reordering capabilities allow users to instantly rebuild previous meal orders from historical transaction data.

  • Deep integration with the "My Chili's Rewards" framework offers clear visibility into active perks, tier progress, and point balances.

  • Automated location tracking and geofencing notify store staff when a pickup customer enters the parking lot.

  • Visual menu hierarchy incorporates granular dish customization options alongside high-resolution food photography.

  • Secure payment gateway processing supports major credit cards and fast digital payment modalities.

✕Cons
  • ✕

    Persistent store selection bugs frequently drop user location preferences, requiring repetitive manual store assignment.

  • ✕

    Cross-platform synchronization errors periodically cause earned rewards visible on the desktop portal to unbind within the mobile app.

  • ✕

    Overlaid animations on the shopping cart interface intermittently freeze, hindering fast menu navigation.

  • ✕

    Payment gateway execution errors periodically block checkout via unexpected reCAPTCHA failure triggers.

Advertisement

Download

FAQs

How does the application utilize GPS location data during curbside pickup?

The application uses background GPS coordinates to calculate proximity to the target store, automatically triggering an arrival notification on the kitchen staff's display when the user enters the geofenced perimeter.

Why do earned loyalty rewards sometimes disappear during mobile checkout?

Reward detachment occurs when session tokens mismatch between the native mobile client and the central user database during active cart updates.

Can users customize specific ingredient components within complex dish options?

Yes, every menu item includes sub-menus allowing users to adjust sauces, remove ingredients, swap sides, or add extra toppings prior to adding items to the cart.

Is consumer payment information stored directly on the local device hardware?

No, financial data is encrypted during transit and handled in compliance with industry data security standards rather than saved unencrypted on local device storage.

Can users browse local menus without creating an account?

Users can browse store menus, check pricing, and locate nearby branches as a guest, though saving preferences and redeeming loyalty points requires account authentication.

Hot Reviews

Summarized from Google Play reviews and community discussions.

Geolocation Reset and Location Assignment Friction

Users express frustration with persistent location assignment resets upon opening the app, which force manual store re-selection and create risk for placing orders at distant branches.

Cross-Platform Account Sync Discrepancies

Feedback highlights recurring discrepancies between web portal rewards balances and mobile cart displays, where active perks vanish during app-based checkout sessions.

Checkout Gateway and CAPTCHA Blocking

Customers note technical blocks during final payment processing caused by unexpected reCAPTCHA verification loops or false out-of-stock flags on available inventory.