Office of the Deputy Commissioner, Khagrachhari · Prepared by Shohel Rana
Alutila eTicketing V2
Three products, side by side: what visitors and staff use today, and what version 2 proposes. Switch products with the tabs; each product shows the current and the proposed screens.
Reconstruction of the live page with its own images and section order: header, hero photo, ticket form, DC's message, gallery, other tourism centers, footer.
Single long form — name, email, date, mobile, quantity, total, pay — with one ticket type and no price shown until the total.
Visitor information (hours, prices, directions) is not on the page; the DC's full message sits above the gallery.
Proposed V2
Concept — matched to client design
alutila.dc-khagrachhari.gov.bd
Same sections as the live site, in order: header, hero, online ticket form, DC's message, gallery, other tourism centers, footer. Fully working above — try the Bengali/English toggle, the counters, and "সম্পূর্ণ বাণী".
Ticket form moves up beside a 3-step explainer and a ticket preview; দেশি/বিদেশি counters use today's weekday price and show the online discount as a real saving.
DC's message trimmed to one paragraph with "read full message" so the page flows on mobile; gallery becomes an editorial grid; other places get distance and area.
Photos, the DC portrait, the district seal and the SSLCommerz strip are the live site's own assets; the standalone file references them at their existing paths.
Counter app
Android app for counter staff · sell, collect and verify tickets at the gate
Current
In use at the counter
Home: four tiles. New ticket: one price per ticket (today ৳40), visitor name and mobile, quantity, date, print.
Ticket verify: camera viewfinder plus a manual code field.
Today's collection and collection list: plain lists with a refresh button; empty state is "No data found".
Proposed V2
Client design + existing screens
Client's design, merged with every screen of the current app. Fully clickable above — log in with mobile number and password (any values work in the demo), then use the bottom tabs.
New ticket: client's two-type flow; today's দেশি price comes from the weekday table (৳40 on Sunday); visitor name, mobile and date kept as an optional fold-out, and shown on the confirm screen.
Ticket verify (new tab): QR viewfinder in the same palette, manual code entry, and three clear outcomes — valid (with confirm-entry), already used (with when and by whom), not found.
Collection (new tab): today's cards, 7-day trend, type split, and the ticket list; the collection list is by day with totals. Empty states say what to do instead of "No data found".
Admin panel
For the DC office · sales records, ticket prices, app users
Current
Live today
admin.dc-khagrachhari.gov.bd/alutila/dashboard
Dashboard: six counters — today and this month, cash vs online.
Sales Records: purchase-date range and entry-date filters; counter, online and total cards, no row-level list.
Ticket Prices: one price per weekday with online and counter discount (%).
App Users: name, phone, verified/pending status, delete; new users created with a password.
Proposed V2
Client design + existing features
admin.dc-khagrachhari.gov.bd/alutila — V2
Client's design, merged with everything the current panel does. Every control works; open "Proposed" view for a larger size.
Dashboard: daily / weekly / monthly / yearly, sales trend, buyer breakdown, plus the counter-vs-online split from today's panel.
Sales Records (new page): the same date filters, a channel filter, three summary cards, and a ticket-level list with used / unused status and CSV export.
Ticket Prices (new page): weekday pricing kept, with দেশি and বিদেশি columns, online and counter discount in %, and the effective price shown live.
Ticketers: client's page, plus the current pending → approve flow and password handling — the admin sets a password when adding a ticketer (as today) and can reset it later.
Prepared by Shohel Rana · September 2026Current screens are the live products; proposed screens are concepts for discussion, not final builds.