Send feedback Stay organized with collections Save and categorize content based on your preferences. Gemini is Google's largest and most capable AI model. This site contains all the info you need to start building applications with Gemini.
![Gemini Docs and API Reference | Google AI for Developers](https://cdn-ak-scissors.b.st-hatena.com/image/square/460b876dc21a9a4c6b971e3832ad555dd7f27825/height=288;version=1;width=512/https%3A%2F%2Fai.google.dev%2Fstatic%2Fsite-assets%2Fimages%2Fshare.png)
One of the key elements of Google's software engineering culture is the use of design docs for defining software designs. These are relatively informal documents that the primary author or authors of a software system or application create before they embark on the coding project. The design doc documents the high level implementation strategy and key design decisions with emphasis on the trade-of
Exposure Notifications API service update Stay organized with collections Save and categorize content based on your preferences. The Exposure Notifications API was a joint effort between Apple and Google to provide the core functionality for building Android apps to notify users of possible exposure to confirmed COVID-19 cases. For an overview of the goals of the system, see the COVID-19 informati
Google Style Guides Every major open-source project has its own style guide: a set of conventions (sometimes arbitrary) about how to write code for that project. It is much easier to understand a large codebase when all the code in it is in a consistent style. “Style” covers a lot of ground, from “use camelCase for variable names” to “never use global variables” to “never use exceptions.” This pro
Send feedback Stay organized with collections Save and categorize content based on your preferences. Every engineer is also a writer. This collection of courses and learning resources aims to improve your technical documentation. Learn how to plan and author technical documents. You can also learn about the role of technical writers at Google.
Google Engineering Practices Documentation Google has many generalized engineering practices that cover all languages and all projects. These documents represent our collective experience of various best practices that we have developed over time. It is possible that open source projects or other organizations would benefit from this knowledge, so we work to make it available publicly when possibl
Mozilla brings Microsoft, Google, the W3C, Samsung together to create cross-browser documentation on MDN Today, Mozilla is announcing a plan that grows collaboration with Microsoft, Google, and other industry leaders on MDN Web Docs. The goal is to consolidate information about web development for multiple browsers – not just Firefox. To support this collaboration, we’re forming a Product Advisory
Send feedback About this guide Stay organized with collections Save and categorize content based on your preferences. This style guide provides editorial guidelines for writing clear and consistent Google-related developer documentation. If you're new to the guide and looking for introductory topics about our style, then start with Highlights, Voice and tone, and Text-formatting summary. Otherwise
Overview LiquidFun is a 2D rigid-body and fluid simulation C++ library for games based upon Box2D. It provides support for procedural animation of physical bodies to make objects move and interact in realistic ways. Stable releases of LiquidFun are available for download from github.com/google/liquidfun/releases. LiquidFun source code is available for download from github.com/google/liquidfun. Dis
YouTube 埋め込みプレーヤーとプレーヤーのパラメータ コレクションでコンテンツを整理 必要に応じて、コンテンツの保存と分類を行います。 概要 このガイドでは、アプリケーションに YouTube プレーヤーを埋め込む方法と、YouTube 埋め込みプレーヤーで使用できるパラメータの定義を紹介します。 IFrame URL にパラメータを追加すると、アプリケーション内での再生方法をカスタマイズできます。たとえば autoplay パラメータによる動画の自動再生や、loop パラメータによる動画の繰り返し再生が可能です。enablejsapi パラメータを使用して、プレーヤーを IFrame Player API によって制御することもできます。 このページには、任意の YouTube 埋め込みプレーヤーでサポートされるすべてのパラメータが定義されています。パラメータをサポートするプレーヤ
Opening the Web Platform We are an open community of developers building resources for a better web, regardless of brand, browser or platform. Anyone can contribute and each person who does makes us stronger. Together we can continue to drive innovation on the Web to serve the greater good. It starts here, with you.
Every major open-source project has its own style guide: a set of conventions (sometimes arbitrary) about how to write code for that project. It is much easier to understand a large codebase when all the code in it is in a consistent style. “Style” covers a lot of ground, from “use camelCase for variable names” to “never use global variables” to “never use exceptions.” This project (google/stylegu
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く