News for hackers. Stuff that matters.

jgw96

Re:Memos AI – Take notes with one button press on Monday July 24, 2023 @08:31PM (#36856164)
To use the old marketing trope: Hate taking notes? Have issues following conversations? Memos AI is what you are looking for.

I wanted to share my latest project I have been working on, Memos AI. With AI, like actually useful AI, exploding, it inspired me to rethink an old speech-to-text focused notes app I had built to see if AI could make it ACTUALLY useful.

I have been able to build something that I think is genuinely useful, especially if you take alot of notes during meetings, lectures or have trouble following conversations. It's fast, cross-platform (Web, Windows, Android, iOS, Linux etc) and hyper focused on usability. Memos AI can: - Transcribe speech with HIGH amounts of accuracy using the OpenAI Whisper model. You also get live transcriptions while recording a note. - Memos AI will analyze that transcript and generate key points, a summary and more using GPT-4 - You can then translate that note, rewrite it into an email, add an image (and any text in that image

It is built with Lit, TypeScript and the Fluent Web Components. Yes, this is a Progressive Web App, but I would challenge ANY actual, non techie consumer, to point out that its a web app.

MSFT Store: https://apps.microsoft.com/store/detail/memos-ai/9PP8DL2QTJS... Google Play: https://play.google.com/store/apps/details?id=app.recordergo... Web / iOS / Linux etc: https://www.recordergo.app

Re:Stencil – A reusable web component generator on Wednesday August 23, 2017 @04:37PM (#15084848)
Hey! Just wanted to mention that i pushed a deploy a few hours ago that changed it to a 400 font-weight.
Re:Stencil – A reusable web component generator on Wednesday August 23, 2017 @12:35PM (#15082912)
Hello all! Just to clear up the confusion here. Components built with stencil are, after compiling, just custom elements. Custom elements (the V1 of the spec) are supported in Chrome and Safari natively. According to https://www.w3counter.com/globalstats.php that means about 77.6% of users globally are running a browser that supports custom elements natively. For these browsers stencil will not load the custom elements polyfill. For IE 11, Edge and Firefox we load a 5KB gzipped custom elements polyfill automatically for you. Its also worth mentioning that Firefox and Edge are both working on custom elements, so eventually these browsers will not need the polyfill either.
Re:Stencil – A reusable web component generator on Wednesday August 23, 2017 @12:27PM (#15082833)
Hello! Good question. There are no stencil events, we just use the custom events api that is built into the browser. Therefore, you can use addEventListener.
Re:Stencil – A reusable web component generator on Wednesday August 23, 2017 @11:07AM (#15082059)
Refresh on the home page and it should be fixed (:
Re:Stencil – A reusable web component generator on Wednesday August 23, 2017 @09:01AM (#15081146)
Hello all! We just deployed a new version of the site that should solve some of these problems, thanks for the feedback.
Re:Announcing Ionic 2 Final on Wednesday January 25, 2017 @05:33PM (#13486907)
The timeline on this stuff is asap haha (:
Re:Announcing Ionic 2 Final on Wednesday January 25, 2017 @03:22PM (#13485625)
Disclosure: I also work at Ionic

So start up time is something that we are very focused on at the moment. Especially on the PWA side of things, TTI (time to interactive) is exceedingly important to ensure a good user experience. We are working on a few things at the moment but most likely the first one to hit is gonna be code splitting. So with code splitting, instead of shipping just one big bundle you will be shipping smaller bundles that are lazy loaded based on routes. This means that when the app first loads only the first bundle for the first view in your app will have to be loaded, parsed etc and then the other bundles will be lazy loaded. With this setup the browser (or webview) will never have to parse and load a huge bundle all in once, it will instead only have to deal with smaller bundles. This should give a pretty big improvement as parsing javascript is slow in every browser. From my testing on a moto g each MB of JavaScript in an ideal situation takes about 2 seconds to be parsed, so reducing the amount of JavaScript the browser has to deal with is a very fast way to get better load times.