Our networking mobile app for event networking offers interest matching, schedule integration, and chat after match to enhance conference app development outcomes. At a conference with 2000 attendees, finding the right person is difficult. Typical scenario: you stand by a booth while a potential partner is on the other side. A mobile networking app solves this with matching and discovery. Our experience (5+ years in mobile development, 50+ projects) guarantees quality and deadlines. In this article, we explain how we design such apps: from profiles and BLE to post-meeting chats. Create a tool that turns random encounters into valuable business connections. Order development and get a turnkey solution.
How a mobile networking app is developed
The participant profile includes name, photo, company, position, interests/tags, and goals (looking for partner / clients / open to hiring). Tags are the basis for the recommendation algorithm.
Matching algorithm is built on tag intersection and cosine similarity of interest vectors. On PostgreSQL, we use the cube extension for vector similarity or a simple array && array operator for tag intersection. For events up to 1000 participants, plain SQL aggregation is 5 times faster than ML-based alternatives. Implementation steps:
- Collect tags during registration. Use a predefined dictionary (50+ tags) and free-form input.
- Store in table
tags(user_id, tag). Index ontag. - Query:
SELECT user_id FROM tags WHERE tag = ANY(array['AI','blockchain']) GROUP BY user_id HAVING COUNT(*) > 2— finds participants with three matching tags. - Mutual interest: "like" is hidden until reciprocity. Implement via table
interests(from_user_id, to_user_id), match occurs when both records exist. Webhook or polling for match notification: push via FCM with vibration and sound.
Why we use a combination of BLE and geolocation
People nearby is a popular networking feature. BLE outperforms GPS by 10 times in indoor accuracy. Two approaches:
| Characteristic | Bluetooth Low Energy (BLE) | Geolocation (GPS) |
|---|---|---|
| Indoor accuracy | High (up to 1 m) | Low (10–50 m) |
| iOS background mode | Limited (scan only registered UUIDs) | Works in background with CLVisit |
| Power consumption | Low | Medium |
| Internet dependency | No | Yes (for coordinate transmission) |
Recommended architecture: geolocation for large radius (entire venue), BLE for standing nearby (< 10 meters). BLE uses CBCentralManager.scanForPeripherals (iOS) / BluetoothLeScanner.startScan() (Android) with custom Service UUID; RSSI gives approximate distance. Apple Developer Documentation states: "Background scanning is only available for services with registered UUID." API response time is under 200 ms.
Contact exchange: three mechanics
-
QR code profile: generate
QRCodefromuserId, scan viaAVMetadataOutput. Most universal. - NFC bump: iOS 14+
NFCNDEFReaderSession+NFCNDEFWriterSession. Android —NfcAdapter.enableForegroundDispatch(). Both devices must support NFC and be close. Great UX but requires coordinated action. Adding NFC bump functionality costs an additional $2,500. - Deep link sharing: link to profile via
UIActivityViewController. Recipient opens app, adds contact. Slowest, but works without NFC or camera.
Saved contacts: list with export to vCard (CNContact → .vcf file via CNContactVCardSerialization). On Android — ContentProviderOperation to add to system address book (requires WRITE_CONTACTS permission).
Meetings and schedule
Meeting request: participant proposes a time from available slots. Integration with conference schedule: slots between bookmarked talks are automatically marked as available.
Meeting acceptance: push notification, add to personal calendar via EventKit.EKEventStore (iOS) or CalendarContract (Android). Location: conference hall, venue coffee shop, or custom text.
Reminder 10 minutes before: local notification. If meeting is cancelled by the other party, push immediately.
Chat after match
Chat opens only on mutual match. WebSocket connection per match or ready-made SDK (Stream Chat, SendBird with freemium). Message history is saved for post-event access — valuable contacts must not be lost. Message delivery time under 100 ms under load of up to 10,000 concurrent chats.
Process and timeline
| Stage | Duration |
|---|---|
| Analytics and prototyping | 1–2 weeks |
| Backend API development | 2–3 weeks |
| Mobile app development | 4–6 weeks |
| Testing and CI/CD | 1–2 weeks |
| Store publication | 1 week |
Basic networking app development starts at $15,000. Profiles + matching + discovery + contact exchange (QR): 6–8 weeks. Meetings + NFC + schedule integration + chat: 2–3 months. Cost is calculated after requirements analysis. Thanks to test and infrastructure optimization, you reduce implementation costs. Contact us for a project assessment and budget estimate.
Server technical requirements
- PostgreSQL 14+ with `cube` extension - Node.js 18+ / Python 3.10+ for API - Redis for session caching - Docker Compose for local developmentWhat's included in development
- Documentation: API spec (OpenAPI), architecture diagram, deployment guide
- Access: App Store Connect, Google Play Console, Firebase
- Training: 2 hours for administrators, video guide for users
- Support: 1 month after release (bugs and minor fixes)
Contact us for a consultation on stack and architecture. We'll calculate a budget for your project and show how a networking app pays off through new business contacts.