Every year brings a flood of “trend” posts, but most are hype. This is my pragmatic view of what seems to actually matter so far in 2018 and what I’ve been experimenting with in my projects at iLab Africa.

1. PWAs and Instant Apps: Hype or Real Opportunity?

Progressive Web Apps (PWAs) are promising app-like experiences without app store friction, and they’re gaining traction for reaching users with limited device storage.

Android Instant Apps let users try an app without installing it. Google is pushing this hard but adoption has been slow - the development overhead is high and the ROI for small teams isn’t obvious yet.

My take: PWAs make sense for content-heavy sites. Instant Apps have potential for shopping or games but I’m not convinced the investment pays off for the kind of projects I work on. I’ve used PWAs for university projects but stick with native Android for production - you need proper offline capability and full device access too often.

2. Mobile Payments and Fintech Integration

In Kenya, mobile money is the default. M-Pesa processes billions of shillings monthly, making payment integration mandatory for practically every app.

Globally, Apple Pay and Google Pay are pushing contactless payments. For developers this means:

• Integrating payment SDKs: M-Pesa, Stripe, or PayPal depending on the market.
• Handling security: Tokenization and PCI compliance.
• Designing UX: One-tap checkouts and saved payment methods.

I’ve integrated M-Pesa APIs into several apps at iLab Africa. The hard parts are network timeouts, callback delays, and reconciliation for users with intermittent connectivity. Payment features need offline queueing and retry logic - otherwise users lose money or think they do, which is worse.

3. Cloud-Backed APIs and Serverless Backends

Firebase has matured well beyond just a real-time database. Cloud Functions, Auth, and Firestore are now viable for production without managing servers. AWS Lambda and Azure Functions are pushing serverless logic at enterprise scale too.

My current stack for most projects is still Laravel APIs on traditional servers because:

• Full control over data models.
• Easier local debugging and testing.
• Custom workflows for complex queries.

For side projects and prototypes, Firebase is noticeably faster for setting up auth and hosting. I reach for it when I need something running in an afternoon.

4. Security and Privacy as First-Class Concerns

GDPR comes into force in May this year. It’s forcing a rethink of data collection, consent, and user rights across the industry. On mobile this means:

• Explicit permissions: Location, contacts, and camera - no more requesting everything upfront.
• Secure storage: Using Android Keystore for sensitive data like auth tokens and encryption keys.
• Data minimization: Collecting only what you actually need.

I’ve started treating auth tokens and user data with a lot more care. Security isn’t just a checkbox anymore - users in African markets are increasingly aware of the risks around mobile money and health data, and they’ll ditch an app they don’t trust.

Which Trends I’m Actually Using

The things that matter most this year aren’t the flashy new features - they’re stability, offline support, and security. That’s what users with unreliable networks and expensive data actually need.