November 2016 Summaries

The blog post discusses best practices for developing a mobile application using Stream APIs, highlighting an open-source Android example available on GitHub and submitted to the Google Play Store. It emphasizes security by advising against embedding API keys and secrets in mobile apps, recommending instead a backend API service to communicate with Stream. The app mimics Instagram, featuring functionalities like a global feed, user registration/login, photo uploads, timelines, and notification feeds, with specific endpoints described for each feature. It acknowledges shortcuts taken during development, such as simplified authentication and unsecured communication, while suggesting improvements like secure communication protocols and more efficient data handling. The post also shares insights into Android development challenges, such as styling issues with Material Design and GridView layout adjustments, and invites community feedback and contributions via GitHub.

The blog post outlines best practices for setting up activity feeds in a simple photo-sharing application, focusing on using UUIDs for unique identification to prevent collisions. It details the use of different types of feeds: flat feeds, aggregated feeds, and notification feeds. Flat feeds like "user" and "timeline" store individual user photos and allow users to follow others, respectively. Aggregated feeds, such as "timeline_aggregated," provide daily summaries of activities using a structured format for actors, verbs, and timestamps. The notification feed tracks activities like "like" or "follow" to inform users about interactions with their photos. The post also emphasizes storing activity IDs in the database to manage actions such as unfollowing or unliking. Future posts will explore backend service implementation in Go and an Android example application demonstrating these practices.

The text outlines the development of a mobile photo-sharing application using Stream APIs, focusing on backend service construction with Go and open-source libraries. The backend is designed to facilitate simple user interactions, such as uploading, liking, and following photos, utilizing a MySQL database schema for data tracking and management. The project also serves as a demonstration of best practices specific to Stream's API for activity feeds and social timelines, although it does not claim to adhere to broader industry standards in areas like authentication or error handling. The application employs the Gin framework for API endpoint development and combines GORM and gorp for database operations, while AWS S3 is used for image hosting. The app aims to minimize data processing on the client side by handling data aggregation and manipulation on the server, ensuring quick response times for mobile users. The text concludes by welcoming feedback on this open-source project through GitHub.

Imgix is a highly recommended SaaS solution for image optimization and delivery, designed to improve user experience by addressing the challenges of serving optimal images efficiently. With over 60% of a webpage's weight often being image content, Imgix offers a streamlined setup process that easily integrates with existing storage solutions like Amazon S3, allowing developers to apply various transformations and optimizations via simple URL parameters. The service utilizes advanced technologies, including proprietary hardware and open-source software, to process over a billion images daily, ensuring fast and reliable delivery through its CDN infrastructure. Despite some limitations, such as the absence of a free tier and the complexity of manually generating URL parameters without their SDKs, Imgix's scalable infrastructure and comprehensive feature set make it a valuable tool for businesses aiming to reduce page load times and enhance image quality. The company’s pricing model, which includes standard and high-volume plans, caters to different customer needs, while its robust engineering team and use of Mac Pros highlight a commitment to performance and innovation.