[UnigramDev/Unigram/record-start-on-press](https://github.com/UnigramDev/Unigram/tree/record-start-on-press) • [131d28b](https://github.com/UnigramDev/Unigram/commit/131d28bd51c3ce8ed0d1eb029fb257aa252aeaf9) • _1 files, +19/-0_
Note the sixty-second pause and message drafts as todo

The official apps stop at sixty seconds and show the pause UI rather than
sending, which 4.3 does not, and they keep an unsent recording as a draft,
which Unigram has no notion of.

[UnigramDev/Unigram/record-start-on-press](https://github.com/UnigramDev/Unigram/tree/record-start-on-press) • [b160874](https://github.com/UnigramDev/Unigram/commit/b160874a168cd63f884059ad5dce1d7b22a27c5e) • _4 files, +185/-38_
Open the recording device on the press, not after it

The 300 ms timer that tells a hold from a tap to switch mode used to run
before device init rather than during it. A session now starts unseen and is
committed when the timer ticks, or thrown away when it doesn't, so nothing
the user can see or hear happens before that. A press only warms up where
access has already been granted, and so can never raise a consent prompt.

[#unigram](?q=%23unigram)