Google Launches Gemini 3.6 Flash and 3.5 Flash-Lite with Distinct Use Cases

·1 views

Google made Gemini 3.6 Flash and Gemini 3.5 Flash-Lite generally available on July 21, 2026, as two distinct tiers within its Gemini API lineup. Both models support a 1-million-token context window, up to 64K output tokens, and built-in tools including Computer Use. Gemini 3.6 Flash is designed for coding, multimodal reasoning, and complex agent workflows, while the more affordable Flash-Lite targets high-volume tasks like extraction, classification, and request routing. Developers migrating existing applications must remove deprecated parameters such as temperature, top_p, and top_k, as the new models no longer accept them. Google recommends routing workloads by task type rather than treating either model as a universal replacement for previous versions.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

How to Recruit 12 Real Google Play Testers in 3-4 Days Without Paying

Google Play requires developers to have 12 opted-in testers actively using their app for 14 consecutive days before approving a public release. Paid tester services often fail because Play's fraud detection flags dormant or newly created accounts, and engagement from testers who never open the app does not count toward the requirement. Developers can instead draw from three reliable sources: their own audience such as newsletter subscribers or Discord members, community beta-swap threads on subreddits like r/androiddev and r/indiedev, and personal networks as a fallback. Warm outreach to existing followers converts at 40-50%, while anonymous forum posts convert at 5-10%, making it advisable to use multiple channels simultaneously. Keeping testers engaged through four structured check-ins over the 14-day period ensures meaningful activity that satisfies Play's requirements and also yields genuine user feedback.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer builds one-command script to snap 8 Terminal windows into ultrawide grid

A developer working with multiple Claude Code sessions on a 3440×1440 ultrawide monitor created a shell script to automatically arrange eight Terminal.app windows into a 4×2 grid with a single command. The manual process of dragging windows into position each morning was taking about a minute, prompting the automation effort. The solution combines Swift and AppleScript, using Swift to handle coordinate-system conversion between macOS's Cocoa Y-up framework and AppleScript's Y-down global coordinates. Implementation revealed five key traps, including silent failures in AppleScript's set position command, incorrect window heights, and a missing 30-pixel menu bar offset on non-primary screens. The script resolves these issues through a convergence loop that re-scans window indexes on every pass rather than relying on names or IDs.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developers Urged to Fix DOM, Rendering, and Core Web Vitals for Better SEO

A technical guide aimed at developers argues that SEO success depends less on keyword strategy and more on how a site is built and rendered. Frameworks like React, Vue, and Angular can hurt search indexing if content is only generated client-side, making server-side rendering or static site generation essential. Proper semantic HTML — using heading hierarchies and landmark tags like main, nav, and article — helps crawlers understand page structure without guessing. Core Web Vitals such as Cumulative Layout Shift can be prevented by setting image dimensions and using font-display: swap for custom fonts. Developers are also advised to audit their robots.txt for accidental crawl blocks and to generate dynamic sitemaps for sites with large volumes of user-generated content.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How ViralVidVault Secured Its PHP Admin Panel Against CSRF Attacks

A developer at ViralVidVault, a European viral-video platform, discovered a bot deleting content via cross-site request forgery (CSRF) on a staging server, exploiting the fact that browsers automatically attach session cookies to any request. The incident exposed how admin actions like deleting videos or flushing caches were protected only by login sessions, making them prime CSRF targets. The team chose the signed double-submit cookie pattern over traditional synchronizer tokens to avoid per-request session writes, which caused performance bottlenecks in their SQLite and Cloudflare-backed setup. In this approach, a random token is issued as a cookie, echoed into forms or AJAX headers, and verified server-side by matching the submitted value against the cookie — without storing anything server-side. To prevent bypass via subdomain cookie injection, the token is HMAC-signed and bound to the session ID using a server secret, following OWASP's recommended signed double-submit cookie standard.

0 comments Read more at DEV Community