Lubos Belak httpstersk

Service Worker - offline support for the web

Progressive apps - high-res icon, splash screen, no URL bar, etc.

Progressive Web Apps: Escaping Tabs Without Losing Our Soul

Experiments

http://absulit.com/portfolio/demo/webvr/001/
https://www.clicktorelease.com/code/polygon-shredder/vr/ #positional
https://www.clicktorelease.com/tmp/threejs/webvr-physics/ #positional #input #haptic
https://janusweb.metacade.com/ https://github.com/jbaicoianu/janusweb/
https://jzitelli.github.io/poolvr/
https://kuva.io/block-background/ #positional #input
https://www.shadertoy.com/results?filter=vr
https://vr-batted-ball-vis.herokuapp.com/index.html

Gradient shadow in pure CSS

HTML

<button>Let's Go !</button>

How to Successfully Publish Your App on the App Store or Google Play

As someone who has released many apps starting in 2015 using frameworks such as Cordova and Ionic, and more recently using React Native and Expo, I have learned that the rules for publishing apps can change frequently and can sometimes be challenging to navigate. With that in mind, I want to provide a brief guide to help others navigate the process. While this guide may not cover every aspect of publishing an app, it does cover general tips and information that should be useful for anyone looking to release their app on the App Store or Google Play.

Metadata

Keywords, Description, Screenshots, App Name, Promo Videos

There are significant differences between Apple and Google when it comes to metadata. Apple is generally stricter than Google, so it is advisable to follow Apple's guidelines to ensure the best chances of success on both platforms. Here are some tips to keep in mind:

Keep your screenshots and promo videos separat

Cursor's Memory Bank

I am Cursor, an expert software engineer with a unique characteristic: my memory resets completely between sessions. This isn't a limitation - it's what drives me to maintain perfect documentation. After each reset, I rely ENTIRELY on my Memory Bank to understand the project and continue work effectively. I MUST read ALL memory bank files at the start of EVERY task - this is not optional.

Memory Bank Structure

The Memory Bank consists of required core files and optional context files, all in Markdown format. Files build upon each other in a clear hierarchy:

flowchart TD

	'use strict';

	class HTMLElementPlus extends HTMLElement {

	static defaultAttributeValue() {
	/* the name of the attribute is parsed in as a parameter */
	return;
	}

	static parseAttributeValue(name, value) {

	const { blocks, plugins } = wp;
	const { dispatch, select } = wp.data;

	/**
	* When a selected block is being disposed during a hot module reload, persist
	* its clientId so it may be reselected after the new module version loads.
	*
	* If the block being unloaded is currently selected, clear that selection to
	* avoid a Gutenberg error that occurs when unregistering a selected block.
	*

	import { mergeUniforms } from 'three/src/renderers/shaders/UniformsUtils.js'
	import { UniformsLib } from 'three/src/renderers/shaders/UniformsLib.js'

	export default {

	uniforms: mergeUniforms([
	UniformsLib.lights,
	UniformsLib.fog,
	]),

	# Script for converting a HF Diffusers saved pipeline to a Stable Diffusion checkpoint.
	# Only converts the UNet, VAE, and Text Encoder.
	# Does not convert optimizer state or any other thing.
	# Written by jachiam

	import argparse
	import os.path as osp

	import torch

	// Types for the result object with discriminated union
	type Success<T> = {
	data: T;
	error: null;
	};

	type Failure<E> = {
	data: null;
	error: E;
	};