Author Archives: Brian Moriguchi

Privacy Policy – PoliPoli version 1.0

Privacy Policy

Becko’s Inc. built the [PoliPoli – version 1.0] app as a Free app. This SERVICE is provided by Becko’s Inc. at no cost and is intended for use as is.

This page is used to inform visitors regarding our policies with the collection, use, and disclosure of Personal Information if anyone decided to use our Service.

If you choose to use our Service, then you agree to the collection and use of information in relation to this policy. The Personal Information that we collect is used for providing and improving the Service. We will not use or share your information with anyone except as described in this Privacy Policy.

The terms used in this Privacy Policy have the same meanings as in our Terms and Conditions, which is accessible at [PoliPoli – version 1.0] unless otherwise defined in this Privacy Policy.

Information Collection and Use

For a better experience, while using our Service, we may require you to provide us with certain personally identifiable information, including but not limited to None. The information that we request will be retained by us and used as described in this privacy policy.

The app does use third party services that may collect information used to identify you.

Link to privacy policy of third party service providers used by the app

Log Data

We want to inform you that whenever you use our Service, in a case of an error in the app we collect data and information (through third party products) on your phone called Log Data. This Log Data may include information such as your device Internet Protocol (“IP”) address, device name, operating system version, the configuration of the app when utilizing our Service, the time and date of your use of the Service, and other statistics.

Cookies

Cookies are files with a small amount of data that are commonly used as anonymous unique identifiers. These are sent to your browser from the websites that you visit and are stored on your device’s internal memory.

This Service does not use these “cookies” explicitly. However, the app may use third party code and libraries that use “cookies” to collect information and improve their services. You have the option to either accept or refuse these cookies and know when a cookie is being sent to your device. If you choose to refuse our cookies, you may not be able to use some portions of this Service.

Service Providers

We may employ third-party companies and individuals due to the following reasons:

  • To facilitate our Service;
  • To provide the Service on our behalf;
  • To perform Service-related services; or
  • To assist us in analyzing how our Service is used.

We want to inform users of this Service that these third parties have access to your Personal Information. The reason is to perform the tasks assigned to them on our behalf. However, they are obligated not to disclose or use the information for any other purpose.

Security

We value your trust in providing us your Personal Information, thus we are striving to use commercially acceptable means of protecting it. But remember that no method of transmission over the internet, or method of electronic storage is 100% secure and reliable, and we cannot guarantee its absolute security.

Links to Other Sites

This Service may contain links to other sites. If you click on a third-party link, you will be directed to that site. Note that these external sites are not operated by us. Therefore, we strongly advise you to review the Privacy Policy of these websites. We have no control over and assume no responsibility for the content, privacy policies, or practices of any third-party sites or services.

Children’s Privacy

These Services do not address anyone under the age of 13. We do not knowingly collect personally identifiable information from children under 13. In the case we discover that a child under 13 has provided us with personal information, we immediately delete this from our servers. If you are a parent or guardian and you are aware that your child has provided us with personal information, please contact us so that we will be able to do necessary actions.

Changes to This Privacy Policy

We may update our Privacy Policy from time to time. Thus, you are advised to review this page periodically for any changes. We will notify you of any changes by posting the new Privacy Policy on this page. These changes are effective immediately after they are posted on this page.

Contact Us

If you have any questions or suggestions about our Privacy Policy, do not hesitate to contact us.

Brian Moriguchi

PoliPoli – BFF To-Do iOS app to help you achieve goals and complete tasks

Set up goals, add tasks (to-dos) to each goal, monitor goal progress, check your Today’s To-Do across multiple goals. Reminder prompts you to check Today’s To-Do list on pre-set time.

Brian Moriguchi

Adding a repository to GitHub Desktop

A repository that I made on GitHub from browser didn’t show up on GitHub Desktop version. A posting on Stack Overflow shows how to add a repo onto GitHub Desktop.

Brian Moriguchi

Using GitHub with Xcode 8

A couple of GitHub tutorial videos that I watched:

Connect to GitHub with Xcode 8

Uploading an Existing Xcode 8 project to GitHub

Brian Moriguchi

iPhoneLife.com Swift 101 – Classes, Variables, Properties & Methods

iPhoneLife.com Daily Tips once published Swift introductory tutorials. This excerpt is about Classes, Variables, Properties & Methods. I’ve seen and read about exactly the same thing for few times in the past six months, but now everything looks simple and easy:

Defining Classes in Swift

Fig02.001DeclareClass

In Swift, classes are defined in a single .swift source code file as compared to Objective-C, where classes are defined in two separate files, a header (.h) file and an implementation (.m) file.

Declaring Variables

Fig02.002DeclareVariableFull

 

In Objective-C you can declare instance variables at the class level and local variables within methods. In Swift, there are no class-level variables—only local variables that you declare within methods. However, you can declare properties at the class level (see the Declaring Properties section below.)

Declaring Simple Properties

Fig02.004PropertyDeclaration

In Objective-C, properties typically had backing instance variables in which the actual value of the property was stored. Swift simplifies properties by unifying the concepts of properties and instance variables. Properties no longer have a backing instance variable. Everything about a property is declared in a single location.

Declaring Computed Properties

Swift also has computed properties that have associated get and set methods.

Fig02.006CalculatedProperty

In this example, the Thermometer class has a simple temperatureFahrenheit property and a computedtemperateCelsius property.

Notice that the get and set methods of the Thermometer class do not reference an instance variable, because there is no such thing as an instance variable in Swift!

In this case, the get method retrieves the value from the temperatureFahrenheit property, converts it to Celsius and returns the value. The set method takes the value passed to it, converts it to Fahrenheit and then stores the result in the temperatureFahrenheit property.

The value passed to the property’s set method is stored in an implicitly named parameter called newValue. If you want to use a different parameter name, you can specify the name in parentheses after the set as shown in the following code:

Fig02.007NamedSetterParameter

Declaring Methods

Fig02.008MethodDeclaration

To declare a method, you first specify the func keyword, followed by the name of the method. If the method has parameters, you include them in the parentheses. For each parameter, you specify the name of the parameter followed by a colon, followed by its type. If the method has a return value, you then add a hyphen and greater than sign (->) followed by the type of the return value.

The following code contains an example of a method that accepts no parameters and returns nothing:

Fig02.009MethodNoParametersOrReturn

Initializer Methods

Initializer example:

 

 

Fig02.010Initializer

Multiple initializer example:

Fig02.011MultipleInitializers

In this example, both methods are named init, so to make the names unique, an external name is assigned to the parameters—fromFahrenheit and fromCelsius. This makes the full method names init(fromFahrenheit:) and init(fromCelsius:) respectively. It’s worth noting that in Swift, init methods are not inherited.

Creating an Instance of a Class

Fig02.012CreateInstance

Brian Moriguchi