Developing an Event Networking Mobile Application
A networking app applies Tinder mechanics to professional contacts: swipe or mutual interest, match, chat. Plus: nearby discovery, business card exchange, meeting scheduling. All within a limited event window.
Profile and Matching
User profile: name, photo, company, title, interests/tags, goals (seeking partner / clients / open to hire). Tags are the basis for recommendation algorithm.
Matching algorithm: tag intersection + cosine similarity on interest vectors (for large tag lists). PostgreSQL side: cube extension for vector similarity or simple array && array operator for tag intersection. For events < 1000 participants—simple SQL aggregation beats any ML.
Two-way interest: "like" hidden until mutual. Implemented via interests(from_user_id, to_user_id) table, match occurs when both records exist. Webhook or polling for match notification: push via FCM with vibration and sound.
Discovery Nearby: Bluetooth and Geolocation
"People nearby" is popular for event networking. Two approaches:
Bluetooth Low Energy (BLE) beaconing: Each device periodically broadcasts userId in BLE advertisement (Custom Service UUID). Other devices listen via CBCentralManager.scanForPeripherals(withServices:) (iOS) or BluetoothLeScanner.startScan() (Android). RSSI (signal strength) approximates distance. Advantage: works without internet and GPS. Problem: iOS background BLE scanning is limited—only registered Service UUIDs.
Geolocation: CLLocationManager.requestLocation() (iOS) / FusedLocationProviderClient.getCurrentLocation() (Android). Client sends coordinates to server, server returns users within N meters. Geolocation more precise on open spaces, worse indoors.
Recommend combining: geolocation for large radius (whole venue), BLE for "standing nearby" (< 10 meters).
Contact Exchange
Three mechanics:
-
QR profile code: generate QR from
userId, scan viaAVMetadataOutput. Most universal. -
NFC bump: iOS 14+
NFCNDEFReaderSession+NFCNDEFWriterSession. AndroidNfcAdapter.enableForegroundDispatch(). Both devices need NFC, close proximity. Cool UX, requires coordinated action. -
Deep link sharing: profile link via
UIActivityViewController. Recipient opens app, adds contact. Slowest, but works without NFC or camera.
Saved contacts: list with vCard export (CNContact → .vcf via CNContactVCardSerialization). Android: ContentProviderOperation to add to system address book (needs WRITE_CONTACTS).
Meetings and Scheduling
Meeting request: propose time from available slots. Conference schedule integration: slots between bookmarked talks auto-marked as available.
Accept meeting: push notification, add to personal calendar via EventKit.EKEventStore (iOS) or CalendarContract (Android). Location: conference room, venue cafe, or custom text.
10-minute reminder: local notification. If other party cancels—push immediately.
Chat After Match
Chat opens only on mutual match. WebSocket per match or third-party SDK (Stream Chat, SendBird freemium). Message history saved for post-event access—valuable contact shouldn't be lost.
Process and Timeline
Profiles + matching + discovery + contact exchange (QR): 6–8 weeks. Meetings + NFC + schedule integration + chat: 2–3 months. Pricing calculated after requirements analysis.







