About PugMe Events
Opening the app: location, not a schedule
Open PugMe Events and you are looking at a simple interface. The app does not show a list of upcoming events or a calendar. It shows your location. The core function is proximity-based interaction. You share your location with others attending the same event. You can see who is nearby. You can message them. You can request help. You can share the itinerary. You can receive exclusive multimedia. You can participate in polls. The app is built around the idea that events are social experiences, not just schedules.
The app does not manage tickets. It does not sell merchandise. It does not stream content. It connects people. For event organizers, wedding planners, and music festival promoters, this is the draw. PugMe is a way to increase the awesomeness of attending an event, as the developer put it in a 2015 blog post. The experience from opening the app to connecting with someone nearby is where the value lies — and where the limitations become apparent.
Location sharing vs. meaningful discovery
Tap the location sharing feature and the app broadcasts your position to other attendees. Other users can see you on a map or list. You can see them. This is the foundation of the app. The messaging feature lets you contact people close to you. You can reach out for help with the event. You can share the itinerary. You can receive exclusive multimedia from the event organizers. You can participate in polls. These are the strengths. The app gives attendees tools to interact with each other and with organizers.
The friction point is discovery. The app shows you who is nearby, but it does not tell you why you should message them. There is no profile information beyond what the user shares. There is no interest matching. There is no way to filter attendees by role, such as organizer, speaker, or VIP. You see a list of nearby people and you guess. This creates a gap. The app provides the connection mechanism but not the connection rationale. Users may not know who to message or why. The app does not surface this issue. It simply shows a list and leaves you to figure it out.
What the changelog says vs. what the app needs
The official changelog for the app reads: "Bug fixes." That is it. No mention of new features. No mention of the discovery gap. No mention of performance improvements. The developer, Rohitesh Dutta (CityNaksha), has released multiple versions — 2.67, 3.38, 3.50, 3.60, 3.65 — and the changelog has remained generic across most of them. Version 3.50 had "Fixed bugs in gifting and release update." Version 3.60 had "Fixes to deep linking." Version 3.65 simply says "Bug fixes." This is a pattern. The app works, but the developer does not communicate what actually changed.
The app has only 5 ratings on the Play Store. This is not a lot. The app is not widely used. The download count is 1K+, which is modest. The app is free. There are no in-app purchases. The business model is unclear. The app may be a side project for the developer. The lack of updates and the generic changelog suggest that the app is not actively maintained. The latest version, 3.65, was released on June 16, 2026. That is recent, but the changelog does not inspire confidence. Users are left guessing whether their issues have been addressed.
The real workflow: share, see, message, maybe connect
Here is the actual sequence for most users. Open the app. Share your location. The app shows you a list of nearby attendees. You see names or usernames. You tap one. You send a message. You wait for a reply. If the other person is active, you connect. You can share the itinerary. You can receive multimedia. You can participate in polls. The workflow is straightforward. The friction is the lack of context. You do not know why you should message someone. The app does not suggest conversation starters. It does not show common interests. It does not show session attendance. You are on your own.
The app also supports help requests. You can reach out for any help with the event. This is useful for practical issues, like finding a room or getting assistance. The app does not specify what kind of help is available. It is a generic request. The organizer can respond, but the app does not guarantee a response. The help feature is a one-way request. There is no tracking of help requests. There is no escalation path. The app is simple. It does what it says. It does not do more.
The permission model and what it means
The app requests access to personal info, messages, and photos and videos. Data is encrypted in transit. You can request that data be deleted. The app does not share data with third parties, according to the Play Store data safety section. This is a positive signal for privacy. The app is free. There are no in-app purchases. The developer is based in India. The support phone number is +918697678133. The email is [email protected].
Get File
App Specifications
| Latest Version | 3.65 |
| Uploaded by | CityNaksha |
| Requires Android | Android 6.0+ |
| Category | Events |
| Content Rating | Rated for 3+ |
Technical Details
| Package Name | ctnxa.cityConn |
| Languages | English |
| Architecture | arm64-v8a |
| Signature | f41bd572cdb8590e0fa1aaa9080c292b82668eab75675af5c986a9bdfd3e70cb |
Security & Additional Info
| Scan Result | Secure |
| Package Name | ctnxa.cityConn |
| SHA‑256 | f41bd572cdb8590e0fa1aaa9080c292b82668eab75675af5c986a9bdfd3e70cb |
| SHA‑1 | 4e0618e0eec2d4d5fcb5fbdf75f5d3e5eea3fc8b |
| App Permissions | 0 |