<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Kevin on Medium]]></title>
        <description><![CDATA[Stories by Kevin on Medium]]></description>
        <link>https://medium.com/@kevinzhow?source=rss-188ffe4b279a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*bKg7r8Dl2WiJ3sY2.jpeg</url>
            <title>Stories by Kevin on Medium</title>
            <link>https://medium.com/@kevinzhow?source=rss-188ffe4b279a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 23:03:40 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kevinzhow/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Introducing the new Japanese “OCR Desk” feature in “Oyomi”.]]></title>
            <link>https://kevinzhow.medium.com/introduce-the-new-japanese-ocr-desk-feature-in-oyomi-8d2751e2f0d4?source=rss-188ffe4b279a------2</link>
            <guid isPermaLink="false">https://medium.com/p/8d2751e2f0d4</guid>
            <category><![CDATA[japanese]]></category>
            <category><![CDATA[oyomi]]></category>
            <category><![CDATA[ocr]]></category>
            <dc:creator><![CDATA[Kevin]]></dc:creator>
            <pubDate>Fri, 28 Jul 2023 03:57:41 GMT</pubDate>
            <atom:updated>2023-07-28T03:58:33.913Z</atom:updated>
            <content:encoded><![CDATA[<p>Recently, I’ve had to read a lot of Japanese materials, such as news, books, manga, and so on. The complexity of these situations has led to a series of pain points with OCR, prompting some new ideas for “Oyomi’s” OCR feature.</p><p>The results are as follows, welcome to watch, like, and share with your good friends!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FcmHXzI0MRK4%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DcmHXzI0MRK4&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FcmHXzI0MRK4%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/7a4cd371111518bea49c552776b5440b/href">https://medium.com/media/7a4cd371111518bea49c552776b5440b/href</a></iframe><h3>Reading books, repeatedly taking photos</h3><p>I’ve recently borrowed some Japanese books from the library. When reading, it’s like being illiterate. I have to scan each page with “Oyomi”, then check what the pronunciations of the kanji are, and look up some characters I don’t recognize.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FkfLoCfmCqVFFBZQxPF8OQ.png" /></figure><p>A common process is:</p><ol><li>Take a photo of a page of the book</li><li>Hope to choose an area for analysis</li><li>Add to the vocabulary book</li><li>After reading, take a photo of the next page</li></ol><p>So, for this process, I’ve made a series of adjustments. Also, a shortcut to choose new images has been added to the upper left corner. Users can continue to operate other images without leaving this page, which truly makes it an OCR workbench.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nB_3LNlwVnQVbxsL7vJ1sw.png" /></figure><h3>Comics, newspapers, area selection</h3><p>When reading comics and newspapers, the content is often scattered and the text is usually less correlated, so you need to accurately select the content of a certain area.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6dF4mA5IO0wocjbsbBpHNA.png" /></figure><p>And for scenarios like comics, a “Manga mode” has been added to the settings. This can merge the selected text to avoid unexpected segmentation issues.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zSWsq1o-OqBx19I-8zV-3w.png" /></figure><h3>Close reading, line-by-line proofreading</h3><p>For some more rigorous materials, you need to be able to do line-by-line proofreading. “Oyomi” has implemented an automatic positioning function at this stage, i.e., when editing the text box, the image will automatically locate to the corresponding position of the text box and highlight it in yellow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xE6m7bZi8mWSeQjZ_tm9Ng.png" /></figure><p>However, there is still room for continuous optimization in terms of recognition accuracy in this stage.</p><h3>OCR history</h3><p>In line with the above features, the history has also undergone a major upgrade. All analyzed content can be brought up for re-analysis at any time, and the last edited state will be perfectly recorded.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mXs20WGxrdcP1TFrasmlDw.png" /></figure><h3>Conclusion</h3><p>That’s the main features of this OCR workbench update. If you have usage scenarios that you hope I can optimize for, feel free to contact me through the feedback in the app.</p><h3>Free Download</h3><p>The iOS and Android versions of “Oyomi” have both rolled out this update.</p><p><a href="https://apps.apple.com/us/app/oyomi-japanese-reader/id1474251984">App Store</a></p><p><a href="https://play.google.com/store/apps/details?id=com.kevinzhow.pengdu">Google Play</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8d2751e2f0d4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Swift on Server Tour 2: Connecting Your Database to the Server]]></title>
            <link>https://kevinzhow.medium.com/swift-on-server-tour-2-connecting-your-database-to-the-server-2e8debeb5ee1?source=rss-188ffe4b279a------2</link>
            <guid isPermaLink="false">https://medium.com/p/2e8debeb5ee1</guid>
            <category><![CDATA[swiftonserver]]></category>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[swiftonservertour]]></category>
            <dc:creator><![CDATA[Kevin]]></dc:creator>
            <pubDate>Tue, 11 Jul 2023 06:37:41 GMT</pubDate>
            <atom:updated>2023-07-11T06:37:41.945Z</atom:updated>
            <content:encoded><![CDATA[<p>In this chapter, we will design the data model for posts in Micro Blog and use PostgreSQL as our database to store the content. Finally, we will write a unit test to test the creation of posts.</p><h3>Designing the Post Data Model</h3><p>In the microblog system we typically use, posts are created by users. Therefore, the usual order for designing the data model is to design the user first and then design the post data model.</p><p>But in order to better understand how to build relationships between data, I have decided to start with the post data model this time.</p><p>A simple post has the following two properties:</p><ul><li>content: The content of the post.</li><li>createdAt: The creation time.</li></ul><p>If we represent our data in a table, it would look like this:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/278b8ad203b7c67972580caf1198ee1d/href">https://medium.com/media/278b8ad203b7c67972580caf1198ee1d/href</a></iframe><p>As more data is published, the table content would look like this:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2db39d3618eb38e5f3fe20394f347f4f/href">https://medium.com/media/2db39d3618eb38e5f3fe20394f347f4f/href</a></iframe><p>It is best to add a unique ID to each record so that we can refer to a specific post quickly and accurately using the ID.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/6042501af29019eb5619c61832db9f3d/href">https://medium.com/media/6042501af29019eb5619c61832db9f3d/href</a></iframe><blockquote><em>In fact, when data is stored in a database, it is stored in tables similar to this.</em></blockquote><p>Next, let’s try using a class in Swift to represent this data structure.</p><pre>class Post {<br>    let id: Int<br>    let content: String<br>    let createdAt: Date<br>}</pre><p>In this way, we have the most basic state of the Post data model.</p><h3>Introducing Post to Vapor</h3><p>Currently, Vapor doesn’t know how to interact with the Post data type in the database because we haven’t provided enough information to Vapor yet. For example:</p><ol><li>Vapor doesn’t know the mapping between the Post data model and the “table structure stored in the database”.</li><li>Vapor doesn’t know what database we are using or how to connect to it.</li></ol><p>Let’s solve these problems step by step.</p><h3>Writing Post as a Vapor Model</h3><p>Vapor uses its own Fluent to communicate with the database, and this functionality is commonly referred to as Object-relational mapping (ORM).</p><p>We modify Package.swift to add the Fluent dependency. Since we are no longer a simple HelloWorld, let&#39;s also change the name to MicroBlog.</p><pre>// swift-tools-version:5.8<br>import PackageDescription<br>let package = Package(<br>    name: &quot;MicroBlog&quot;,<br>    platforms: [<br>       .macOS(.v12)<br>    ],<br>    dependencies: [<br>        .package(url: &quot;https://github.com/vapor/vapor.git&quot;, from: &quot;4.77.0&quot;),<br>        .package(url: &quot;https://github.com/vapor/fluent.git&quot;, from: &quot;4.4.0&quot;),<br>    ],<br>    targets: [<br>        .executableTarget(<br>            name: &quot;App&quot;,<br>            dependencies: [<br>                .product(name: &quot;Vapor&quot;, package: &quot;vapor&quot;),<br>                .product(name: &quot;Fluent&quot;, package: &quot;fluent&quot;),<br>            ]<br>        ),<br>    ]<br>)</pre><p>Next, we create Sources/App/Models/Post.swift.</p><pre>import Vapor<br>import Fluent<br><br>final class Post: Model {<br>    // The name of the table in the database.<br>    static let schema = &quot;posts&quot;<br>    // The unique identifier.<br>    @ID(key: .id)<br>    var id: UUID?<br>    // The content.<br>    @Field(key: &quot;content&quot;)<br>    var content: String<br>    // The creation time.<br>    @Timestamp(key: &quot;created_at&quot;, on: .create)<br>    var createdAt: Date?<br>    init() { }<br>    init(id: UUID? = nil, content: String) {<br>        self.id = id<br>        self.content = content<br>    }<br>}</pre><p>In Vapor, we use some Property Wrappers to assist in mapping the model to the database table.</p><ul><li>schema is the &quot;table name&quot; where this type of data is stored in the database, which is posts in this case.</li><li>@ID is the &quot;unique identifier&quot; of the data in the database table. By default, Vapor recommends using a UUID random string as the ID and will use the string id as the field name in the database table. You can modify this field name by using @ID(custom: &quot;&quot;).</li><li>@Field represents the data attribute to be stored in the database. With @Field(key: &quot;content&quot;), we explicitly declare that var content: String corresponds to the content field in the database table.</li><li>@Timestamp is a special type of @Field used to represent time-based storage. It also has a trigger feature. Here, we use on: .create to indicate that the time should be automatically recorded when a Post is created.</li></ul><p>Now Vapor recognizes the Post data type.</p><h3>Starting a PostgreSQL Database Using Docker</h3><p>We use PostgreSQL as our database service. Installing PostgreSQL directly on a computer can be complex, but Docker simplifies this process.</p><blockquote><em>Docker is a lightweight containerization technology that bundles the runtime needed by an app into a sandbox environment. With this technology, we can seamlessly start other apps on a Linux system without having to install various dependencies on the host. You can use this technology by installing </em><a href="https://www.docker.com/products/docker-desktop/"><em>Docker Desktop</em></a><em>.</em></blockquote><h3>Writing a docker-compose.yml</h3><p>docker-compose.yml is a container orchestration file. In this file, we describe the container Apps we need and their environment variables, network settings, etc.</p><p>First, create docker-compose.yml in the root directory of the project and write the following content</p><pre>version: &#39;3.7&#39;  # Defines the version of the Docker Compose file, version 3.7 is used here<br>volumes:  # Defines the volumes part<br>  db_data:  # Docker will use this key as the name, and automatically create the db_data volume to store data<br>services:  # Defines the services part<br>  db:  # db service configuration<br>    image: &#39;postgres:15-alpine&#39;  # Uses the image of PostgreSQL 15 Alpine version<br>    volumes:  # Defines the mounted volumes<br>      - &#39;db_data:/var/lib/postgresql/data/pgdata&#39;  # Mounts the db_data volume to the /var/lib/postgresql/data/pgdata directory in the container<br>    environment:  # Defines the environment variables<br>      PGDATA: &#39;/var/lib/postgresql/data/pgdata&#39;  # Sets the PGDATA environment variable to /var/lib/postgresql/data/pgdata<br>      POSTGRES_USER: &#39;vapor_username&#39;  # Sets the POSTGRES_USER environment variable to vapor_username<br>      POSTGRES_PASSWORD: &#39;vapor_password&#39;  # Sets the POSTGRES_PASSWORD environment variable to vapor_password<br>      POSTGRES_DB: &#39;vapor_database&#39;  # Sets the POSTGRES_DB environment variable to vapor_database<br>    ports:  # Defines port mapping, maps the host&#39;s 5432 port to the container&#39;s 5432 port<br>      - &#39;5432:5432&#39;</pre><p>Now, we go to the location of docker-compose.yml in the terminal and use the command docker-compose up db to start the database service. The database will listen on port 5432 on the local machine.</p><blockquote><em>If you see this error: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? Please check whether Docker Desktop is started.</em></blockquote><h3>Letting Vapor Connect to the Database</h3><p>Next, our goal is to let Vapor get our server information and connect to our server.</p><p>We first modify Package.swift to add Fluent support for PostgreSQL</p><pre>// swift-tools-version:5.8<br>import PackageDescription<br>let package = Package(<br>    name: &quot;MicroBlog&quot;,<br>    platforms: [<br>       .macOS(.v12)<br>    ],<br>    dependencies: [<br>        .package(url: &quot;https://github.com/vapor/vapor.git&quot;, from: &quot;4.77.0&quot;),<br>        .package(url: &quot;https://github.com/vapor/fluent.git&quot;, from: &quot;4.4.0&quot;),<br>        .package(url: &quot;https://github.com/vapor/fluent-postgres-driver.git&quot;, from: &quot;2.7.2&quot;),<br>    ],<br>    targets: [<br>        .executableTarget(<br>            name: &quot;App&quot;,<br>            dependencies: [<br>                .product(name: &quot;Vapor&quot;, package: &quot;vapor&quot;),<br>                .product(name: &quot;Fluent&quot;, package: &quot;fluent&quot;),<br>                .product(name: &quot;FluentPostgresDriver&quot;, package: &quot;fluent-postgres-driver&quot;),<br>            ]<br>        ),<br>    ]<br>)</pre><p>Then, add the database connection information in Sources/App/main.swift</p><pre>// ...<br>app.databases.use(.postgres(configuration: SQLPostgresConfiguration(<br>    hostname: &quot;localhost&quot;,<br>    port: 5432,<br>    username: &quot;vapor_username&quot;,<br>    password: &quot;vapor_password&quot;,<br>    database: &quot;vapor_database&quot;,<br>    tls: .prefer(try .init(configuration: .clientDefault)))<br>), as: .psql)<br><br>try app.run()</pre><p>At this point, Vapor knows how to connect to the database. However, the database is still a blank slate and does not have the tables we need. Therefore, finally, we need to write something called a Migration to update the table structure on the database.</p><h3>Creating a Database Table Using Migration</h3><p>Migration is a function in Fluent used to migrate the structure of database tables. Next, we will learn how to use this tool.</p><p>Write the following content in Sources/App/Migrations/1_CreatePost.swift</p><pre>import Fluent <br><br>// Define CreatePost struct, implement AsyncMigration protocol<br>struct CreatePost: AsyncMigration { <br>    // Prepare method, prepare operations on the database<br>    func prepare(on database: Database) async throws { <br>        // Create database schema object for the Post table<br>        try await database.schema(Post.schema)  <br>            .id()  // Add id column<br>            .field(&quot;content&quot;, .string, .required)  // Add content column, type is string, cannot be null<br>            .field(&quot;created_at&quot;, .datetime)  // Add created_at column, type is date time<br>            .create()  // Create Post table<br>    }<br>   // Revert method, rollback operations on the database<br>    func revert(on database: Database) async throws { <br>        try await database.schema(Post.schema).delete()  // Delete the database schema object of the Post table<br>    }<br>}</pre><p>At runtime, the above code will be converted into SQL statements. For example, the code in prepare will be converted into the following SQL code</p><pre>CREATE TABLE IF NOT EXISTS public.posts<br>(<br>    id uuid NOT NULL,<br>    content text COLLATE pg_catalog.&quot;default&quot; NOT NULL,<br>    created_at timestamp with time zone,<br>    CONSTRAINT posts_pkey PRIMARY KEY (id)<br>)</pre><p>Therefore, Migration is just Fluent’s ORM encapsulation of SQL. Through this encapsulation, we can greatly reduce errors when writing SQL, and improve performance by optimizing common SQL statement scenarios.</p><p>If you need to use advanced features of the database, Fluent also supports direct use of SQL statements for Migration.</p><h3>Register and Run Migration</h3><p>We need to register CreatePost in Sources/main.swit so that our app knows what content it will be dealing with when we run the migration later.</p><pre>//...<br>app.migrations.add([CreatePost()])<br><br>try app.run()</pre><p>Now, execute swift run App migrate in the root directory of the project, and enter y to complete the update of the table structure in the database.</p><pre>The following migration(s) will be prepared:<br>+ App.CreatePost on default<br>Would you like to continue?<br>y/n&gt; y</pre><h3>Write Unit Test to Test Post CURD</h3><p>Next, we will write a unit test to test the post creation function. Write the following content in Tests/AppTests/PostTests.swift.</p><blockquote><em>Writing unit tests can perform automated tests for functions, ensuring that our server functions do not have exceptions. We will continue to discuss the use of unit tests in subsequent chapters.</em></blockquote><pre>@testable import App<br>import XCTVapor<br><br>final class PostTests: XCTestCase {<br>    func testCreateUser() async throws {<br>        let app = Application(.testing)<br>        defer { app.shutdown() }<br>        <br>        // autoRevert will automatically perform all the content in revert in Migration<br>        try await app.autoRevert()<br>        // autoMigrate will automatically perform all the content in prepare in Migration<br>        // These two steps will rebuild our database, providing us with a clean testing environment<br>        try await app.autoMigrate()<br>        let post = Post(content: &quot;Hello, world!&quot;)<br>        <br>        try await post.save(on: app.db)<br>        let postID = try? post.requireID()<br>        // If postID is not nil, it is successfully created, and the test passes<br>        XCTAssertNotNil(postID)<br>    }<br>}</pre><p>Then, modify our Package.swift file to add a description about Test.</p><pre>// swift-tools-version:5.8<br>import PackageDescription<br><br>let package = Package(<br>    name: &quot;MicroBlog&quot;,<br>    platforms: [<br>       .macOS(.v12)<br>    ],<br>    dependencies: [<br>        .package(url: &quot;https://github.com/vapor/vapor.git&quot;, from: &quot;4.77.0&quot;),<br>        .package(url: &quot;https://github.com/vapor/fluent.git&quot;, from: &quot;4.4.0&quot;),<br>        .package(url: &quot;https://github.com/vapor/fluent-postgres-driver.git&quot;, from: &quot;2.7.2&quot;),<br>    ],<br>    targets: [<br>        .executableTarget(<br>            name: &quot;App&quot;,<br>            dependencies: [<br>                .product(name: &quot;Vapor&quot;, package: &quot;vapor&quot;),<br>                .product(name: &quot;Fluent&quot;, package: &quot;fluent&quot;),<br>                .product(name: &quot;FluentPostgresDriver&quot;, package: &quot;fluent-postgres-driver&quot;),<br>            ]<br>        ),<br>        .testTarget(name: &quot;AppTests&quot;, dependencies: [<br>            .target(name: &quot;App&quot;),<br>            .product(name: &quot;XCTVapor&quot;, package: &quot;vapor&quot;),<br>        ])<br>    ]<br>)</pre><p>Now, we can run unit tests by executing swift test at the path where Package.swift is located.</p><p>We will now get a prompt that the test has not passed.</p><pre>FluentKit/Databases.swift:162: Fatal error: No default database configured.<br>error: Exited with signal code 5</pre><p>This is because the content about database connection written in main.swift will not be executed in the test. We need to refactor this part of the code so that both sides can use it.</p><h3>Refactor App Initialization Using configure.swift</h3><p>Write the following code in Sources/App/configure.swift</p><pre>import Fluent<br>import FluentPostgresDriver<br>import Vapor<br><br>public func configure(_ app: Application) async throws {<br>    app.databases.use(.postgres(configuration: SQLPostgresConfiguration(<br>        hostname: &quot;localhost&quot;,<br>        port: 5432,<br>        username: &quot;vapor_username&quot;,<br>        password: &quot;vapor_password&quot;,<br>        database: &quot;vapor_database&quot;,<br>        tls: .prefer(try .init(configuration: .clientDefault)))<br>    ), as: .psql)<br>    app.migrations.add([CreatePost()])<br>}</pre><p>Modify main.swift to use configure</p><pre>import Vapor<br>import Fluent<br>import FluentPostgresDriver<br><br>let app = Application()<br>app.http.server.configuration.port = 8080<br>defer { app.shutdown() }<br>app.get { req async in<br>    &quot;It works!&quot;<br>}<br>try await configure(app)<br>try app.run()</pre><p>Modify PostTests.swift to use configure</p><pre>@testable import App<br>import XCTVapor<br><br>final class PostTests: XCTestCase {<br>    func testCreateUser() async throws {<br>        let app = Application(.testing)<br>        defer { app.shutdown() }<br>        try await configure(app)<br>        <br>        // autoRevert will automatically perform all the content in revert in Migration<br>        try await app.autoRevert()<br>        // autoMigrate will automatically perform all the content in prepare in Migration<br>        // These two steps will rebuild our database, providing us with a clean testing environment<br>        try await app.autoMigrate()<br>        let post = Post(content: &quot;Hello, world!&quot;)<br>        <br>        try await post.save(on: app.db)<br>        let postID = try? post.requireID()<br>        // If postID is not nil, it is successfully created, and the test passes<br>        XCTAssertNotNil(postID)<br>    }<br>}</pre><p>Now run swift test we will see the test pass message</p><p>Test Case &#39;-[AppTests.PostTests testCreateUser]&#39; passed (0.263 seconds).</p><p>Congratulations, Vapor and the database are connected!</p><h3>Code for This Chapter</h3><p>You can find the relevant code for this chapter at <a href="https://github.com/kevinzhow/swift-on-server-tour/tree/main/2">https://github.com/kevinzhow/swift-on-server-tour/tree/main/2</a></p><h3>Extension: View Database Content Using pgAdmin</h3><p>If you want to see what content has been created in the database, you can connect to PostgreSQL using pgAdmin.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NQeG6LtNMPqR2W6x2Vf0aA.png" /></figure><h3>Preview of Next Chapter</h3><p>In the next chapter, we will write APIs to implement Post’s CURD (Create Update Read Delete) and further learn about testing.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2e8debeb5ee1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Swift on Server Tour 1: Your First Server App and Its Story]]></title>
            <link>https://kevinzhow.medium.com/swift-on-server-tour-1-your-first-server-app-and-its-story-a46d1f0bd81a?source=rss-188ffe4b279a------2</link>
            <guid isPermaLink="false">https://medium.com/p/a46d1f0bd81a</guid>
            <category><![CDATA[swiftonserver]]></category>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[swiftonservertour]]></category>
            <dc:creator><![CDATA[Kevin]]></dc:creator>
            <pubDate>Mon, 26 Jun 2023 12:58:48 GMT</pubDate>
            <atom:updated>2023-06-26T12:58:48.921Z</atom:updated>
            <content:encoded><![CDATA[<p>In this chapter, we will learn how to set up the development environment for Swift on Server and create our first server-side Hello, World app. Additionally, we’ll briefly discuss some technical details behind accessing the server app.</p><h3>Setting up the Swift on Server Development Environment</h3><p>Thanks to Swift’s open-source nature, Swift can be developed on Linux as well. With the efforts of the <a href="https://www.swift.org/sswg/">Swift Server Workgroup</a>, VSCode has become a competent Swift editor. Therefore, to ensure readability for different types of users, this series of articles will use VSCode as the editor.</p><h3>Installing Swift</h3><p>Apple’s <a href="https://www.swift.org/download/">Download Swift</a> provides installation guides for different platforms. Unfortunately, Swift for Linux is not available in the official repositories of major distributions. Hence, Linux users will need to explore alternative installation methods.</p><h3>Configuring VSCode</h3><p>Simply install the <a href="https://marketplace.visualstudio.com/items?itemName=sswg.swift-lang">Swift Extension for Visual Studio Code</a> plugin.</p><h3>Creating Hello World</h3><p>I created a folder named “1” to store the code for this chapter. You can also create it using the following command:</p><pre>mkdir 1</pre><p>As a Swift project, the first thing we need to do is create a Package.swift file to describe the project:</p><pre>// swift-tools-version:5.8<br>import PackageDescription<br>let package = Package(<br>    name: &quot;HelloWorld&quot;,<br>    platforms: [<br>       .macOS(.v12)<br>    ],<br>    dependencies: [<br>        .package(url: &quot;https://github.com/vapor/vapor.git&quot;, from: &quot;4.77.0&quot;),<br>    ],<br>    targets: [<br>        .executableTarget(<br>            name: &quot;App&quot;,<br>            dependencies: [<br>                .product(name: &quot;Vapor&quot;, package: &quot;vapor&quot;)<br>            ]<br>        ),<br>    ]<br>)</pre><p>Next, create the 1/Sources/App/main.swift file:</p><pre>import Vapor<br>let app = Application()<br>app.http.server.configuration.port = 8080<br>defer { app.shutdown() }<br>app.get { req async in<br>    &quot;It works!&quot;<br>}<br>try app.run()</pre><p>To run the code, use swift run in the root directory of the &quot;1&quot; folder, or click the &quot;Run &amp; Debug&quot; option in VSCode.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RNA6nuo5cxM_DKPDIPPlzA.png" /></figure><blockquote><em>Usually, when you save the </em><em>Package.swift file, the Swift extension for VSCode will automatically generate a </em><em>.vscode/launch.json file in the project&#39;s root directory, enabling the Run &amp; Debug functionality.</em></blockquote><p>After compilation, you will see a message indicating that the server is running:</p><pre>[Vapor] Server starting on http://127.0.0.1:8080</pre><p>Access <a href="http://127.0.0.1:8080/">http://127.0.0.1:8080</a> in your browser, and you will see the familiar “It works!” message.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BZquRMrUig_ZQuVyOP79rg.png" /></figure><p>Congratulations, your first server app is up and running!</p><h3>How Does the Browser Access the Server App?</h3><p>To understand this question, let’s start with the URL the browser accesses: <a href="http://127.0.0.1:8080/hello">http://127.0.0.1:8080</a>. This URL can be broken down into three parts:</p><ul><li>http: the desired protocol</li><li>127.0.0.1: the IP address to access</li><li>8080: the port on the machine corresponding to the IP address to access</li></ul><p>When you press enter, the browser uses the HTTP protocol to create the following request:</p><pre>GET / HTTP/1.1<br>Host: 127.0.0.1:8080</pre><p>This request is then sent to the machine represented by the IP address 127.0.0.1, which is the loopback address for the local machine, and is delivered to the server app waiting on port 8080.</p><blockquote><em>127.0.0.1 is a special reserved address that represents the local machine. When this address is used, it actually points to the machine that made the request.</em></blockquote><p>Now let’s review what the server app’s code does:</p><pre>// Listen on port 8080 of the local machine<br>app.http.server.configuration.port = 8080<br>// If a request arrives with a GET method and path &quot;/&quot;<br>app.get { req async in<br>    &quot;It works!&quot;<br>}</pre><p>In reality, our server app sends back a response like this:</p><pre>HTTP/1.1 200 OK<br>content-type: text/plain; charset=utf-8<br>content-length: 9<br><br>It works!</pre><p>When the browser receives this response, it first learns from the 200 status code that the request was successful. The content-type section indicates that the returned data is plain text encoded in UTF-8, and the content-length indicates that the length of the content is 9.</p><p>Based on this information, the browser decides to display the text “It works!” on the page.</p><p>This back-and-forth data exchange is the most basic functionality of a server app. Behind it, the TCP/IP network protocol stack supports the communication. TCP/IP is a sophisticated and complex protocol, and HTTP, as shown above, is just the topmost application layer in the TCP/IP four-layer model.</p><p>Building a simple server app doesn’t require in-depth knowledge of TCP/IP. However, as the business grows and faces more complex problems, understanding TCP/IP can help us solve many issues. However, this topic is beyond the scope of this article series. I encourage readers to explore it according to their future business needs.</p><p>The code of this chapter can be found on GitHub at <a href="https://github.com/kevinzhow/swift-on-server-tour">https://github.com/kevinzhow/swift-on-server-tour</a>.</p><h3>Preview of the Next Chapter</h3><p>In the next chapter, we will start using Vapor to connect to a database, perform CRUD operations, and explore how these operations are implemented behind the scenes.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a46d1f0bd81a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Swift on Server Tour 0: Why this could be a good choice for you]]></title>
            <link>https://kevinzhow.medium.com/swift-on-server-tour-0-why-this-could-be-a-good-choice-for-you-f842d6ddaa03?source=rss-188ffe4b279a------2</link>
            <guid isPermaLink="false">https://medium.com/p/f842d6ddaa03</guid>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[swiftonservertour]]></category>
            <category><![CDATA[swiftonserver]]></category>
            <dc:creator><![CDATA[Kevin]]></dc:creator>
            <pubDate>Mon, 12 Jun 2023 01:20:51 GMT</pubDate>
            <atom:updated>2023-06-12T01:43:59.457Z</atom:updated>
            <content:encoded><![CDATA[<h3>Background</h3><p>Before using Swift on Server, the web framework I was most familiar with was Ruby on Rails. In addition, I have also used Python, NodeJS, Elixir, and Go to develop backend services. However, when it came to developing the backend service for my app “Oyomi,” I weighed my options and ultimately chose Swift on Server.</p><p>In this chapter, I will share why I made this decision and why it has proven to be the right choice in the following three years. If you are in a similar situation, I believe you will benefit from this.</p><blockquote><a href="https://apps.apple.com/cn/app/id1474251984"><em>Oyomi</em></a><em> — a Japanese grammar analysis app based on machine learning</em></blockquote><h3>Starting with a Standalone App</h3><p>When I first developed Oyomi in 2019, it was designed as a standalone product. The original intention was to ensure that the product could continue to run well even if I was no longer involved, allowing users to make a one-time purchase and use it permanently.</p><p>The reason for designing it as a standalone product was twofold:</p><ol><li>Educational resources should be easily accessible to ensure fairness.</li><li>I needed to keep the operating costs of the product low enough to sell it cheaply, so that more people could afford it.</li></ol><p>However, as time went on, updating the machine learning models for Oyomi became problematic.</p><p>In a standalone situation, model updates depended entirely on whether users updated the app. Therefore, I could not guarantee that every user would use the latest models in a timely manner, leading to a poor user experience. In addition, users gradually accumulated a lot of learning data, which made it difficult for them to use the app across different devices without cloud synchronization, and it was easy to lose data.</p><p>Therefore, to solve the conflict between “user experience” and “standalone,” in 2021, I decided to develop a backend for Oyomi.</p><h3>Requirements-Driven Selection</h3><p>Before researching technical solutions, let’s first look at the requirements for Oyomi’s backend:</p><ul><li>Oyomi’s algorithm logic is already written in Swift, and rewriting it would greatly slow down my development efficiency.</li><li>Oyomi uses many C libraries to support its algorithms, so integration with C libraries should be straightforward.</li><li>The performance of the backend server must be good enough so that users hardly have to wait.</li><li>The resource consumption during server runtime must be low enough so that I don’t have to spend a lot of money on high-end servers when configuring multiple nodes for high availability.</li></ul><h3>Ruby on Rails’ Pros and Cons</h3><p>Let’s take Ruby on Rails as an example. This is a web framework that I have been using since 2013 and have always been a fan of. So, let’s first look at its pros and cons.</p><p>Pros:</p><ul><li>Can efficiently complete business requirements.</li><li>The ecosystem is comprehensive, with open-source implementations for most common business functions.</li><li>It is easy to find partners who use this technology.</li><li>It is easy to find learning materials.</li></ul><p>Cons:</p><ul><li>Performance is average (can be optimized by writing modules that consume a lot of computing power in other compiled languages).</li><li>Memory consumption is relatively high.</li><li>Interoperability with C libraries is somewhat difficult.</li><li>Concurrency capability is weak (can be optimized through multithreading, multiple instances, and multiple nodes).</li></ul><h3>Swift on Server’s Pros and Cons</h3><p>In contrast, what are the pros and cons of Swift on Server?</p><p>Pros:</p><ul><li>Can reuse code from iOS apps and the Swift ecosystem.</li><li>A compiled language is very stable.</li><li>Integration with C libraries is very easy and natural, and Swift 5.9 has improved integration with C++ this year.</li><li>It has excellent performance and very low memory consumption, which means it saves a lot of money.</li><li>The entire ecosystem uses the design concept of non-blocking I/O, and support for high concurrency is very good.</li></ul><p>Cons:</p><ul><li>As a server-side technology, it is not mainstream, and most services do not have corresponding SDKs.</li><li>It is difficult to find partners who learn Swift on Server.</li><li>Learning materials are scarce.</li></ul><p>In addition, Swift has 3 additional advantages for me:</p><ul><li>It is very pleasant to write in this language.</li><li>Swift community is very active</li><li>Apple invests heavily in it, providing many surprises every year.</li></ul><p>Therefore, for me, as long as I play to Swift on Server’s strengths, overcome its weaknesses, it is a perfect choice.</p><h3>Overcoming Swift on Server’s Inherent Disadvantages</h3><p>Just as scripting languages can borrow from other languages to supplement their shortcomings, Swift can also borrow from other language ecosystems to supplement its shortcomings. In this Cloud Native era, with the help of microservices and Serverless, we can easily solve these problems.</p><h3>Solving the Problem of Lack of Third-Party Service SDKs</h3><p>Take Azure as an example. Azure’s TTS service does not provide a Swift backend SDK, but it is easy to find SDKs for other languages such as Python and NodeJS.</p><p>My solution is to deploy the JS code that interacts with Azure’s TTS service to AWS Lambda. When the server app needs to interact with TTS, it uses HTTP to request this Lambda function.</p><p>The advantages of this solution are as follows:</p><ul><li>The Lambda function can be written very simply, such as in the case of TTS, I only have 60 lines of code.</li><li>The runtime environment of the Lambda function is completely separate from that of our server app, so it does not consume additional resources, and there is no impact between them at runtime.</li><li>The free quota for AWS Lambda is sufficient, and you hardly ever need to pay money.</li></ul><h3>Solving the Problem of Technological Inclusiveness</h3><p>We are often faced with a problem of liking Swift, he may like Rust, and others may like Go or other languages.</p><p>When I chose Swift on Server, was I cut off from other people’s worlds?</p><p>Of course not! Through a well-designed and reasonable microservices architecture, you can easily use completely different languages and technologies in different business modules. Compared with implementing a large monolithic application in one language, this brings two direct benefits:</p><ul><li>Each language has its own strengths, and using microservices can easily integrate different technologies to work together.</li><li>Everyone can choose their favorite technology to achieve their goals, which can make them happy.</li></ul><h3>Using Swift on Server for Three Years</h3><p>Since the server went online in 2021, it has run efficiently and stably for three years. During this period, the business has expanded from a user system and grammar analysis to a payment system, billing system, and later a vocabulary notebook and learning system. In the future, I will continue to use Swift on Server to meet other product requirements.</p><p>The reason for starting this series is to systematically share my experience using Swift on Server and help more people benefit from it.</p><p>Admittedly, Swift on Server is not a solution for everyone, so I have also listed a portrait. If you meet these conditions, please continue to follow this series of articles.</p><h3>Who Is Suitable for Using Swift on Server?</h3><p>Any one of the following criteria applies:</p><ul><li>Already using Swift language.</li><li>Has their own iOS app and wants to develop a backend.</li><li>Passionate about Swift language.</li><li>Focuses on performance and high concurrency.</li></ul><h3>Series Preview</h3><p>This series of articles will use a microblog server as an example to explore the world of Swift on Server. This series is mainly aimed at beginners in server development, so in addition to implementing functions, we will write a lot of concept-related content.</p><p>Overall, the topics will cover the following aspects:</p><ol><li>Concept: What is a server app?</li><li>Concept: What happens in an HTTP request?</li><li>Framework: Choose your framework — Vapor.</li><li>Database: Design your data model.</li><li>API: Design your API.</li><li>Auth: User permission verification.</li><li>Test: Test your API.</li><li>CI: Deploy your server.</li><li>Microservices: Working with other languages.</li><li>Microservices: Chat room with multiple people online simultaneously.</li></ol><p>I will update this series in my spare time and hope to update it every 1–2 weeks.</p><p>Stay tuned!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f842d6ddaa03" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to learn Japanese by reading Novels and News with the help of Oyomi.]]></title>
            <link>https://kevinzhow.medium.com/how-to-learn-japanese-by-reading-novels-and-news-with-the-help-of-oyomi-736e8dd1e7c4?source=rss-188ffe4b279a------2</link>
            <guid isPermaLink="false">https://medium.com/p/736e8dd1e7c4</guid>
            <category><![CDATA[japanese]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[apps]]></category>
            <dc:creator><![CDATA[Kevin]]></dc:creator>
            <pubDate>Sat, 18 Feb 2023 09:26:55 GMT</pubDate>
            <atom:updated>2023-02-18T09:26:55.859Z</atom:updated>
            <content:encoded><![CDATA[<p>If you are interested in learning Japanese but feel overwhelmed by the complexity and variety of the language, you might want to check out Oyomi, a smart app that can help you learn Japanese from any content you like.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*olrcVKpSIdEopDLVjfEJcQ.png" /></figure><p>Oyomi has several helpful features that can make your learning process easier and more enjoyable. Here are some of them:</p><ol><li>Oyomi can extract content from web pages or EPUB books.</li><li>Oyomi can do semantic analysis of the content and tell you what grammars are used as well as the meaning of the content.</li><li>You can collect words and sentences so Oyomi will generate a review plan for you automatically.</li></ol><p>You don’t have to limit yourself to boring textbooks or limited resources when learning Japanese.</p><p>With Oyomi, you can choose any web page or EPUB book that interests you and import it into the app.</p><h3>Learn from Web Pages</h3><p>Oyomi is a powerful tool that can help you learn from any web page. It can analyze the text and structure of a web page and turn it into semantic blocks that you can easily understand and manipulate. Here are the steps to use Oyomi to learn from web pages:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KsRmfcZ97eD61Agcg7FZOA.png" /></figure><ol><li>Copy the web url of the page you want to learn from and paste it into the analyze field in Oyomi.</li><li>Click the “Analyze” button on the top right corner of the screen.</li><li>Wait for the web page to load in Oyomi. You will see a preview of the page.</li><li>Click the “Analyze” button again to process the text into semantic blocks.</li></ol><h3>Lookup &amp; Translation &amp; Read Aloud</h3><p>From here now you can easily lookup the meaning of the word or translate and read aloud the sentences.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eQZvIq8rRTCcHHuHP9SzAQ.png" /></figure><p>You can tap on any word or phrase to see its meaning, pronunciation, part of speech, and example sentences.</p><h3>Verb conjugation</h3><p>You might have encountered some difficulties with verb conjugation. Unlike English, where verbs only change their forms based on tense and number, Japanese verbs have many different forms that express various nuances of mood, politeness, honorifics and more.</p><p>For example, the verb 食べる (taberu), which means “to eat”, can be conjugated into dozens of forms such as 食べます (tabemasu), 食べない (tabenai), 食べさせる (tabesaseru), 食べられる (taberareru) and so on. Each form has a different meaning and usage that you need to master in order to communicate effectively in Japanese.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GOaNBJc9oqLVhBvpF6iigg.png" /></figure><p>How can you master all these verb forms and use them correctly in your sentences? Well, one way is to memorize the rules and patterns of verb conjugation. But that can be tedious and time-consuming. Another way is to use Oyomi, a handy tool that helps you learn verb conjugation in an easy and fun way.</p><p>You can also see the process of verb conjugation step by step. For example, if you want to know how to conjugate 食べる into potential form (which means “can eat”), you can simply click on the verb and Oyomi will show you the result:</p><p>食べる -&gt; drop る -&gt; add られる -&gt; 食べられる</p><h3>Learning</h3><p>When you click the “Study” button, you’ll see three sections: Structure, Vocabulary and Grammar.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E9bKgZNwCt-X_EJiKf14Lw.png" /></figure><h3>Structure</h3><p>The Structure section shows the semantic tree of the sentence, indicating the grammatical relationship between the phrases.</p><h3>Vocabulary</h3><p>The Vocabulary section shows all of the words that you plan to learn from the sentence. You can add words to this section by clicking the star before the word when you are doing a lookup. This way, you can create your own personalized word list based on your interests and needs.</p><h3>Grammar</h3><p>The Grammar section shows all of the grammatical rules related to the sentence. It tells you how and why certain structures are used in different contexts. You can also find examples and explanations for each rule to help you understand them better.</p><h3>Learn from EPUB Book</h3><p>Oyomi has a built-in bookshelf that supports EPUB format books. You can import your EPUB books by clicking the add button at the top right corner of the app. Then you can browse and select the books that you want to read.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BCvcNoIZlpJ_jkc1HHJOtQ.png" /></figure><p>When you open a book, you will see an “Analyze” button after each paragraph.</p><p>This button allows you to analyze the content of the paragraph and get useful information such as vocabulary definitions, grammar explanations, furigana readings, and more.</p><p>You can also listen to the audio of the paragraph and practice your pronunciation.</p><h3>Review plan</h3><p>Another challenge of learning Japanese is remembering what you have learned and applying it in real situations.</p><p>Oyomi can help you with that by allowing you to collect words and phrases that you want to remember or practice later.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LjrcFczBNyIEd1edsy_bgw.png" /></figure><p>You can add them to your personal wordbook with just one tap of the star icon before the word.</p><p>Oyomi will then generate a review plan for you based on your learning progress and goals. You can review your words and phrases anytime using various modes such as choice, fill-in-the-blank, matching, etc.</p><h3>Use the Widget to Learn Vocabulary on Your iOS Home Screen</h3><p>If you are looking for a convenient and effective way to improve your vocabulary, you might want to try the widget feature on your iOS device.</p><p>The widget is designed to help you use fragments of time to memorize words. Whether you have a few minutes before a meeting, during a commute, or while waiting in line, you can use the widget to learn new words or refresh your memory.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vy-So8nv5gHUJ5KwCbG4bg.png" /></figure><p>To add the widget to your home screen, follow these simple steps:</p><ul><li>Long press on an empty area of your home screen until the apps start jiggling.</li><li>Tap on the plus sign (+) at the top left corner of the screen.</li><li>Search for Oyomi</li><li>Tap on the widget app and choose the size and style of the widget you want.</li><li>Tap on Add Widget and place it anywhere on your home screen.</li><li>Tap on Done at the top right corner of the screen.</li></ul><p>You can now enjoy learning vocabulary with the widget anytime and anywhere. Happy learning!</p><h3>Get the App</h3><p>Try it out yourself download it now. Oyomi now supports iOS Android and macOS.</p><p><a href="https://apps.apple.com/us/app/oyomi-japanese-reader/id1474251984">App Store.</a></p><p><a href="https://play.google.com/store/apps/details?id=com.kevinzhow.pengdu&amp;hl=en&amp;gl=US">Google Play Store</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=736e8dd1e7c4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Behind the Scenes of Developing a New App: “Oyomi: Japanese Grammar Learning and Analyzer”]]></title>
            <link>https://kevinzhow.medium.com/behind-the-scenes-of-developing-a-new-app-oyomi-japanese-grammar-learning-and-analysis-956a939b1fa8?source=rss-188ffe4b279a------2</link>
            <guid isPermaLink="false">https://medium.com/p/956a939b1fa8</guid>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[japanese]]></category>
            <dc:creator><![CDATA[Kevin]]></dc:creator>
            <pubDate>Thu, 16 Feb 2023 06:23:47 GMT</pubDate>
            <atom:updated>2023-02-17T02:39:47.743Z</atom:updated>
            <content:encoded><![CDATA[<h3>Why did I develop this app?</h3><p>After developing the app “KanaOrigin” for learning Japanese kana, I started to think about how to make a product related to grammar. Although there are a few products on the market for reference, I felt that this might be an opportunity to rethink this problem, so I brought this question back to “the purpose of learning Japanese”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*olrcVKpSIdEopDLVjfEJcQ.png" /></figure><p>For me personally, the purpose of learning Japanese is very simple. I hope to be able to understand what those delicious things, beautiful packages, light novels, manga, games, and various signs I encounter in Japan are written.</p><p>So from this perspective, what I hope most is to learn Japanese by reading the content I like. If there is an app that can help me interpret various content and summarize knowledge points, that would be great.</p><p>Therefore, with this goal in mind, I started to design this app.</p><h3>Oyomi’s functional design</h3><p>Let’s start with a famous quote from the science fiction writer “Verne”:</p><p>人間が想像できることは、人間が必ず実現できる。</p><h3>Word segmentation</h3><p>Japanese, like Chinese, does not come with word segmentation. The first step of Oyomi is to use machine learning technology to break down the whole into parts, segment the sentences, and add some part-of-speech tags.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4m_IDy9HbdVxieGqUJEHtw.png" /></figure><p>Then, if you already know how to read kana, you can read it with the addition of ruby (furigana).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yeOdj9kFrLYocS1n6snBLA.png" /></figure><p>To make it easier for us to distinguish the parts of speech, we can customize some color markings.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*snvO4g-xQynWK68VqytoZA.png" /></figure><h3>Word lookup</h3><p>At this stage, it is to figure out the meaning of each word. In Oyomi, you can directly click on any word to find out its meaning.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5NC8zwqJcZnE5SXiPKiWOg.png" /></figure><p>Oyomi has a simple and intuitive feature that lets you add words to your personal wordbook.</p><p>All you have to do is to click on the star icon before the word, and Oyomi will automatically save it for you.</p><p>But that’s not all. Oyomi also creates a customized learning plan for you, based on your level and progress. It will remind you to review the words at the optimal intervals, using spaced repetition techniques, to help you form long-term memory.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7dnYeQmUnI5X0JBx_cj55g.png" /></figure><h3>Conjugation inference</h3><p>For word lookup, I didn’t stop there. If you have learned some Japanese, you should understand the learning pain points brought by “conjugation”. Therefore, for verbs with conjugation, Oyomi will help you trace the conjugation process and show what the original form is.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RhhyJXPIu8rMkcD7rDzBYg.png" /></figure><p>In later versions, this feature will be extended to other words with conjugation, such as adjectives, adjectival verbs, auxiliary verbs.</p><h3>Semantic structure</h3><p>Even if we know the meaning of each word, there is still an important modifier relationship between the sentences that needs to be understood clearly. Therefore, Poread still uses machine learning technology to provide the semantic structure function.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WrTq1AOeqTKsJ0FCE6okcw.png" /></figure><p>This is a very simple tree structure. We can look from the bottom up. The core part of the whole sentence is the last orange “have the ability to achieve” and its part is explaining what can be achieved.</p><p>According to this semantic structure, I think you can probably figure out the meaning of a sentence.</p><h3>Read aloud and translate</h3><p>Finally, Oyomi also provides read aloud and translation functions, so that you can compare whether your answer is consistent with the correct answer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hlf5ZlehviGoJJA8wB_WvQ.png" /></figure><p>Through the above process, you can freely choose the content you want to read.</p><p>If you can’t find it for a while, I also prepared some content recommendations that will be updated from time to time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sjkBr52QDlviKH6Q6vWTEw.png" /></figure><p>Here are some classic novels, light novels, and some music recommendations.</p><h3>Analysis</h3><p>In the analysis interface, you can use the scan function to scan some content from books, pictures, or you can enter it yourself</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EFrfRuN8otWILvxnJCLJoQ.png" /></figure><p>Then click “Analyze” and you’re done.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dJ4jV6wApi6DOgND9zJxUw.png" /></figure><p>So, is that all for Praise?</p><p>Of course not, although I did want to develop it to this point and release it at first, but I think that if the user who downloads this software is a Japanese novice, it might be a bit confusing to use, and the experience seems to be missing something…</p><p>Right! It’s the “Learning” module.</p><h3>Interactive Course</h3><p>Oyomi Season 1 has prepared about 8 introductory courses, all using an interactive learning method, and, Season 1 is provided for free.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yOUaAn6RUgVfSLRkAs9-aQ.png" /></figure><p>These 8 lessons should help you smoothly understand the origins of Japanese characters, word rules, word order, sentence patterns, and modifiers, conjugations.</p><h3>Reference</h3><p>The last part is a quick reference manual</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xh8CvH9kastlOk55oyevQQ.png" /></figure><p>Currently, I have made the “Verbs”, “Adjectives”, and “Honorifics” sections, which should also be the most frequently referenced parts in Japanese learning.</p><p>For example, for verbs, not only does it introduce what the three types of verbs are, but also the specific conjugation methods</p><p>After clicking on conjugation, you can see how to add auxiliary verbs to this type of verb, common sentence patterns, and what conjugation process is required before adding auxiliary verbs. This should be of great help in understanding conjugation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YU3uI0vBS8cQ_CKp-fKV1A.png" /></figure><h3>Conclusion</h3><p>The above is all the core functions of Praise at present, each function is derived from my rethinking of the Japanese learning method, and also the result of my own research on Japanese, I hope it can help you who are self-studying Japanese.</p><h3>Download App Now</h3><p>Oyomi now supports iOS macOS and Android.</p><p><a href="https://apps.apple.com/us/app/oyomi-japanese-reader/id1474251984">App Store</a></p><p><a href="https://play.google.com/store/apps/details?id=com.kevinzhow.pengdu&amp;hl=en&amp;gl=US">Google Play</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=956a939b1fa8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Clubhouse 在中国会怎么样？它的可复制性与不可复制性]]></title>
            <link>https://kevinzhow.medium.com/clubhouse-%E5%9C%A8%E4%B8%AD%E5%9B%BD%E4%BC%9A%E6%80%8E%E4%B9%88%E6%A0%B7-%E5%AE%83%E7%9A%84%E5%8F%AF%E5%A4%8D%E5%88%B6%E6%80%A7%E4%B8%8E%E4%B8%8D%E5%8F%AF%E5%A4%8D%E5%88%B6%E6%80%A7-896823781f9b?source=rss-188ffe4b279a------2</link>
            <guid isPermaLink="false">https://medium.com/p/896823781f9b</guid>
            <category><![CDATA[clubhouse]]></category>
            <dc:creator><![CDATA[Kevin]]></dc:creator>
            <pubDate>Wed, 03 Feb 2021 23:56:02 GMT</pubDate>
            <atom:updated>2021-02-03T23:56:40.039Z</atom:updated>
            <content:encoded><![CDATA[<p>我接下来会快速的概括一些想法，并假设你已经用过 Clubhouse。</p><h3>传统社交平台的问题</h3><p>我经常跟朋友感叹，现在社交媒体上很难开口说话，只要你说的有一点违反「说话的艺术」，那么通常都会有人以惊人的精力和毅力，不停揪住一个刁钻的角度和你摩擦，直到你选择拉黑对方。即使如此，留下的也是一种「我是输了还是赢了」的自我怀疑，可能还需要自我进行一些心理干预。</p><p>这真的糟透了。</p><p>我无数次想起互联网的 Blog 时期，Twitter 早期，饭否时期，为之怀念。那时候共识是大概率能达成的，争论是有意义的，现在上网的人多了，都会打字了，在这些平台上的社交体验却变得比我青春期和家长的交流体验还差。</p><p>事实上优质的社交体验需要经过筛选，这已毋庸置疑，我们通过兴趣，从新的角度聚合，我们翻越围城，在新的地方聚合，但却总在重复一件事情，「他们」又来了。</p><p>为何我们的社交体验，能够如此之大的被「他们」影响？这可能是每个社交平台为了追求扩张留下的副作用。转发，评论，这两个 Web 2.0 的好兄弟，极大的降低了表达的门槛，但不加思考的表达越来越多，这个问题就开始变得复杂。</p><p>思考本身是一种技能，表达也是一种技能，这两者在社交时，本身应该是一个筛选选项，而在那个时期，降低这两个门槛获取用户，是产品成长的秘诀，作为一个产品经理，你甚至能因为做到了这件事，而被捧上神坛，如果你能利用人性的弱点，不论是好还是坏的方式，得到指数级增加的用户，那你就可以封神。</p><p>成长的代价我们现在都尝到了，我们不仅得到了一个以声量定对错的社交「媒体」，还得到了水军，所有的规则漏洞都被利用了起来，每个人都身处一个精心定制的回音壁，最后社交中的表达，独立思考都变成了一种稀缺，我们得到了一个巨大的媒体，但我们失去了社交。</p><h3>Clubhouse 改变了什么</h3><p>它给回了我们社交，它的优点很多，但我只想说其中一个。</p><p>当我第一次进入一个 room 的时候，作为听众，我不能打字，只能听，所以我无法打断任何人，也无法恶心任何人，更无法吹捧任何人。</p><p>所以我无法操控发言者，听众的任何思考过程。</p><p>如果我觉得发言者是一帮傻叉，我可以立刻走人，但我也可以耐着性子听一会，如果我真的不服，我可以举手发言，得到允许后成为发言者。</p><p>你必须有能力逻辑清晰的表达自己的观点，才能成为台上的参与者，我爱死这个筛选机制了，这真的太棒了，谁还不会打字，留言装什么孙子，更别说绝大部分留言还限制字数，发的链接可能也打不开。</p><p>除此之外，你当然也可以自己开 room 成为发言者，说自己想说的，但一切判断，都是由听众选择。这种对独立思考的尊重，自由表达的信任，美到令人窒息。</p><h3>Clubhouse 在中国会怎么样？它的可复制性与不可复制性</h3><p>我们不需要谈论他的产品，他的技术，这些都可以复制，甚至邀请的人脉也可以复制，你可以像素级复制所有东西。</p><p>但它存在的基础不基于这些，我们只需要关注他在中国不可能存在的关键部分。</p><p>以我上文提到的优点为例，当我们谈论独立思考，那么什么是独立思考？其实独立思考并不复杂，他只是针对信息的总结，当你看到了足够多的因果关系，那么就可以得到一个判断依据，去判断其他事的结果，我们甚至都还不需要走到说对错的阶段。</p><p>因此，提倡独立思考，我们就是在信任信息的自由传播。当你在 Clubhouse 开启一个房间，当大家在社交，讨论，试图针对一件事得出共识。那么前提就需要所有人可以得到相同的信息，至少是分享相同的信息，而不需要担心因此受到不可挽回的惩罚。</p><p>这就决定了 Clubhouse 在中国的不可复制，拿过来你得到的必然不是 Clubhouse，而是一个 Feature.</p><h3>基于这个 Feature，我们有什么可能性</h3><p>我痴迷于做产品的原因就在于，用户对于「能解决问题的产品」的正负反馈是如此迅速。而产品的规模无非是在于你解决的问题是一种共性问题，还是特殊问题。剩下的运营，营销，商业部分，则是一种催化剂，决定这款产品以何种路径，何种速度走向坟墓（如果觉得不适可以把坟墓换成成功）</p><p>为了不走向坟墓，产品总是在求变，来续命一波。</p><p>Clubhouse 最近常被不同的音频类产品拿来比较，但这毫无意义，功能只是布料，产品是剪裁的结果。我们已经有很多产品，用语音聊天室的方式解决了各种陌生人的问题，解决了会议的问题，用直播的方式，解决了很多带货的问题。</p><p>但我们社交的问题没有被解决，至少是没有用最优雅的方式解决。</p><p>而幸运的是，这次解决问题的几个要素，又一次全都集齐了。</p><ol><li>我们有一个完美的产品样板，这意味着所有目标用户已经认可这种形式</li><li>只要你有聚合一群有趣的人的能力，这种形式就可以用</li><li>落地这种 feature，他不依赖于取代现有产品，也不依赖于特定平台，你可以选择共生，也可以选择自力更生</li><li>疫情给了 Clubhouse 这类场景迁移到线上的理由</li></ol><p>最后我不想说这个 Feature 会颠覆什么，因为这显然会让人产生联想，无论这种联想是否切合实际。Clubhousue 只是在解决问题，而这些问题确实越来越痛苦，大家都期待新的社交体验，因此产品人也不需要再纠结什么，我很期待接下来能看到的新东西。</p><blockquote>接下来我会说一些和 Clubhouse 无关的内容，主要是一些自己的事情，如果不关心的话就不要看了。</blockquote><p>我虽然有很多怎么做的想法，但很可惜这次我有不做理由，如果有持续关注我的朋友，可能知道我早已经决定在现有产品的路上还要延续着再走至少 3 年。</p><p>事实上 2018 年我放弃了很多东西离开北京的时候，所为的便是追求自己的产品观，虽然当时我以为这将是没有限制，完全自由的追求。</p><p>尽管有镣铐，过去的 3 年里我还是很享受这个过程，接下来的时间更为关键，这决定了 3 年后我到底能做到什么程度。</p><p>此时此刻我体会到了这句话「决定做什么真的不是很难，决定不做什么很难」</p><p>与君共勉。</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=896823781f9b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[聊一聊 50 音起源的再设计]]></title>
            <link>https://kevinzhow.medium.com/%E8%81%8A%E4%B8%80%E8%81%8A-50-%E9%9F%B3%E8%B5%B7%E6%BA%90%E7%9A%84%E5%86%8D%E8%AE%BE%E8%AE%A1-759afb4dbe6c?source=rss-188ffe4b279a------2</link>
            <guid isPermaLink="false">https://medium.com/p/759afb4dbe6c</guid>
            <category><![CDATA[日语]]></category>
            <category><![CDATA[设计]]></category>
            <dc:creator><![CDATA[Kevin]]></dc:creator>
            <pubDate>Fri, 22 Feb 2019 06:59:14 GMT</pubDate>
            <atom:updated>2019-02-22T07:23:32.205Z</atom:updated>
            <content:encoded><![CDATA[<p>在春节期间 <a href="https://itunes.apple.com/cn/app/id1439222882?mt=8">50音起源</a> 发布了重新设计的 1.1 版本。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*sW0116a7Vw1bV6Uo.png" /></figure><p>这里也一并拿出老版本的设计对比一下。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ryHMo4k1YBvXOoyF.png" /></figure><p>重新设计的起因，是因为之前的版本是作为「最小可用」的产品去设计的，因此当希望进行功能拓展时，并不能适应新的需求。考虑到这也是一个尝试一些新设计，突破自我的时候，我喝了杯咖啡便开动了。</p><h3>「起源」再设计</h3><p>很显然，随着用户的重度使用，起源相关的内容会逐渐被掌握，这个页面的查看几率也会逐步下降，直到用户几乎忽略这部分功能。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Xc_W5Kt9ywAZtXpM.png" /></figure><p>恰好，在新版中，我有几个想要实现的功能</p><ul><li>根据用户的学习情况，动态提示用户学习和复习的内容</li><li>特训功能，帮助用户针对自己的弱项高强度学习</li><li>提供一些和人文相关的日常信息，比如星期几，月份的传统讲法</li></ul><p>为了融合这两部分，我尝试在原版的风格上进行拓展，及其艰难的，我设计出了下图的状况</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/910/0*mD3VeeW9TyVYNNt0.png" /></figure><p>在起身观看这半截设计的时候，我觉得是无法接受的，这是一个毫无美感，甚至比之前更差，难以协调的设计。抱着对自己怀疑和羞耻之情，我重新开了一个 Sketch 文档，和过去彻底做一个了断。</p><p>所幸的是，这种了断真的减轻了我的思想包袱，我得以很轻松的去尝试新的设计。在新的设计中，我希望给用户一种愉悦，宁静的心情，所以色彩成了我首先考虑的元素。</p><p>基于 iOS 的 Large Title 去简化了界面元素，删除分割线，再按照功能去划分了不同的 Section. 每个 Section 按照对应的功能特色去进行「形式」的设计。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/732/0*7DTBgvh4UMoT8d-g.png" /></figure><p>最终「起源」就完成了它的再设计，成为了「今天」</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/896/0*02dbmR-IoJ6jDOMt.png" /></figure><h3>「学习」的再设计</h3><p>在旧版的设计中，学习的部分在现在来看，是简单过头了</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*U8vdwHHY6VodoIdu.png" /></figure><p>更让我介意的是，配合这样的白色主题，学习过程会显得比较乏味。我希望在新的设计中，通过色彩的变化，给用户新鲜感。每个不同的学习项目，都配合了不同的颜色主题，这个主题和「今天」中的卡片颜色是对应一致的。</p><p>同时，选择题的圆形会很大程度上限制内容的长度，因此也做了对应的修改。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZXdjxzYyXhitQ4RG.png" /></figure><p>最终得到的结果还是让我满意的，抛弃了 iOS 的系统主题框架，新的进度条和课程提示信息也显得更加赏心悦目。</p><h3>「速查」与「课程」的再设计</h3><p>这部分的改动其实不多，主要是对主题色彩进行了统一</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*N7lUsFK2Rf-AKtHb.png" /></figure><p>修改了会让气氛显得严肃的衬线体，从而在整体上能够保持让用户感到轻松的心情。</p><h3>后记</h3><p>这次再设计，整体上已经能够承担未来 1 年多的功能演化，在这个过程中，及时与旧设计说再见想来是我做的非常正确的一个决定，如果一个设计已经不能够给你灵感，那么确实也是时候去做些改变了。</p><p><em>Originally published at </em><a href="https://zhowkev.in/2019/02/22/liao-yi-liao-50-yin-qi-yuan-de-zai-she-ji/"><em>zhowkev.in</em></a><em> on February 22, 2019.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=759afb4dbe6c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[自由职业一周年我收获了什么]]></title>
            <link>https://kevinzhow.medium.com/%E8%87%AA%E7%94%B1%E8%81%8C%E4%B8%9A%E4%B8%80%E5%91%A8%E5%B9%B4%E6%88%91%E6%94%B6%E8%8E%B7%E4%BA%86%E4%BB%80%E4%B9%88-954c10e297a7?source=rss-188ffe4b279a------2</link>
            <guid isPermaLink="false">https://medium.com/p/954c10e297a7</guid>
            <dc:creator><![CDATA[Kevin]]></dc:creator>
            <pubDate>Thu, 22 Nov 2018 00:26:22 GMT</pubDate>
            <atom:updated>2019-02-21T05:07:04.165Z</atom:updated>
            <content:encoded><![CDATA[<p>近日自觉到了一个时间节点，仔细一想，是一周年的日子，正好「<a href="https://zhowkev.in/2018/11/13/cong-qi-yuan-kai-shi-xue-xi-50-yin-de-app/">50音起源</a>」也发布了，决定写篇文章整理下自己的内在。</p><h3>自由？</h3><p>自由职业，其实就是个体户，但通常并不是路边卖小笼包那样有生活气息。自由职业更多的是依靠某种专业技能，离开了公司这种组织，自行在社会上发光发热。</p><p>我仍然很清楚的记得，我决定离开公司的那个瞬间。有一天我突然觉得自己是一个，不会画画，不会音乐，在所从事的事情上找不到自己理想的痕迹，虽然生活无忧，却只能靠买买买来补偿内心空虚的人。</p><p>这不就是我自己年轻时候讨厌的人吗？</p><p>我开始假象顺着这个轨迹，自己的未来是什么样子，三年，五年，或者十年。我发现如果不离开这种环境，我无法给自己规划未来。我亦不能成为一个自己欣赏的人。</p><p>很多情绪冲了上来，我在之后的几个月里陷入了充满抑郁的生活。</p><p>最终，我听从了内心的声音，选择了改变。我想我也别无选择，否则它已经放弃了生的渴望。</p><p>一个重新获得了自由的灵魂，在快乐中有些迷茫，我到底该向什么方向去？</p><h3>内观</h3><p>在随后的日子里，虽然有成立公司的计划，但随着我一些想法的成型，最终把计划推迟了。我希望花更多时间去观察自己，培育自己的心智。</p><p>究其原因，坦诚的说，我感觉自己的心智不像以前那么坚定了，或者说相去甚远，它充满了疑问，并缺少对「自我」的认同感。这种状态我无法让自己的行动配合上自己的思考。有些我觉得应该做的事情，内心在反抗。</p><p>心智快要和我散伙了。</p><p>从这个时候起，我把「心智」的概念与「我」分割开来，开始去观察它，它本能的对一切作出反应，而我负责思考其背后的原因，试图与其沟通，和解。</p><p>这种方式确实帮助到了我，「心智」有自己的价值观，「我」有被社会所熏染的另外一种价值观。两者不能相互侵犯，只能对话，我既需要做那些让「心智」成长的事情，也需要做那些让「我」成长的事情，两者才不会互相嫌弃。</p><p>内观随之成为了我的日常活动，它给我带来的成长远超出了我的预料。我内心的挣扎越来越少，决策和行动越来越多。</p><h3>帮助别人成长</h3><p>在接下来的日子，我开始思考自己应该投身于什么事情上。我想过让自己兴奋的社交产品，游戏，甚至做出了几款 MVP，但最终我放弃了他们。</p><p>因为我找不到这件事上的价值，或者说，这些都不是一件我失败了也不后悔的事情。这和以前有着极大的不同，因为「心智」变了，它不再认同一切创造活动，它告诉我健康，精力，时间的有限，它希望我做那些能帮助别人成长的事情，以此作为给我提供执行力的条件。</p><p>「我」接受了。</p><p>此后，我的方向就定为了「成长」</p><h3>产品的方法</h3><p>由内而外的，选择产品的方法也发生了改变，现在我在选择一款产品做什么的时候，会有三个基本问题去考虑。</p><ul><li>这个需求是不是不会变的</li><li>如果我坚持 10 年，能做到多极致</li><li>对于同类产品，我是否能够提供更好的体验，并大幅超过替换成本</li></ul><p>专注在时间纬度的投入，回报最终是惊人的。每个方向都有其极致与超越极致的状态，这些因素都要最终和自己的一切结合，成为生命的一部分。</p><p>因此我充满热情的去创造，拿出 MVP 来测试，并调整自己接下来的行动。</p><h3>心愿</h3><p>我希望自己明年能完成今年所构想的一款产品，并切能够更充实的过好每一天。</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=954c10e297a7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[「50音起源」从起源学习 50 音的 App iOS/Android]]></title>
            <link>https://kevinzhow.medium.com/50%E9%9F%B3%E8%B5%B7%E6%BA%90-%E4%BB%8E%E8%B5%B7%E6%BA%90%E5%AD%A6%E4%B9%A0-50-%E9%9F%B3%E7%9A%84-app-ios-android-649929906cad?source=rss-188ffe4b279a------2</link>
            <guid isPermaLink="false">https://medium.com/p/649929906cad</guid>
            <category><![CDATA[日语]]></category>
            <dc:creator><![CDATA[Kevin]]></dc:creator>
            <pubDate>Tue, 13 Nov 2018 14:49:14 GMT</pubDate>
            <atom:updated>2019-02-21T05:10:11.486Z</atom:updated>
            <content:encoded><![CDATA[<h3>an「50音起源」从起源学习 50 音的 App iOS/Android</h3><p>几乎尝试过了每一款日语学习软件，在这个过程里有不少困惑我的地方。</p><p>我认为日语学习并不是简单的学习假名，词汇，语法。而是应该是从其背后的文化开始学起，产生共鸣与认同。而我尝试的各种日语学习软件，都有些过于直奔主题，这种情况下每个假名不会和学习者建立起感情的连接，相反可能更像鬼画符。</p><p>这是我自己的体验，所以开发这款软件的初衷也是为了改善学习体验。因此「50音起源」这款 App的第一个 Tab 就是放了「起源」相关的内容。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SjYHYgsk2uVvapUs.png" /></figure><p>我相信这些会让学习者更好的理解日语，后续还有很多值得我去做的内容，如果下载的用户多我会做的快一点，少的话，我可能做的慢一点。</p><h3>字源是什么？</h3><p>每个假名都从汉字的演化而来，像平假名是从草书演化过来，片假名是从楷书的偏旁部首演化而来。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0I_-8ehdQOLa-xe4.png" /></figure><p>字源的演化是学习过程中应该知道的一部分，因此在速查中，一并列出了假名的字源。这确实更好的帮助我建立了和这些假名的感情链接。</p><h3>学习方式是怎么设计的？</h3><p>每个假名都有</p><ul><li>建立印象</li><li>选择题测试</li><li>拼写测试</li><li>反应速度测试</li></ul><p>四个过程进行学习，并辅以符合遗忘周期的复习方式。但我没有设置推送提醒，因为，如果是提醒了才学习，反而学的没劲，还可能产生厌烦情绪。主动学习的时候，感觉会好得多。我更希望每次打开软件，用户都可以获得美好的体验。希望在这个过程里，兴趣去做用户的监督者。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*BxbZWk8DoMVCGMM1.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HRs2lJdypprn8MDY.png" /></figure><p>在最开始学习的时候，会通过一组母语文字测试来建立你对一种文字的反应基准线，学习模块的目标是让你对 50 音的反应能接近母语的反应。</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jJErQibb6tWiFxxW.png" /></figure><p>除此之外，部分单词还搭配了可以交互的 3D 模型</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*m2vU9TDpWXXypoUW.png" /></figure><h3>我应该如何使用这款软件？</h3><p>50 音的学习是日语学习最开始的一部分，建议通过「起源」了解假名的历史背景，利用「速查」在单词学习过程中对照自己遗忘的假名读法，使用「学习」功能对假名逐渐建立概括性的了解。</p><p>而对于日语进一步的学习，我的建议是构建交流的场景，学习思想的表述，掌握更多的词汇。</p><p>利用 Siri 就可以达到一个有趣的交流实验，把 Siri 改成日语，用翻译软件翻译一句 “今天天气怎么样” 成日文 — — “明日の天気はどうですか” 听软件怎么发音，然后你可以讲给 Siri 让它回答你，一次有趣的交流就完成了。</p><p>我们把 Siri 改成日语，构建了一个交流场景，“明日の天気はどうですか” 是你想要表述的想法，这时候需要解决的问题就是掌握这句话的语法，以及词汇。</p><p>在这句话里，语法就是如何用 “の，は，どうですか” 把词汇 “明日，天気” 粘到一起去。去学习一些基础的日语语法，构建更多的交流场景，学习就会更加顺利并且愉快。</p><h3>接下来有什么计划？</h3><p>接下来会加入单词的部分，加入后软件会涨价。另外，单词的学习方式，也会颇具新意的。</p><h3>下载</h3><p>点这里<br> iOS <a href="https://itunes.apple.com/us/app/apple-store/id1439222882">https://itunes.apple.com/us/app/apple-store/id1439222882</a><br> Android <a href="https://play.google.com/store/apps/details?id=com.kevinzhow.kanaorigin">https://play.google.com/store/apps/details?id=com.kevinzhow.kanaorigin</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=649929906cad" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>